Page 1 of 1

Upgrade Failing Due to Space Constraints

Posted: Wed Jun 22, 2016 11:44 am
by CarlWedu
our /usr/local/nagiosna/var/backend.log file is taking up alot of space on our server and our upgrade of the box is failing due to space constraints. recommendations for rectifying? thanks!

-rw-rw-r--+ 1 nna nnacmd 686137344 Jun 22 12:21 backend.log


# ./upgrade
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not get metalink https://mirrors.fedoraproject.org/metal ... rch=x86_64 error was
14: problem making ssl connection
* base: mirror.cs.pitt.edu
* epel: mirror.cs.pitt.edu
* extras: repo1.ash.innoscale.net
* updates: mirror.cs.pitt.edu
extras | 3.4 kB 00:00
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1097, in _retrieve
self.fo.write(buf)
IOError: [Errno 28] No space left on device

Current download cancelled, interrupt (ctrl-c) again within two seconds
to exit.

Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1097, in _retrieve
self.fo.write(buf)
IOError: [Errno 28] No space left on device

Re: Upgrade Failing Due to Space Constraints

Posted: Wed Jun 22, 2016 12:18 pm
by tgriep
You can delete the backend.log file to free up space on your system so you can upgrade it.
FYI, the log file was fixed in version Network Analyzer version 2R1.0 released on 03/04/2015 log rotations were added so upgrading should fix it for you.
Added daily log rotation for backend.log and 7 days to be kept -JO

Re: Upgrade Failing Due to Space Constraints

Posted: Wed Jun 22, 2016 12:50 pm
by CarlWedu
thank you!!

/resolve

Re: Upgrade Failing Due to Space Constraints

Posted: Wed Jun 22, 2016 12:58 pm
by mcapra
Closing this and marking as resolved