NewSysLog | Crontab
Dear list, I have this issue with bzip2 and the generation of backup logfiles. This is the error I get: --- cut --- bzip2: I/O or other error, bailing out. Possible reason follows. bzip2: No such file or directory Input file = /var/log/all.log.0, output file = /var/log/all.log.0.bz2 newsyslog: `bzip2 -f /var/log/all.log.0' terminated with a non-zero status (1) bzip2: Can't open input file /var/log/maillog.0: No such file or directory. newsyslog: `bzip2 -f /var/log/maillog.0' terminated with a non-zero status (1) --- cut --- Can you tell me what goes wrong here and how to solve this? thanks in advance, Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
NewSysLog | Crontab
Dear list, I have this issue with bzip2 and the generation of backup logfiles. This is the error I get: --- cut --- bzip2: I/O or other error, bailing out. Possible reason follows. bzip2: No such file or directory Input file = /var/log/all.log.0, output file = /var/log/all.log.0.bz2 newsyslog: `bzip2 -f /var/log/all.log.0' terminated with a non-zero status (1) bzip2: Can't open input file /var/log/maillog.0: No such file or directory. newsyslog: `bzip2 -f /var/log/maillog.0' terminated with a non-zero status (1) --- cut --- Can you tell me what goes wrong here and how to solve this? thanks in advance, Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NewSysLog | Crontab
On 26/05/2012 12:02, Jos Chrispijn wrote: I have this issue with bzip2 and the generation of backup logfiles. This is the error I get: --- cut --- bzip2: I/O or other error, bailing out. Possible reason follows. bzip2: No such file or directory Input file = /var/log/all.log.0, output file = /var/log/all.log.0.bz2 newsyslog: `bzip2 -f /var/log/all.log.0' terminated with a non-zero status (1) bzip2: Can't open input file /var/log/maillog.0: No such file or directory. newsyslog: `bzip2 -f /var/log/maillog.0' terminated with a non-zero status (1) --- cut --- Can you tell me what goes wrong here and how to solve this? The underlying problem seems to be problems writing to /var/log. Is the partition (/var probably) full up or out of inodes? df -ih /var/log Also, look at the console to see if anything has been logged there. If it isn't running out of space, then check that the directory hasn't got weird flags settings: ls -laoR /var/log Having something like noschg set on the directory would cause the observed symptoms, but I am at a loss to understand how on earth anything like that could come about. There are a couple of other things it might be, but it's quite unlikely you wouldn't get crashes, coredumps and other signs of the end-times should any of those be the case. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: NewSysLog | Crontab
Hi Matthew, Thanks, will investigate this... best regards, Jos Matthew Seaman: On 26/05/2012 12:02, Jos Chrispijn wrote: I have this issue with bzip2 and the generation of backup logfiles. This is the error I get: --- cut --- bzip2: I/O or other error, bailing out. Possible reason follows. bzip2: No such file or directory Input file = /var/log/all.log.0, output file = /var/log/all.log.0.bz2 newsyslog: `bzip2 -f /var/log/all.log.0' terminated with a non-zero status (1) bzip2: Can't open input file /var/log/maillog.0: No such file or directory. newsyslog: `bzip2 -f /var/log/maillog.0' terminated with a non-zero status (1) --- cut --- Can you tell me what goes wrong here and how to solve this? The underlying problem seems to be problems writing to /var/log. Is the partition (/var probably) full up or out of inodes? df -ih /var/log Also, look at the console to see if anything has been logged there. If it isn't running out of space, then check that the directory hasn't got weird flags settings: ls -laoR /var/log Having something like noschg set on the directory would cause the observed symptoms, but I am at a loss to understand how on earth anything like that could come about. There are a couple of other things it might be, but it's quite unlikely you wouldn't get crashes, coredumps and other signs of the end-times should any of those be the case. Cheers, Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NewSysLog | Crontab
On 26/05/2012 18:41, Jos Chrispijn wrote: Thanks, will investigate this... Keeping the list in the loop... % df -ih /var/log Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/ada0p2 453G 5.8G 411G 1% 468k 29M 2% / One big partition for the whole OS? % ls -laoR /var/log total 448 drwxr-xr-x 5 rootwheel- 1024 May 26 00:00 . drwxr-xr-x 23 rootwheel- 512 May 17 19:57 .. drwx-- 2 rootwheel- 512 May 22 23:30 .spamassassin -rw-r--r-- 1 rootwheel- 1 May 23 16:04 Minimalist.log -rw--- 1 rootwheel-60 May 26 00:00 all.log -rw--- 1 rootwheel-14 May 26 00:00 all.log.0.bz2 -rw--- 1 rootwheel-14 May 25 00:00 all.log.2.bz2 -rw--- 1 rootwheel-14 May 24 00:00 all.log.4.bz2 -rw--- 1 rootwheel-14 May 23 00:00 all.log.6.bz2 Oooh, fun. None of the obvious ideas were right, and this is looking really quite mysterious. You've only got even numbered versions of all.log backups, but they are spaced 1 day apart, which is the usual recycle timing for all.log. However, there's not much in your all.log at all. It should get at least a message every 5 minutes assuming it's configured. Did you turn on the all.log in /etc/syslogd.conf at all? Or do those 60 bytes in all.log just say something very much like this: # cat /var/log/all.log May 26 00:00:00 lucid-nonsense newsyslog[23677]: logfile turned over (obviously, with your hostname instead and a different PID for newsyslog, and maybe a different date.) In which case, you're not actually logging anything to all.log at all, and you could just make the whole thing go away by: # cd /var/log # rm all.log* But that's no fun at all, and doesn't go anywhere towards explaining why you only get even numbered backups. Can we check a few things please? * Have you modified /etc/newsyslog.conf at all? Or /etc/syslogd.conf ? What does this command return for you? % grep all.log /etc/syslog.conf /etc/newsyslog.conf * What happens when you run the following sequence of commands: # cd /var/log # echo test foo # bzip2 -f foo || echo $? # ls -la foo* (using script(1) to capture a console transcript would be a good thing here.) Assuming you end up with a foo.bz2 file 45 bytes long, then you should also be able to do this: # bzcat foo.bz2 test * What version of FreeBSD is this, how did you install it and have you applied any patches or made any unusual configuration choices or modifications to the system? Is there anything out of the ordinary with your hardware or the setup on the machine that you think might be relevant? Does it have any history of problems? Did anything about the system change recently? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: NewSysLog | Crontab
From owner-freebsd-questi...@freebsd.org Sat May 26 15:55:21 2012 Date: Sat, 26 May 2012 21:51:37 +0100 From: Matthew Seaman matt...@freebsd.org To: Jos Chrispijn j...@webrz.net Cc: freebsd-questions@freebsd.org Subject: Re: NewSysLog | Crontab On 26/05/2012 18:41, Jos Chrispijn wrote: Thanks, will investigate this... Keeping the list in the loop... % df -ih /var/log Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/ada0p2 453G 5.8G 411G 1% 468k 29M 2% / One big partition for the whole OS? % ls -laoR /var/log total 448 drwxr-xr-x 5 rootwheel- 1024 May 26 00:00 . drwxr-xr-x 23 rootwheel- 512 May 17 19:57 .. drwx-- 2 rootwheel- 512 May 22 23:30 .spamassassin -rw-r--r-- 1 rootwheel- 1 May 23 16:04 Minimalist.log -rw--- 1 rootwheel-60 May 26 00:00 all.log -rw--- 1 rootwheel-14 May 26 00:00 all.log.0.bz2 -rw--- 1 rootwheel-14 May 25 00:00 all.log.2.bz2 -rw--- 1 rootwheel-14 May 24 00:00 all.log.4.bz2 -rw--- 1 rootwheel-14 May 23 00:00 all.log.6.bz2 Oooh, fun. None of the obvious ideas were right, and this is looking really quite mysterious. You've only got even numbered versions of all.log backups, but they are spaced 1 day apart, which is the usual recycle timing for all.log. This is a clear-cut indication of _two_ processes running that rotate the logfiles. The first process to run works, and the second one bitches and moans, and -quits- (with the error shown about not being able to find the file original file to compress) *after* having rened the 1st back-up to the 2nd name. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
