Web Gui not loading after full disk
-
I had an issue where I left a packet capture running and it consumed the remaining 37GB of space on the file system. I noticed the problem when I couldn't log into the web gui but could log in via SSH. Of course this led to the config.xml file corrupting to just 10% of its size. I removed the packet capture and replaced the config.xml with one from the backup a day or two ago. I can still access via SSH but the web gui isn't loading at all. From the SSH access I've tried both 11) Restart WebConfigurator and 16) Restart PHP-FPM
What can I check to get it back up and running again so I can log in? I'd prefer not to reboot as it will kill the network but I can do it as a last resort.
-
OK. I'm back at the point that the web gui is up but the password that works for the CLI isn't working in the GUI. Is there a service that needs to be started or something for the web gui login to work or match the cli login?
-
The admin/root password should be the same on both. Unless maybe it's different on the config you restored?
I would probably try a re-root if you cannot do a full reboot. There will still be some disruption but it's far quicker.
-
@stephenw10 What is the risk that I won't be able to get back in? I have a forward from my IP on an off port that redirects to the internal login page. That isn't working so the NAT rules aren't loading at the moment (or at least that one).
-
There is always a risk but normally filling the filesystem doesn't do anything permanently. Services that require disk access start to fail and eventually you end up with only the base functionality.
I'd want to have a recovery strategy in place though. Better to be safe.
Steve
-
@stephenw10 The password did change yesterday afternoon. That could be it. It'll all pick back up after a reboot?
-
@stephenw10 I have a spare unit here that I'm restoring the config to. Once I've verified that's good then I can do the reroot/reboot.
-
@stewart said in Web Gui not loading after full disk:
The password did change yesterday afternoon. That could be it. It'll all pick back up after a reboot?
Which password is the CLI now accepting?
You could try running
/etc/rc.reload_allto force the restored config to reload.
If you manually copied it into place that may not have happened.Steve
-
@stephenw10 The CLI was accepting the new PW. The GUI was accepting no combinations of usernames and passwords. OpenVPN was the same. A re-root fixed the issue. I've only ever rebooted. I didn't realize a re-root doesn't take down the network. Anyone that was working fine never noticed anything. Is there a good rule of thumb for when to reboot and when to re-root?
-
Not really beyond this: https://docs.netgate.com/pfsense/en/latest/diagnostics/system-reboot.html#reboot-methods
-
@stephenw10 Yeah, I read that but it doesn't really give case scenarios. I appreciate the help.
