On Monday, 3 August 2020 07:58:03 BST Bertram Scharpf wrote:
> Hi,
>
> I detected that since mid-May my main log files
> /var/log/{messages,auth.log,daemon.log,...}
> don't get rotated any more.
>
> I tried to solve this by making an entry in
> /etc/logrotate.conf, but that doesn't work.
> "maxsi
Hi,
I detected that since mid-May my main log files
/var/log/{messages,auth.log,daemon.log,...}
don't get rotated any more.
I tried to solve this by making an entry in
/etc/logrotate.conf, but that doesn't work.
"maxsize" works, but not "weekly" nor "daily".
What happened in May and what do I ha
On Sun, 12 Feb 2017 21:26:51 -0600, Dale wrote:
> >> Thanks Alexander, it pays going back to basics ... for some reason my
> >> cronie service was not running. o_O
> >>
> >> I added it to default runlevel and hopefully it will do its magic
> >> from now on.
> > I'm glad I'm not the only one pro
Peter Humphrey wrote:
> On Sunday 12 Feb 2017 17:32:30 Mick wrote:
>
>> Thanks Alexander, it pays going back to basics ... for some reason my
>> cronie service was not running. o_O
>>
>> I added it to default runlevel and hopefully it will do its magic from now
>> on.
> I'm glad I'm not the only o
On Sunday 12 Feb 2017 17:32:30 Mick wrote:
> Thanks Alexander, it pays going back to basics ... for some reason my
> cronie service was not running. o_O
>
> I added it to default runlevel and hopefully it will do its magic from now
> on.
I'm glad I'm not the only one prone to this kind of thing
On Sunday 12 Feb 2017 19:11:23 Alexander Kapshuk wrote:
> On Sun, Feb 12, 2017 at 6:57 PM, Mick wrote:
> > I am perplexed why box of mine will not logrotate system logs, which have
> > now grown into gigs. kern.log, syslog, messages, etc. are eating up
> > space unconstrained, to the point where
On Sun, Feb 12, 2017 at 6:57 PM, Mick wrote:
> I am perplexed why box of mine will not logrotate system logs, which have now
> grown into gigs. kern.log, syslog, messages, etc. are eating up space
> unconstrained, to the point where the partition run out of it.
>
> Trying to run /etc/cron.daily/l
I am perplexed why box of mine will not logrotate system logs, which have now
grown into gigs. kern.log, syslog, messages, etc. are eating up space
unconstrained, to the point where the partition run out of it.
Trying to run /etc/cron.daily/logrotate from a terminal does not show anything
in m
On Sat, 2 Apr 2016 08:51:30 +0200, Alan McKinnon wrote:
> > Exactly, and that's why there needs to be some sort of place holder
> > for the file name.
> I don't think it's a case of "there needs to be".
> I think it's more a case of "you want it to be to solve this special
> problem you have", an
On 02/04/2016 04:01, lee wrote:
>> It depends. There are options to tell logrotate to use, or not use,
>> > dates in the new filename, and what compression to use or not use. So
>> > the names can vary.
> Exactly, and that's why there needs to be some sort of place holder for
> the file name.
>
Alan McKinnon writes:
> On 25/03/2016 13:46, lee wrote:
>>
>> Hi,
>>
>> is there a built-in way (like a place holder) to figure out what name a
>> rotated log file has been given by logrotate?
>>
>> Here's what I'm trying to do:
>>
>>
>> , [ cat /etc/logrotate.d/exim }
>> | /var/log/exim
On 25/03/2016 13:46, lee wrote:
>
> Hi,
>
> is there a built-in way (like a place holder) to figure out what name a
> rotated log file has been given by logrotate?
>
> Here's what I'm trying to do:
>
>
> , [ cat /etc/logrotate.d/exim }
> | /var/log/exim/exim*.log {
> | daily
> |
Hi,
is there a built-in way (like a place holder) to figure out what name a
rotated log file has been given by logrotate?
Here's what I'm trying to do:
, [ cat /etc/logrotate.d/exim }
| /var/log/exim/exim*.log {
| daily
| missingok
| rotate 800
| compress
|
Am 28.08.2011 20:44, schrieb Florian Philipp:
> Am 28.08.2011 13:14, schrieb Mick:
>> On Sunday 07 Aug 2011 16:20:18 Florian Philipp wrote:
>>> Am 07.08.2011 02:22, schrieb Mick:
On Friday 05 Aug 2011 23:08:38 Neil Bothwick wrote:
> On Fri, 05 Aug 2011 17:59:00 +0200, Florian Philipp wrote
Am 28.08.2011 13:14, schrieb Mick:
> On Sunday 07 Aug 2011 16:20:18 Florian Philipp wrote:
>> Am 07.08.2011 02:22, schrieb Mick:
>>> On Friday 05 Aug 2011 23:08:38 Neil Bothwick wrote:
On Fri, 05 Aug 2011 17:59:00 +0200, Florian Philipp wrote:
> Yes, this was introduced in 3.8.0 to fix sec
On Sunday 07 Aug 2011 16:20:18 Florian Philipp wrote:
> Am 07.08.2011 02:22, schrieb Mick:
> > On Friday 05 Aug 2011 23:08:38 Neil Bothwick wrote:
> >> On Fri, 05 Aug 2011 17:59:00 +0200, Florian Philipp wrote:
> >>> Yes, this was introduced in 3.8.0 to fix security issues [1]. Change
> >>> your co
On Sunday 07 Aug 2011 16:20:18 Florian Philipp wrote:
> Am 07.08.2011 02:22, schrieb Mick:
> > On Friday 05 Aug 2011 23:08:38 Neil Bothwick wrote:
> >> On Fri, 05 Aug 2011 17:59:00 +0200, Florian Philipp wrote:
> >>> Yes, this was introduced in 3.8.0 to fix security issues [1]. Change
> >>> your co
Am 07.08.2011 02:22, schrieb Mick:
> On Friday 05 Aug 2011 23:08:38 Neil Bothwick wrote:
>> On Fri, 05 Aug 2011 17:59:00 +0200, Florian Philipp wrote:
>>> Yes, this was introduced in 3.8.0 to fix security issues [1]. Change
>>> your config to look like this:
>>> /var/log/portage/elog/summary.log {
On Friday 05 Aug 2011 23:08:38 Neil Bothwick wrote:
> On Fri, 05 Aug 2011 17:59:00 +0200, Florian Philipp wrote:
> > Yes, this was introduced in 3.8.0 to fix security issues [1]. Change
> > your config to look like this:
> > /var/log/portage/elog/summary.log {
> > su portage portage
> > ...
> > }
>
On Fri, 05 Aug 2011 17:59:00 +0200, Florian Philipp wrote:
> Yes, this was introduced in 3.8.0 to fix security issues [1]. Change
> your config to look like this:
> /var/log/portage/elog/summary.log {
> su portage portage
> ...
> }
>
> Disclaimer: I've not really tried this (yet) but I think I'm
Am 05.08.2011 17:22, schrieb Jarry:
> Hi,
> today I received this mail from cron:
> ---
> error: skipping "/var/log/portage/elog/summary.log" because
> parent directory has insecure permissions (It's world writable
> or writable by group which is not "root") Set "su" directive
> in config file to t
Hi,
today I received this mail from cron:
---
error: skipping "/var/log/portage/elog/summary.log" because
parent directory has insecure permissions (It's world writable
or writable by group which is not "root") Set "su" directive
in config file to tell logrotate which user/group should be
used for
On Thu, Jul 28, 2011 at 13:39, Pandu Poluan wrote:
> On Thu, Jul 28, 2011 at 13:34, Walter Dnes wrote:
>> One more question... when you ran "emerge --sync", did you see a
>> message telling you to update portage immediately? When you see that
>> message, do it right away before updating anythin
On Thu, Jul 28, 2011 at 13:34, Walter Dnes wrote:
> One more question... when you ran "emerge --sync", did you see a
> message telling you to update portage immediately? When you see that
> message, do it right away before updating anything else.
>
> --
> Walter Dnes
>
My `emerge --sync` happe
One more question... when you ran "emerge --sync", did you see a
message telling you to update portage immediately? When you see that
message, do it right away before updating anything else.
--
Walter Dnes
On Thu, Jul 28, 2011 at 11:43:46AM +0700, Pandu Poluan wrote
> (app-admin/logrotate-3.7.9-r2::gentoo, installed) pulled in by
> app-admin/logrotate required by (net-proxy/squid-3.1.8::gentoo, installed)
> app-admin/logrotate required by @selected
>
> (sys-apps/portage-2.2.0_alpha47::g
Tried `emerge -avuND @world` and found out that logrotate blocks portage :
Total: 17 packages (13 upgrades, 1 downgrade, 2 new, 1 in new slot),
Size of downloads: 39,167 kB
Conflict: 1 block (1 unsatisfied)
* Error: The above package list contains packages which cannot be
* installed at the sam
* Helmut Jarausch wrote:
> On 07/12/10 11:00:00, Enrico Weigelt wrote:
> > do you have the process accounting deamon running ?
>
> No, and I've never done so.
Thats why the logfile is missing ;-)
If you dont have that daemon running (and so nobody write to that
logfile), you could simply remov
On 07/12/10 11:00:00, Enrico Weigelt wrote:
> * Helmut Jarausch wrote:
> > Hi,
> >
> > since a few days logrotate is failing due to
> > error: stat of /var/account/pacct failed: No such file or directory
>
> do you have the process accounting deamon running ?
No, and I've never done so.
>
>
* Helmut Jarausch wrote:
> Hi,
>
> since a few days logrotate is failing due to
> error: stat of /var/account/pacct failed: No such file or directory
do you have the process accounting deamon running ?
did you instruct logrotate to create this logfile if missing ?
cu
--
Hi,
since a few days logrotate is failing due to
error: stat of /var/account/pacct failed: No such file or directory
What has changed, what am I missing?
Many thanks for a hint,
Helmut.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
2010/5/10 Alan McKinnon :
> Please hash out all the lines in the denyhosts rotate file and run
> "logrotate -d /etc/logrotate.conf"
> Then let's see what error comes up.
>
> --
> alan dot mckinnon at gmail dot com
>
>
I hit the same problem few days ago but I didn't look for a solution
until today
On Monday 10 May 2010 11:40:29 Helmut Jarausch wrote:
> On 10 May, Alan McKinnon wrote:
> > On Monday 10 May 2010 09:46:11 Helmut Jarausch wrote:
> >> Hi,
> >> I have the following file as /etc/logrotate.d/denyhosts
> >> /var/log/denyhosts {
> >>
> >>missingok
> >>notifempty
> >>create
On 10 May, Alan McKinnon wrote:
> On Monday 10 May 2010 09:46:11 Helmut Jarausch wrote:
>> Hi,
>> I have the following file as /etc/logrotate.d/denyhosts
>> /var/log/denyhosts {
>> missingok
>> notifempty
>> create 0640 root root
>> sharedscripts
>> prerotate
>>
On Monday 10 May 2010 09:46:11 Helmut Jarausch wrote:
> Hi,
> I have the following file as /etc/logrotate.d/denyhosts
> /var/log/denyhosts {
> missingok
> notifempty
> create 0640 root root
> sharedscripts
> prerotate
> /etc/init.d/denyhosts stop
>
Hi,
I have the following file as /etc/logrotate.d/denyhosts
/var/log/denyhosts {
missingok
notifempty
create 0640 root root
sharedscripts
prerotate
/etc/init.d/denyhosts stop
endscript
postrotate
/etc/init.d/den
On Friday 26 September 2008 09:49:57 Kaushal Shriyan wrote:
> Hi,
>
> I am using logrotate utility on gentoo to compress catalina.out file.
[snip]
> error: unable to open /var/log/tomcat5/catalina.out.1 for compression
First thing to check is that the user doing this operation has write
permis
Hi,
I am using logrotate utility on gentoo to compress catalina.out file. when i
run it using debug mode, I get
#/usr/sbin/logrotate -dv /usr/local/bin/scripts/logrotate-tomcat5-catalina.conf
reading config file /usr/local/bin/scripts/logrotate-tomcat5-catalina.conf
reading config info for /var/
Hi All,
I have noticed that the log files on a box of mine are getting larger than
expected. I ran logrotate by hand to see if I get any errors and this came
up:
# logrotate -f /etc/logrotate.conf
error: line too long in state file /var/lib/logrotate.status
# ls -la /var/lib/logrotate.status
On Tue, 25 Sep 2007 12:36:57 +0100
Neil Bothwick wrote:
> On Tue, 25 Sep 2007 12:06:09 +0200, Arnau Bria wrote:
>
[...]
> blog_log_access_common does not match the *log pattern in the config
> file.
You're completely right...
apache2/access_fotos.emergetux.net_log apache2/blog_log_access_c
On Tue, 25 Sep 2007 12:06:09 +0200, Arnau Bria wrote:
> I have this in my logroate.d/apache
> # Apache2 logrotate snipet for Gentoo Linux
> # Contributes by Chuck Short
> #
> /var/log/apache2/*log {
> daily
> missingok
> notifempty
> size 5M
> sharedscripts
> postrotate
> /etc/init.d/
Hi,
I have this in my logroate.d/apache
# Apache2 logrotate snipet for Gentoo Linux
# Contributes by Chuck Short
#
/var/log/apache2/*log {
daily
missingok
notifempty
size 5M
sharedscripts
postrotate
/etc/init.d/apache2 reload > /dev/null 2>&1 || true
endscript
}
And my logs are:
#
On Mon, 13 Aug 2007 08:19:17 -0700
James Ausmus wrote:
> On 8/13/07, Arnau Bria <[EMAIL PROTECTED]> wrote:
> > On Mon, 13 Aug 2007 07:18:49 -0700
> > James Ausmus wrote:
> >
> > > On 8/13/07, Arnau Bria <[EMAIL PROTECTED]> wrote:
> > [...]
> > > Just a stab in the dark - do you have your cron serv
On 8/13/07, Arnau Bria <[EMAIL PROTECTED]> wrote:
> On Mon, 13 Aug 2007 07:18:49 -0700
> James Ausmus wrote:
>
> > On 8/13/07, Arnau Bria <[EMAIL PROTECTED]> wrote:
> [...]
> > Just a stab in the dark - do you have your cron service running? Can
> > you test that it properly runs other cron scripts
On Mon, 13 Aug 2007 07:18:49 -0700
James Ausmus wrote:
> On 8/13/07, Arnau Bria <[EMAIL PROTECTED]> wrote:
[...]
> Just a stab in the dark - do you have your cron service running? Can
> you test that it properly runs other cron scripts?
Yep, cause I have 5 gziped log files, so I works until the fi
On 8/13/07, Arnau Bria <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have my logrotate configured but it does not work propertly.
> I have logrotate in crontab:
> # crontab -l
> [...]
> 2 0 * * * /usr/sbin/logrotate /etc/logrotate.conf
Just a stab in the dark - do you have your cron service runnin
Hi,
I have my logrotate configured but it does not work propertly.
Let me explain:
mail # ls -lsah
total 20M
4,0K drw--- 2 root root 4,0K ago 13 03:10 .
4,0K drwxr-xr-x 15 root root 4,0K ago 13 03:10 ..
15M -rw--- 1 root root 15M ago 13 12:38 mail.log
2,4M -rw--- 1 root root 2,4M
On 8/5/07, Mick <[EMAIL PROTECTED]> wrote:
> I am not sure I understand "that doesn't work":
>
> It does not rotate the message log file at all?
> It rotates it but does not create a new empty message log file after rotation?
Thanks for your reply and sorry for answering so late.
rotating the logs
On Sunday 05 August 2007 08:36, Jakob wrote:
> Thanks for that hint, but there was nothing about logrotate in dead.letter.
> logrotate itself works fine for me but I want the messages file erased
> after rotating and start with a new file and that doesn't work.
> any more ideas?
I am not sure I u
> Look for a dead.letter file in /root which may contain any errors of the
> logrotate script. In my system there is /etc/logrotate.d/syslog-ng which
> contains:
> ===
> #
> $Header:
> /var/cvsroot/gentoo-x86/app-admin/syslog-ng/files/syslog-ng.logrotate,v
> 1.2 20
On Saturday 04 August 2007 09:29, Jakob wrote:
> > from LOGROTATE(8):
> >
> > Here is more information on the directives which may be included in a
> > logrotate configuration file:
> >
> > [...]
> >
> > copy Make a copy of the log file, but don't change the original at
> > all
> from LOGROTATE(8):
>
> Here is more information on the directives which may be included in a
> logrotate configuration file:
>
> [...]
>
> copy Make a copy of the log file, but don't change the original at
> all. This option can be used, for instance, to make a snapshot
>
2007/8/3, Jakob <[EMAIL PROTECTED]>:
> Hi all,
>
> I'm running logrotate on my homeserver and the logs are rotated
> correctly but after rotating it should create new empty log files and
> that doesnt work.
>
> here are my confs:
> /etc/logrotate.conf:
> # $Header: /var/cvsroot/gentoo-x86/app-admin
Jakob wrote:
> Hi all,
>
> I'm running logrotate on my homeserver and the logs are rotated
> correctly but after rotating it should create new empty log files and
> that doesnt work.
>
> here are my confs:
> /etc/logrotate.conf:
> # $Header: /var/cvsroot/gentoo-x86/app-admin/logrotate/files/logrota
Hi all,
I'm running logrotate on my homeserver and the logs are rotated
correctly but after rotating it should create new empty log files and
that doesnt work.
here are my confs:
/etc/logrotate.conf:
# $Header: /var/cvsroot/gentoo-x86/app-admin/logrotate/files/logrotate.conf,v
1.2 2004/07/18 01:5
Hi All,
I do not understand why the log files within /var/log/portage/ will
not rotate on my PC, while they rotate fine on my laptop. The
/etc/logrotate.conf is the same on both boxen:
==
# rotate log files weekly
weekly
#daily
# keep 4 weeks worth of bac
Uwe Thiem wrote:
On 03 August 2005 12:11, Etaoin Shrdlu wrote:
On Wednesday 03 August 2005 12:54, Uwe Thiem wrote:
Hi folks,
from /etc/logrotate.conf:
-
# no packages own lastlog or wtmp -- we'll rotate them here
/var/log/wtmp {
monthly
create 0664 root utmp
rotate 1
}
-
On Wednesday 03 August 2005 16:10, Uwe Thiem wrote:
> Are you sure you aren't using it? Have you looked into
> /etc/cron.daily?
Yes, I'm sure.
# emerge -s logrotate
* app-admin/logrotate
Latest version available: 3.7.1-r1
Latest version installed: [ Not Installed ]
Size of d
On 03 August 2005 12:11, Etaoin Shrdlu wrote:
> On Wednesday 03 August 2005 12:54, Uwe Thiem wrote:
> > Hi folks,
> >
> > from /etc/logrotate.conf:
> >
> > -
> > # no packages own lastlog or wtmp -- we'll rotate them here
> > /var/log/wtmp {
> > monthly
> > create 0664 root utmp
> >
On Wednesday 03 August 2005 12:54, Uwe Thiem wrote:
> Hi folks,
>
> from /etc/logrotate.conf:
>
> -
> # no packages own lastlog or wtmp -- we'll rotate them here
> /var/log/wtmp {
> monthly
> create 0664 root utmp
> rotate 1
> }
> -
>
> It states it rotates lastlog (/var/log/la
Hi folks,
from /etc/logrotate.conf:
-
# no packages own lastlog or wtmp -- we'll rotate them here
/var/log/wtmp {
monthly
create 0664 root utmp
rotate 1
}
-
It states it rotates lastlog (/var/log/lastlog) but it doesn't and my lastlog
grows forever. Doesn't seem right. Anybo
61 matches
Mail list logo
