Re: logrotate problem

2014-10-08 Thread Catalin Soare
On Oct 6, 2014 11:00 PM, "Michael Grant" wrote: > > I think I've tracked this down to rsyslogd being updated a few days ago and it not restarting. > > So I tried to restart it by hand with /etc/init.d/rsyslogd restart but it failed to stop. So trying to understand why it didn't stop, I tried runn

Re: logrotate problem

2014-10-06 Thread Michael Grant
I think I've tracked this down to rsyslogd being updated a few days ago and it not restarting. So I tried to restart it by hand with /etc/init.d/rsyslogd restart but it failed to stop. So trying to understand why it didn't stop, I tried running start-stop-daemon manually and here's what I see: #

Re: logrotate problem

2014-10-06 Thread Joe
On Mon, 6 Oct 2014 19:51:38 +0100 Michael Grant wrote: > When logrotate fired this month, almost all of my logs remain at zero > length and the .1 log continues to grow. For example: > > ls -l /var/log > ... > -rw-r- 1 root adm 0 Oct 5 06:25 messages > -rw-r- 1 root

logrotate problem

2014-10-06 Thread Michael Grant
When logrotate fired this month, almost all of my logs remain at zero length and the .1 log continues to grow. For example: ls -l /var/log ... -rw-r- 1 root adm 0 Oct 5 06:25 messages -rw-r- 1 root adm 4938 Oct 6 06:56 messages.1 ... -rw-r- 1 root ad

Apache+mod_chroot+logrotate problem?

2006-01-08 Thread Todd A. Jacobs
Apache failed to restart this morning when logrotate kicked in. I got the following error: [Sun Jan 8 06:25:39 2006] [notice] SIGUSR1 received. Doing graceful restart fopen: No such file or directory I'm assuming this is because whatever file it wanted didn't exist inside the chroot jai

RE: Logging/ Logrotate Problem

2003-03-11 Thread Stefan Drees
> -Ursprüngliche Nachricht- > Von: nate [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 10. März 2003 23:05 > An: [EMAIL PROTECTED] > Betreff: Re: Logging/ Logrotate Problem > > > Stefan Drees said: > > Hi, > > i have set up my first debian server and ev

Re: Logging/ Logrotate Problem

2003-03-10 Thread nate
Stefan Drees said: > Hi, > i have set up my first debian server and everything runs > fine, for one week :-(. The machine stops working, logcheck > consums must of the cpu time, because daemon.log and syslog > have grown up to 1GB in size. I deleted them, but a few hours > later they have grown up

Logging/ Logrotate Problem

2003-03-10 Thread Stefan Drees
Hi, i have set up my first debian server and everything runs fine, for one week :-(. The machine stops working, logcheck consums must of the cpu time, because daemon.log and syslog have grown up to 1GB in size. I deleted them, but a few hours later they have grown up to 10MB. Here are my questions:

Fwd: pleaz help with logrotate problem

2002-06-05 Thread José
E9?=" <[EMAIL PROTECTED]> >Priority: Normal >X-Mailer: PMMail 2000 Professional (2.20.2380) For Windows 2000 (5.0.2195;2) >MIME-Version: 1.0 >Content-Type: text/plain; charset="iso-8859-1" >Content-Transfer-Encoding: quoted-printable >Subject: pleaz help with

Re: pleaz help with logrotate problem

2002-06-04 Thread prover
From: "José" <[EMAIL PROTECTED]> To: Sent: Tuesday, June 04, 2002 2:20 PM Subject: pleaz help with logrotate problem > hi all, > > i use debian potato 2.2r4 with kernel 2.4.18 > > i want daemon.log rotated 1x per month and keep compressed files 6 months &

pleaz help with logrotate problem

2002-06-04 Thread José
hi all, i use debian potato 2.2r4 with kernel 2.4.18 i want daemon.log rotated 1x per month and keep compressed files 6 months so this is my logrotate.conf file : -- monthly

Re: logrotate problem?

2002-03-06 Thread Wayne Topa
Rick Pasotto([EMAIL PROTECTED]) is reported to have said: > My system is 99% woody. Yesterday I noticed that no entries were being > made to /etc/syslog but instead were being made to /etc/syslog.0. That > is still happening today. > > What has gone wrong? I reported that last month. No one resp

logrotate problem?

2002-03-06 Thread Rick Pasotto
My system is 99% woody. Yesterday I noticed that no entries were being made to /etc/syslog but instead were being made to /etc/syslog.0. That is still happening today. What has gone wrong? -- "Once the principle of government -- judicial monopoly and the power to tax -- is incorrectly accepted