PfSense 2.2 503 - Service Not Available
-
This seems like a sensible fix. It should help reduce the risk of corruption on data loss. The mitigants seem to me:
-
Make sure SSH access works from wherever one needs to manage a dead firewall from (probably WAN)
-
Backup /etc to someplace sensible
-
adjust /etc/fstab to trade performance for reliability
Hopefully this will get sorted.
I would think that moving to boot on ZFS would be a reasonable migration path. No more fsck.
-
-
zfs is more of a long term goal (and it is one of our goals, definitely) – not something we can implement fast or without lots of testing, and not an option for upgrades. So it is great for the future, but not what we need to fix right now.
-
I'm having this same issue at a remote site.
does it just kill the GUI or does it kill the routing as well? I can still ping the box but I'm really hoping it's still allowing traffic to flow through…...
-
I just ran into this issue on two VM instances of pfSense I was setting up. Iv been struggling to get CARP working between two KVM hosts and would reboot the hosts without shutting down the pfSense VM first (simulating power failure). Have now re-installed the pair 3 times. Trying the ",sync,noatime" option in /etc/fstab to see if it prevents needing to re-install.
-
yaplej: please report if it does help - seems like you're doing the right kind of testing to verify. I've made the changes on all my pfSense instances: fingers crossed power doesn't go out at a remote site and kill it.
-
I had this happen after a power outage. Version 2.2.0. I received 503 error on the web console, tried enabling ssh from the console with no luck, routing did work as long as I gave the workstation a static IP and and a DNS other than pfSense. I ended up reinstalling to fix the issue. I installed several instances this time to different partitions so I can at lease boot something. http://www.blog.unflap.com/2009/12/28/dual-boot-pfsense-for-testing-new-versions/ You can just choose to go back to the main menu instead of reboot and can install as my instances as you need.
Note for some reason a clean install of 2.2.2 would not boot on my Dell Optiplex 320. I would get the F1, F2, F3 selection and then reboot in an endless loop. It had listed ad0 for the drive. I finally went back to 2.1.0 and installed multiple instances without issue to ad4. Not sure why the drive letter change. All three instances updated to 2.2.2 and a config restore just fine.
-
I just had this happen after installing Bandwidthd on a new test 2.2.2 config that I spun up today. No power outage or anything else strange going on. I selected the LAN interface and clicked Save. Then I went to Access Bandwidthd and got:
Please start bandwidthd to populate this directory.
I went back to the Bandwidthd config page and again clicked Save, and that's when I got the 503. All WebGUI attempts now give 503 until I restart PHP-FPM. I have never, ever seen this before until now with bandwidthd.
With PHP-FPM restarted, everything appeared to be normal again. Then when I went to my dashboard, all the widgets were good except for the NTP widget which showed 503, and my LAN traffic gaph which shows
Cannot get data about interface vmx1
ntopng seems to have died as well.
-
That's likely a different root cause than the filesystem corruption others are seeing.
-
And the problem persists through a reboot. Now both squid and squidGuard, which were working fine, are crashing as fast as they can start. WebGUI gives the exact same display as my screencap, with 503 for the NTP widget and the LAN graph not able to talk to vmx1. Bizarre.
-
With the squid* censored, I's pretty much possible you are getting an unclean reboot – which is perfectly enough to screw the filesystem.
On that note, I wonder if anyone tested with fsck from some previous FBSD versions. The one in 10.1 is simply mad.
-
I didn't see any warnings about a dirty filesystem. The system never crashed or anything that might cause an obvious filesystem error. fsck comes up with about a dozen unreferenced inodes though.
-
I left it running overnight and came back to a dead GUI and an endless stream of:
swap_pager_getswapspace(n): failed.
I lost my VMware heartbeat around 1am and it didn't return for 45 minutes.
Hard reset allowed me to boot. The LAN graph is still borked but the NTP widget now seems to be working again.
-
Hi,
I just encontered the same problem today. I'm running pfSense in a VirtualBox on an old computer probably with HDD troubles.
PHP-FPM could not start.I had to reinstall and restore a backup of config.xml.
I hope not to experience this trouble to often.
-
Version 2.2.2 direct install (no vm).
Power cut yesterday and problems here too 503 & 500 errors, ssh wasn't working or dhcp.
-
For those who want to avoid having their filesystem corrupted, here's a quick shell one-liner to add sync to fstab and remount / with sync:
cp /etc/fstab /etc/fstab.orig; /usr/bin/sed -i '' 's/^\(\/.*[[:space:]]*\/[[:space:]]*ufs[[:space:]]*\)rw\([[:space:]]*[[:digit:]][[:space:]]*[[:digit:]]\)$/\1rw,sync\2/' /etc/fstab; mount -o sync /(Be sure to copy the entire line)
This will happen automatically during the 2.2.3 upgrade, and new installs of 2.2.3 will have sync enabled.
-
I also started a wiki doc about it, with the commands there as well. https://doc.pfsense.org/index.php/Filesystem_Corruption_%28503_errors,_cannot_get_uid%29
-
The fix for this is quite simple
Go to the command prompt…
vi /etc/group
add a line at the end using the same syntax as the line above it. Just use wheel as the group name and use a GID number that is not already used in the file.
Save it and restart the PHP service. The error will go away and you will be golden. -
Another fix will be : get the repaired pfSense version 2.2.4 …
-
Another fix will be : get the repaired pfSense version 2.2.4 …
Sounds definitely better than messing with screwed /etc/group manually.
-
I am getting a 500 internal server error with the latest version - 2.2.4 RELEASE.
Restarting PHP-FPM solved the issue, but does anyone know the root cause of the 500 error? I am seeing a lot of older threads coming up with that error and a couple posts above this one Gertjan says that this released fixed the 503 error.
Hopefully you have more information.
