similar to: error creating output file /var/lib/logrotate/logrotate.status.tmp: File exists

I had a system date problem when logrotate ran for the first time such that /var/lib/logrotate.status has: logrotate state -- version 2 "/var/log/yum.log" 1970-1-1-0:0:0 "/var/log/wtmp" 1970-1-1-0:0:0 "/var/log/chrony/*.log" 1970-1-1-0:0:0 "/var/log/spooler" 1970-1-1-0:0:0 "/var/log/btmp" 1970-1-1-0:0:0 "/var/log/maillog" 1970-1-1-0:0:0

I'm noticing that logrotate's default configuration for rotating /var/ log/secure and /var/log/messages partially fails if root's shell is set to /bin/tcsh (via chsh). (Running on CentOS 4.4; logrotate-3.7.1-5.RHEL4). What seems to be happening is that the logrotate.d/syslog postrotate command runs: /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null

Hi, I want to create a new log /var/log/maillog for postfix each day and so i created a new logrotate config for the log and removed it from /etc/logrotate.d/syslog. ~]# cat /etc/logrotate.d/maillog /var/log/maillog { daily rotate 31 start 1 compress create 0600 root postrotate /etc/init.d/postfix reload > /dev/null endscript } After

Hi all, I have a problem with logrotate and I don't know why. In /var/log/messages appears these errors: Apr 8 15:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 16:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 17:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 18:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8

The 2.04b rpm for rh60 ships with and installs a config file for logrotate (the samba.log file in the packaging/RedHat section). ===== /var/log/samba/log.nmb { postrotate /usr/bin/killall -HUP nmbd endrotate } /var/log/samba/log.smb { postrotate /usr/bin/killall -HUP smbd endrotate } ===== 1) I think that the use of "endrotate" is wrong. There is no

You may want to retry that after a make distclean, in case anything changed in the toolchain. -pd > On 6 Apr 2017, at 14:43 , Therneau, Terry M., Ph.D. <therneau at mayo.edu> wrote: > > This run was done this AM on my linux box, and older 32 bit Dell optiplex (core 2 duo). The failure message is at the very end. (It's due to be replaced in a couple of weeks.) The sequence

Dear all when I am login in terminal I am getting following message. declare -x ALL_PROXY="socks://hproxy.iitm.ac.in:3128/" declare -x AMBERHOME="/sware/amber/amber12" declare -x COLORTERM="gnome-terminal" declare -x CPPFLAGS="-I/usr/local/bin/include" declare -x

Ever since a recent power failure I have been getting a Logrotate error. My machine is on a UPS -- it shutdown cleanly, but I suspect that its BIOS/RTC battery is dead, since the machine came up thinking it was 1982 :-(. I reset the clock and everything is fine, *except* I had to delete Logrotate's state files (which had bad dates). But now Logrotate is raising the error: error: error

Has anyone had any success in getting Samba to correctly restart logging to the log files with the default logrotate setup (or even a modified one) from RedHat? The default setup is to move the files to another location, create a new file for Samba to fill, then send the daemons a HUP signal. I've tried some of the options that can be used in the logrotate.d/samba file (nocreate and

Howdy list, Hey does anyone know what the best cron job is to call logrotate to run the squid logrotations? -Or the subscribe address for a squid or logrotate mailing list (can't seem to find anything other than the usual MARC archives). I have this in /etc/logrotate.conf # rotate log files daily, they get too big otherwise, another story. daily # keep 8 weeks worth of backlogs e.g. 60

FYI. I have not been able to determine 100% that logrotate does this, but ulogd appears to stop logging whenever logrotate runs. So far, the only obvious commonality that I see is that logrotate ran and that the /var/log/ulogd/ulogd.syslogemu is completely empty until I restart ulogd. I have proven that the logging is broken by manually performing a network operation that Shorewall normally

Virtual networks can now be created and destroyed with a r/o filesystem. Signed-off-by: Michael Burns <mburns at redhat.com> --- common-post.ks | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/common-post.ks b/common-post.ks index 44a0270..5531e08 100644 --- a/common-post.ks +++ b/common-post.ks @@ -151,6 +151,7 @@ rm -f /etc/cron.daily/logrotate sed -i

Hi Y'all, We have nginx set up and we are having problems with logrotate. The permissions and users do not seem to be any different from other machines that are working ok however the /var/log/nginx does have a directory in there that we are using to collect some special log stuff. Could this subdirectory be interfering with the logrotate process? ta Andrew [root@ ~]# logrotate -d

Hi you could try a file /etc/logrotate.d/samba-local with this content /var/log/samba/log.samba-dcerpcd /var/log/samba/log.rpcd_classic /var/log/samba/log.rpcd_winreg /var/log/samba/log.samba-bgqd /var/log/samba/log.rpcd_spoolss { ?? ?weekly ?? ?missingok ?? ?rotate 7 ?? ?compress ?? ?delaycompress ?? ?notifempty } Le 27/11/2023 ? 10:12, Stefan G. Weichinger via samba a ?crit?: > Am

Hello, next week I'll install logrotate on a centos 4.4 server via yum. The man page says that the default mail command is /bin/mail -s, but there is no such binary on Centos. I do have mutt installed, however, so I would like to use it. Ideally, I would like to have logrotate send logs with mutt as attachments like this: mutt me at home.account -a compressed_log_file -s "here are

Hi all: logrotate is broken on my stock 4.1 install. After hunting and hunting I found there is a bug filed with Redhat on the issue. logrotate fails becasue my /tmp partition is mounted noexec. I understand it is that way for security reasons. The box in question is on a dedicated hosting site and that's the way it was handed off to me, built. Some said setting TMPDIR=/var/tmp;export

Dear All, Currently i am using CentOS 4.4 Linux Logrotate is not happen without -f option I have executed the following logrotate /etc/logrotate.conf manually and Logrotate command exit without any error messages If i executed with -f option then Logrotate will happen I am not sure why this is happening. Can some one throw light on this. Regards -S.Balaji

Am 28.03.23 um 10:40 schrieb Rowland Penny via samba: > > > On 28/03/2023 08:40, Arnaud FLORENT via samba wrote: >> Hello >> >> >> i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using >> www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository >> >> >> everything is running fine but i have few log files in /var/log/samba/

On 28/03/2023 08:40, Arnaud FLORENT via samba wrote: > Hello > > > i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using > www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository > > > everything is running fine but i have few log files in /var/log/samba/ > are not handl by /etc/logrotate.d/samba > > log.samba-dcerpcd > >

Anyone having problems with logrotate and CentOS 5.4? Although I have /etc/logrotate.d/mail (contents below) to rotate my maillog file, it fails to do it automatically: /var/log/maillog { compress dateext maxage 365 rotate 60 size=+1024k missingok postrotate /etc/init.d/MailScanner restart endscript } ++++++++++++++++++++++++++++ logrotate.conf: