Disk full because of log file
-
you can also turn off the ping hosts feature altogether.
-
Thank you for this information.
But how can I do that ? I don’t find.And isn’t this ping host feature used to see green light in front of the host ?
-
But how can I do that ? I don’t find.
Web Interface -> FOG Configuration -> FOG Settings -> General Settings -> FOG_HOST_LOOKUPAnd isn’t this ping host feature used to see green light in front of the host ?
Yes.
-
ok thank you
I should open my eyes
-
The @ in front of a function simply surpresses the warning. Tom disabled that to have more verbose output to work it to make it easier to resolve problems.
-
@Quazz I also did it because there were a lot of calls using the @ symbol. Using @ in front of functions is actually very taxing on the server too.
-
@Tom-Elliott said in Disk full because of log file:
@Quazz I also did it because there were a lot of calls using the @ symbol. Using @ in front of functions is actually very taxing on the server too.
Yes I first want to preserve my disk space
But pinging host is very usefull.So I don’t know how to solve these warnings, I’m not a php programmer.
It seems that timeout in fsockopen function doesn’t work for offline hosts -
I’ve added some minor code in hope to help thwart the spamming of the log with these fclose warnings. Typically, there should be plenty of space for the root partition (/) to write its log files. What is your FOG OS’s partition layout?
df -h -
@Tom-Elliott
Images are on a separate partition.
/ partition is 12 Go, today I can see 5 Go free.
This is enough, but not when dozens of lines per second are written in log file.
And whit this one (ping), 2 warning messages are written for each host not on line.
It can grow rapidly. -
You could disable logging, though I’d highly recommend against it.
-
@Tom-Elliott
Maybe disable only warnings messages ?
So I mark this resolved
Thanks
