http:///service/ipxe/bg.png Error 0x3e11613b / Fog UI Stuck in Loop

[Wayne Workman]

@TomBagley said in http:///service/ipxe/bg.png Error 0x3e11613b / Fog UI Stuck in Loop:

@Wayne-Workman Yes, very nearly. I deleted because I was able to access the FOG UI eventually. How do I know what I can/can’t delete? Or should I be looking to rebuild onto a VM with more space?

I’d first start by looking for snapins that are in /opt/fog/snapins but are not in the web interface snapins management area, and delete the ones that shouldn’t be there.

There are some linux commands you can run to list all files sorted by size, I’ll see if I can find them.

[TomBagley]

@Wayne-Workman Thanks Wayne there was quite a lot not required so that’s got the root back to 20% available. The UI and Fog boot menu are more stable now but I am back to being stuck at ‘attempting to register host…’

[Quazz]

@TomBagley Could you make a new thread for that issue? Sounds like a different issue entirely, screenshots would be helpful as well

[TomBagley]

@Quazz Sure! Thanks for your help thus far.

[Wayne Workman]

@TomBagley What is the output of du -sh /var/log/httpd and the output of ls -laht /var/log/httpd/error_log

[TomBagley]

@Wayne-Workman

15G     /var/log/httpd

-rwxr-xr-x. 1 root root 1.3G Aug 10 14:32 /var/log/httpd/error_log

Thanks

[Tom Elliott]

@TomBagley Clean up the error log a bit.

Run: cat /dev/null > /var/log/httpd/error_log

[Wayne Workman]

@TomBagley There’s where your space is going. What is the output of ls -laht /var/log/httpd

[TomBagley]

@Tom-Elliott Have done, thanks for the tip.

@Wayne-Workman said in http:///service/ipxe/bg.png Error 0x3e11613b / Fog UI Stuck in Loop:

ls -laht /var/log/httpd

total 14G
-rwxr-xr-x. 1 root root  26M Aug 10 14:42 access_log
-rwxr-xr-x. 1 root root    0 Aug 10 14:42 error_log
-rwxr-xr-x. 1 root root 3.7G Aug  7 03:33 error_log-20160807
drwxr-xr-x. 9 root root 4.0K Aug  7 03:33 ..
drwxr-xr-x. 2 root root 4.0K Aug  7 03:33 .
-rwxr-xr-x. 1 root root 118M Aug  7 03:33 access_log-20160807
-rwxr-xr-x. 1 root root 9.2G Jul 31 03:09 error_log-20160731
-rwxr-xr-x. 1 root root 152M Jul 31 03:09 access_log-20160731
-rwxr-xr-x. 1 root root  992 Jul 25 03:36 error_log-20160725
-rwxr-xr-x. 1 root root 158M Jul 25 03:36 access_log-20160725
-rwxr-xr-x. 1 root root 1.3K Jul 17 03:37 error_log-20160717
-rwxr-xr-x. 1 root root 129M Jul 17 03:37 access_log-20160717
-rwxr-xr-x. 1 root root    0 May  6 09:18 ssl_access_log
-rwxr-xr-x. 1 root root    0 May  6 09:18 ssl_error_log
-rwxr-xr-x. 1 root root    0 May  6 09:18 ssl_request_log
[root@localhost ~]#

[Tom Elliott]

@TomBagley go ahead and remove the left over log too:

rm -rf error_log-20160731

[TomBagley]

@Tom-Elliott Thanks!

[Tom Elliott]

@Tom-Elliott One more you can clean up:

rm -rf error_log-20160807