Firebox x1250e crash after upgrading
-
The client is reporting it cannot connect to the server. That's probably because the server isn't running for some reason. If it is running, and you have the correct driver selected, then you will see something on the LCD.
The two LCDproc packages have recently been rebuilt to address the PBI issues and are now both at 0.57.
There is an issue with IPv6 in which the client attempts to use the IPv6 localhost address which the server should be listening on but isn't for some reason. Let me see if I can find that post…...here:
https://forum.pfsense.org/index.php?topic=7920.msg484265#msg484265Steve
-
Hey SW10, on your firebox site where I got the BIOS, I saw and updated WPXepc file. I am using that one, are the other files listed what I can use to play with the code and build it?
-
I installed LCDProc from the packages list and did get to show info after a reboot. Anyway around having to reboot to get it to show info?
-
Yes the source for WGXepc is there at my googlesite.
I assume you installed lcdproc-dev? You mean you have to reboot the box repeatedly? If you're using the official package start method it should be started automatically (though it was very temperamental last time a tried it). You can restart it in Status > Services or by changing a setting in the lcdproc menu and saving it. Personally I don't run it like that because it starts 'sometimes' and crashes often! I do this:
https://forum.pfsense.org/index.php/topic,7920.msg344513.html#msg344513Steve
-
Ill use that cmd if I need to start it again, after installing, moving the conf and choosing the options it showed "pfsense starting" and until I rebooted the box it did not show the actual info chosen in the gui. Which file is the source? The one I pulled works just fine, I just wanted to learn more about that file since I was able to get the files for the custom LCD to play with and actually rebuild LCDd last night. Did you or do you know what the LED option for the LCD do? Does it use the ARM LED? I thought about giving it a try, but didnt want to have to reboot just to have the changes take affect.
-
Nevermind about MBMON, got it installed and working with my custom PHP status pages to show the temp of the box.
-
Got this today, SW10 mind helping me on this one?
Diagnostics: Crash reporter help
Unfortunately we have detected a programming bug.
Would you like to submit the programming debug logs to the pfSense developers for inspection?
Please double check the contents to ensure you are comfortable sending this information before clicking Yes.
Contents of crash reports:
Crash report begins. Anonymous machine information:
i386
10.1-RELEASE-p4
FreeBSD 10.1-RELEASE-p4 #0 36d7dec(releng/10.1)-dirty: Thu Jan 22 15:12:38 CST 2015 root@pfsense-22-i386-builder:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_SMP.10Crash report details:
PHP Errors:
[10-Feb-2015 21:08:41 America/City] PHP Fatal error: Call to undefined function get_stats() in /usr/local/www/getstats.php on line 49Filename: /var/crash/minfree
2048 -
Hmm, my first thought is that you're using a custom PHP status page and the crash report is in the php function get_stats.
Seems likely to be link. ;)Steve
-
The 2 pages I replaced with mine, they actually used my mem code when I checked it in! Anywho the 2 pages I replaced were:
system_information_widget.php
functions.inc.php -
I am getting even more errors using the files from the guthub repo
-
resolved the error
-
My Firebox 500 failed to come back after the 2.2 upgrade: CAM errors as previously reported. I found the solution earlier to force PIO mode with loader.conf hints (https://doc.pfsense.org/index.php/Upgrade_Guide#Disk_Driver_Changes).
I don't really understand why this is the best solution, though. Why does pfSense not figure out the proper mode itself, as it did in 2.1?
Would re-flashing from a new install image help?
-
My Firebox 500 failed to come back after the 2.2 upgrade: CAM errors as previously reported. I found the solution earlier to force PIO mode with loader.conf hints (https://doc.pfsense.org/index.php/Upgrade_Guide#Disk_Driver_Changes).
I don't really understand why this is the best solution, though. Why does pfSense not figure out the proper mode itself, as it did in 2.1?
Would re-flashing from a new install image help?
Sorry my thread was about a kernel error recieved when booting and how SW10 help me resolve that
-
Hey SW10, I tried the LCDd I recompiled on FreeBSD 10.1, when I try to start it I get critical error and no other info, where can I look to see what is happening?
EDIT: SOLVED! Found a flag to show what it does when I issue start. Fixed one thing and it started right up! Now I am trying to decide if I like the one from the package better or my custom one better.
Does the updates I have for LCDProc and LCDProc-DEV from the package manager fix the start issue where after choosing options and starting the service no info showed up until I rebooted?
-
I don't know, does it start up correctly every boot? Does it crash out if your WAN IP changes? ;)
The DMA setting you now have to apply is because in previous versions DMA was disabled by default in NanoBSD (serial). That allowed it to boot on some older boxes like the Alix but put a hude performance restriction on newer hardware that can use UDMA on CF cards. The updated code in FreeBSD 10.1 properly detected the lack of DMA support in the Alix so it can now boot with DMA still enabled. The Firebox can't. It's pretty easy to work around onde you know what's happening.
Steve
-
Only rebooted once so not sure, have a static WAN so I should not have that issue, ill upgrade tonight and see what happens.
-
The location it wants the conf file in for LCDd has changed.
-
It looks like that when I uninstall and reinstall the LCDProc package the custom files I put in the directory get removed and then re-added. Where would those be held so I can delete them to start fresh?
