Cannot access System Logs (503 error)



  • Version 2.2.3 on a Supermicro C2558

    It started when I tried to do a packet capture on one of my FreeNAS jails (having a minor NAT port forwarding issue).

    I then stopped packet capture and attempted to view results and then the Web GUI suddenly displayed "503 - Service Unavailable" from my browser. I did, however, still have internet connectivity.

    I could no longer access Web GUI from my laptop. I tried rebooting via IPMI - no go. Restarted Web Config - no go. Resarted php-fpm - no go

    I then connected my phone to Wifi and tried accessing Web GUI - GO. So im like, cool, I can login from my phone, so maybe its a prob with my laptop. Tried restarting Laptop - no go.

    I searched the forums and it appears some users have mentioned BandwidthD being a potential culprit (I had the package installed but have never used it). So I attempted to uninstall package from the Web GUI on my phone and BAMM, now im getting a 503 error from my phone!!

    I then reboot again from IPMI and then restart php-fpm immediately followed by a Web config restart and GO!! Now I have access Web GUI from both my laptop and phone!!

    HOWEVER,

    I tried to view logs to see what the prob may be and I get another 503 error!! Except this time, its ONLY the system logs that give me the 503 error, everything else appears to be working fine. I then uninstall bandwidthd, restart pf again and am still getting the 503 error on the system log page, but nothing else.

    I dont even know how to approach this without being able to view the logs. Is there a way to view the logs from the shell?? Anyone have any ideas why its only the system logs? Is there a way to restart that service?

    EDIT: Im sure there is, Ill research that now, but want to get this thread out there now.

    EDITv2: My RAM usage is abnormally high at 67% of 4GB. Ive never seen it rise above 20%



  • Ok, now my RAM usage is approaching 91%, WTF!!?!? Looks like Snort may be going a lil crazy even though I already disabled it.

    Here's a screen shot of my system activity screen.

    Damn, nevermind. As I was just about to take the screenshot, I saw that snort finally disappeared from system activity screen. RAM usage is back down to normal around 8%.

    Still getting 503 error on System Log screen though  :o :o :o


  • Banned

    @TDJ211:

    I searched the forums and it appears some users have mentioned BandwidthD being a potential culprit (I had the package installed but have never used it). So I attempted to uninstall package from the Web GUI on my phone and BAMM, now im getting a 503 error from my phone!!

    I'd remove the evil package first:

    https://forum.pfsense.org/index.php?topic=90830.msg502489#msg502489



  • Soooooo

    After googling a bit I decided it was a waste of time banging my head into a wall and I should just do a full reinstall since I had just made a full config backup just the other night (whew!).

    After restoring everything, I checked System Logs menu and it appeared everything was back to normal. Well just a min ago, I checked my logs and I got the damned 503 error screen again!!  >:(

    Since I did a full reinstall, I knew it had to be on my end, so I completely cleared out all my cache, cookies, web browsing history, ect and it looks like that did it. I'm all good now!!  :D

    I still do think there was something screwy going on with pf though. But for anyone who may have a similar prob in the future, clean up your browser as well.



  • @doktornotor:

    @TDJ211:

    I searched the forums and it appears some users have mentioned BandwidthD being a potential culprit (I had the package installed but have never used it). So I attempted to uninstall package from the Web GUI on my phone and BAMM, now im getting a 503 error from my phone!!

    I'd remove the evil package first:

    https://forum.pfsense.org/index.php?topic=90830.msg502489#msg502489

    Thanks, yea I eventually did after I was able to get web GUI access back but it didnt do anything for the System Logs prob.


Log in to reply