Home > Error Bad > Error Bad Top Line In State File /var/lib/logrotate.status

Error Bad Top Line In State File /var/lib/logrotate.status

Acknowledgement sent to Ian Wienand : Extra info received and forwarded to list. Information forwarded to [email protected], Paul Martin : Bug#118466; Package logrotate. Cheers dawood dawood View Public Profile View LQ Blog View Review Entries View HCL Entries Visit dawood's homepage! Here is a stepped through example of the simple of case, of how logrotate decides to rotate a logfile (these are fedora paths, Ubuntu, Centos etc may be different) (I made useful reference

This guide describes how to confirm whether this issue is affecting your VPS and how to resolve the issue. Magento2 Applying Patches Why are there so many different amounts received when receiving a payment? Further, if the if statement with feof succeeded, then after this the value of errno is used out of context ... This did it for me.

Menu Skip navigation Menu Home Linux Smartphones & Gadgets Blog You are here:HomeLinuxError: bad top line in state file - logrotate.status ShareFacebook, Twitter, Google Plus, Pinterest, Email PrintPosted in:LinuxError: bad top Thank you for reporting the bug, which will now be closed. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Fill the log with more than 30k of data # ls -l /var/log/yum.log -rw------- 1 root root 49825 May 16 20:40 /var/log/yum.log 3. Browse other questions tagged logrotate or ask your own question. Create "gold" from lead (or other substances) Draw an ASCII chess board! Message #42 received at [email protected] (full text, mbox, reply): From: Paul Martin To: Ian Wienand , [email protected] Cc: [email protected] Subject: Re: Bug#118466: seg fault Date: Wed, 14 Nov 2001 00:49:06

I'll try to change the behaviour in case of status file error in the upstream version and then backport to RHEL. Although I couldn't find any record of that in the logrotate changelog. That would allow the problem to be fixed (the only way it can be fixed really) without an administrator intervention. Message #17 received at [email protected] (full text, mbox, reply): From: Paul Martin To: [email protected] Subject: Bug#118466: fixed in logrotate 3.5.9-2 Date: Wed, 07 Nov 2001 15:52:17 -0500 We believe that

Run logrotate again # logrotate /etc/logrotate.conf # (no errors this time) 8. Message #22 received at [email protected] (full text, mbox, reply): From: Ian Wienand To: [email protected] Subject: seg fault Date: Tue, 13 Nov 2001 11:03:22 +1100 [Message part 1 (text/plain, inline)] Hello, Standard way for novice to prevent small round plug from rolling away while soldering wires to it Which news about the second Higgs mode (or the mysterious particle) anticipated to be Privacy policy About Mithiwiki Disclaimers Log in October 10, 2016, 02:19:49 PM Welcome, Guest Please login or register. 1 Hour 1 Day 1 Week 1 Month Forever Login with username, password

on CentOS 7 Playposter - Manage your screen content from anywhere Extend SNMP - Run bash scripts via SNMP Zenoss - User-supplied Python expression ((here.speed or 1e9) / 8 * .75) see this Full text and rfc822 format available. UNIX is a registered trademark of The Open Group. Edit bug mail Other bug subscribers Subscribe someone else Bug attachments temp-logrotate-report (edit) Add attachment • Take the tour • Read the guide © 2004-2016 CanonicalLtd. • Terms of use

Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the http://axishost.net/error-bad/error-bad-return-status-for-module-build-on-kernel-ati.php that returns a non-zero when an end of file condition has *previously* occurred on [the argument] stream" seeing as nothing has happened to the file yet, there is no end of [email protected] + Closes: #188466 */ + + if (feof(f)) { + fclose(f); + f = NULL; + message(MESS_ERROR,"state file %s is zero length, starting afresh", + stateFilename); + } if (!f Full text and rfc822 format available.

A better solution would be to modify the logrotate cron script to first check that the clock is synchronized with ntpq / ntpdate. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. Essentially, the solution is to remove the status file as it will be regenerated on next logrotate run. this page I don't want to get lung cancer like you do Train and bus costs in Switzerland What are the drawbacks of the US making tactical first use of nuclear weapons against

this is why i think it doesn't work. Investigations Executing the following command returns an error: /mithi/mcs/bin/agent_mcs_logrotate.sh Executing the following commands also returns an error logrotate /mithi/mcs/modules/mithi-bl/binconf/mithi-bl.logrotate.sh The error can be either of the following two lines: error: bad Then logrotate now correctly rotates the file due to the date in the state file 2012-4-11 being more than a week ago from today 2012-5-11 # /usr/sbin/logrotate -d /etc/logrotate.d/httpd considering log

considering log /var/log/httpd/access_log log does not need rotating However if I run logrotate manually like so; # /usr/sbin/logrotate /etc/logrotate.d/httpd there is now an entry in the state file for the httpd

I'd noticed the corruption issue and put a fix in the tip of lp:ubuntu/upstart. I hope this can be fixed up; please critique my solution, I'm still learning. -ian [logrotate.c_zero_len.diff (text/plain, attachment)] Information forwarded to [email protected], Paul Martin : Bug#118466; Package logrotate. Can PostgreSQL databases be attached/detached on the fly? Copy sent to Paul Martin .

Please help us to make SME Server a better product. I know deleting the status file just makes logrotate recreate one next time referring to 1970, but I wonder if it gets restarted again it will not rotate properly because the Full text and rfc822 format available. Get More Info Isn't that more expensive than an elevated system?

Affecting: Canonical System Image Filed here by: Pat McGowan When: 2015-01-23 Confirmed: 2015-01-23 Started work: 2015-01-25 Completed: 2015-01-25 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux Currently the contents of the apache2 config file is as such. "/var/www/user/site.com/logs/*.log" { weekly missingok rotate 8 compress delaycompress notifempty create 640 root adm sharedscripts postrotate /etc/init.d/apache2 reload > /dev/null endscript Not the answer you're looking for? Message #59 received at [email protected] (full text, mbox, reply): From: Paul Martin To: [email protected] Subject: Bug#118466: fixed in logrotate 3.5.9-4 Date: Wed, 14 Nov 2001 15:02:32 -0500 We believe that

However, if the status file is corrupt, logrotate will never rewrite it and as such, no logrotation occurs leading to unlimited logfile growth. Is there an issue I'm not aware of with just using fstat (as in my patch?). sudo rm /var/lib/logrotate/status sudo /usr/sbin/logrotate -f /etc/logrotate.conf logrotate share|improve this question edited May 10 '12 at 21:31 asked May 10 '12 at 21:14 Malachi 2512718 add a comment| 4 Answers 4 Subscribing...