On Sun, 2024-12-08 at 17:34 -0600, Roger Heflin wrote:
> So, full filesystem or read-only filesystem would seem to be the most likely.
Not full and not read-only, however it hasn't happened again in a few
weeks so I'm going to assume that some update has fixed whatever it
was.
Thanks.
poc
--
_
On Sun, 2024-12-08 at 23:20 +, Will McDonald wrote:
> On Sun, 8 Dec 2024 at 23:03, Patrick O'Callaghan
> wrote:
>
> > Dec 08 00:11:51 Bree logrotate[418079]: error: unable to open
> > /var/log/sssd/sssd_kcm.log-20241027 (read-only) for compression: Permission
>
logrotate as far I as I know runs as root, so selinux should not matter.
So, full filesystem or read-only filesystem would seem to be the most likely.
Corrupted filesystem/directory and/or directory that hit some odd fs
limitation (ext4 hashes files in a dir and when too many files hash
into a
On Sun, 8 Dec 2024 at 23:03, Patrick O'Callaghan
wrote:
> Dec 08 00:11:51 Bree logrotate[418079]: error: unable to open
> /var/log/sssd/sssd_kcm.log-20241027 (read-only) for compression: Permission
> denied
>
However:
>
> $ sudo ls -lZ /var/log/sssd/sssd_kcm.log-202410
]: Starting logrotate.service - Rotate log
files...
Dec 08 00:11:51 Bree logrotate[418079]: error: unable to open
/var/log/sssd/sssd_kcm.log-20241027 (read-only) for compression: Permission
denied
> On 22 Jul 2024, at 15:33, Paolo Galtieri wrote:
>
> I'm running syslog because that has what has always been running.
Unless you need specific syslog features journal is a big improvement.
The logs are records with fields, not just a string of text, that allows for
smarter searching for ex
I'm running syslog because that has what has always been running. This
was from before systemd. Why both rsyslog and syslog-ng were running I
have no idea. I did not intentionally start both, I assumed only one
would be running.
Paolo
On 7/21/24 01:15, Barry wrote:
On 21 Jul 2024, at 01
> On 21 Jul 2024, at 01:20, Paolo Galtieri wrote:
>
> Actually I have both running.
That will not work. Only one must be running.
Just to check; are you using syslog because systemd journal is not covering
your use-case?
If journal is sufficient then remove both the syslog daemons.
Barry
Actually I have both running.
Paolo
On 7/20/24 16:37, Todd Zullinger wrote:
Paolo Galtieri wrote:
It's interesting that both packages are available on F39.
Is there a reason to have both? And if only one should be
installed which?
It's not really different than having multiple web browsers
o
Paolo Galtieri wrote:
> It's interesting that both packages are available on F39.
> Is there a reason to have both? And if only one should be
> installed which?
It's not really different than having multiple web browsers
or desktop environments. Some folks like rsyslog, some like
syslog-ng. You
It's interesting that both packages are available on F39. Is there a
reason to have both? And if only one should be installed which?
Paolo
On 7/20/24 14:27, Todd Zullinger wrote:
Go Canes wrote:
On Sat, Jul 20, 2024 at 3:49 PM Paolo Galtieri wrote:
I wonder then if this is an issue due to
Go Canes wrote:
> On Sat, Jul 20, 2024 at 3:49 PM Paolo Galtieri wrote:
>>
>> I wonder then if this is an issue due to dnf upgrade? I've used dnf
>> upgrade to upgrade my system since at least F35. I wonder if at some
>> point there was a syslog file which then became rsyslog and the old
>> sysl
On Sat, Jul 20, 2024 at 3:49 PM Paolo Galtieri wrote:
>
> I wonder then if this is an issue due to dnf upgrade? I've used dnf
> upgrade to upgrade my system since at least F35. I wonder if at some
> point there was a syslog file which then became rsyslog and the old
> syslog file was never remov
t, 20 Jul 2024 12:05:10 -0700
Paolo Galtieri wrote:
A little investigation showed the following in /etc/logrotate.d
rsyslog:/var/log/messages
syslog:/var/log/messages
I don't have a syslog file in my /etc/logrotate.d, only rsyslog.
I'm running fedora 40 and logrotate seem
On Sat, 20 Jul 2024 12:05:10 -0700
Paolo Galtieri wrote:
> A little investigation showed the following in /etc/logrotate.d
>
> rsyslog:/var/log/messages
> syslog:/var/log/messages
I don't have a syslog file in my /etc/logrotate.d, only rsyslog.
I'm running fedora 40 and
I have updated my system using dnf upgrade for several releases. I am
currently running F39. Today I was looking at my running services and
noticed that the logrotate.service is failing to start due to the
following error:
Jul 20 11:49:41 caseyjones.homenet192-168-10.com logrotate[307129
That would have to have been a mariadb config file/code change to no
longer allow root at localhost to access without a password.
Based on this change adding the root@localhost type auth on Windows
then it should work.
https://jira.mariadb.org/browse/MDEV-26715
Those changes were 10.11.0 so I won
Worked fine with Fedora before 40, but now get message.
Line in /etc/logrotate.d/mariadb
/usr/bin/mariadb-admin $EXTRAPARAM --local flush-error-log \
flush-engine-log flush-general-log flush-slow-log
#OUTPUT
#/usr/bin/mariadb-admin: connect to server at 'localhost' failed
#error: 'Access de
d" so that the new
> file is picked up.
>
>> However, there doesn't seem to be a timer entry in systemctl output.
>> Ideas on how to get started would be appreciated.
>
> It seems that the triggering timer isn't mentioned in the log, but you
> should se
Ideas on how to get started would be appreciated.
It seems that the triggering timer isn't mentioned in the log, but you
should see the log entries for running logrotate.
"journalctl -b -u logrotate" will list only those.
___
users mailing
Hi,
I have a fedora32 system and would like the maillog to rotate exactly
at a specific time. How do I do that? It used to be that I could
create a crontab entry but now there appears to be this timer service,
including /usr/lib/systemd/system/logrotate.timer included with the
package that appear
OK. I found by reading the head of the new messages log.
I see its termination message...
On 5/10/20 1:29 AM, Robert Moskowitz wrote:
actually the change occurred at 1am.
On 5/10/20 1:19 AM, Robert Moskowitz wrote:
I see that my various log files have been rolled over at midnight.
But looki
On 06/11/15 03:11, Mark C. Allman wrote:
> I see this line in /etc/logrotate.d/syslog:
>
> /bin/kill -HUP `cat /var/run/syslogd.pid 2>/dev/null` 2>/dev/null||true
>
> The PID file for rsyslog is actually /var/run/rsyslogd.pid, therefore
> once logrotate runs the new l
I see this line in /etc/logrotate.d/syslog:
/bin/kill -HUP `cat /var/run/syslogd.pid 2>/dev/null` 2>/dev/null||true
The PID file for rsyslog is actually /var/run/rsyslogd.pid, therefore
once logrotate runs the new log files, e.g., messages, maillog, etc.,
are empty. Sound like a bug to y
>> The script should be written to use 'file' not just parse the extension.
>
>
> Why? Just because in <.001% of the time the extension will be wrong? Not
> exactly an efficient use of resources.
Are you in that much of a hurry to get your logwatch reports?
I'd prefer to have a more accurate pro
Am 24.10.2012 19:20, schrieb Joe Zeff:
> On 10/24/2012 08:58 AM, Alex wrote:
>> The script should be written to use 'file' not just parse the extension.
>
> Why? Just because in <.001% of the time the extension will be wrong? Not
> exactly an efficient use of resources.
because it is NOT the
On 10/24/2012 08:58 AM, Alex wrote:
The script should be written to use 'file' not just parse the extension.
Why? Just because in <.001% of the time the extension will be wrong?
Not exactly an efficient use of resources.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or c
>> I have an fc15 box and I'm having a problem with logwatch. I'm using
>> bzip2 for the compresscmd for logrotate, yet it somehow is giving the
>> compressed files a gz instead of bz2 extension. Logwatch uses this to
>> determine which command to use t
Alex pise:
> Hi,
>
> I have an fc15 box and I'm having a problem with logwatch. I'm using
> bzip2 for the compresscmd for logrotate, yet it somehow is giving the
> compressed files a gz instead of bz2 extension. Logwatch uses this to
> determine which command to use
Hi,
I have an fc15 box and I'm having a problem with logwatch. I'm using
bzip2 for the compresscmd for logrotate, yet it somehow is giving the
compressed files a gz instead of bz2 extension. Logwatch uses this to
determine which command to use to read the compressed files, so it
th
have upgraded my server from Fedora 14 to Fedora 16 (x86_64) - most
> things are going again happily but there are a few remaining problems -
> the main one at the moment involves Logrotate, Systemctl, Httpd and SSL.
> My logrotate.conf is set up for daily rotations so I get old logs l
e are a few remaining problems -
the main one at the moment involves Logrotate, Systemctl, Httpd and SSL.
My logrotate.conf is set up for daily rotations so I get old logs like:
/var/log/httpd/access_log-20120202
but, presumably because of the changes in Fedora from "service" to
&q
People,
I have upgraded my server from Fedora 14 to Fedora 16 (x86_64) - most
things are going again happily but there are a few remaining problems -
the main one at the moment involves Logrotate, Systemctl, Httpd and SSL.
My logrotate.conf is set up for daily rotations so I get old logs like
On Tue, 2011-10-25 at 16:12 -0400, Mike Wohlgemuth wrote:
> I don't see any way to get fail2ban to reopen the log file without
> also forgetting the current ban list.
As I recall, it's supposed to make temporary bans. So does it really
need to keep a ban list forever? You'd be banning things tha
On 10/25/2011 4:12 PM, Mike Wohlgemuth wrote:
> On 10/25/2011 11:12 AM, Mikkel L. Ellertson wrote:
>> It looks like you would have to modify the syslog logrotate script
>> and add a second command in the postrotate section after it restarts
>> syslogd. Does fail2ban accept
On 10/25/2011 11:12 AM, Mikkel L. Ellertson wrote:
> It looks like you would have to modify the syslog logrotate script
> and add a second command in the postrotate section after it restarts
> syslogd. Does fail2ban accept a SIGHUP to close and reopen the log file?
>
>
That was m
On 10/25/2011 01:23 AM, Andre Speelmans wrote:
> Change the config file for logrotate so that it does not create a new
> file, but that it uses copy-and-truncate. The exact syntax is easily
> found in the man-page.
>
Ah, that looks like what I need. I read the man page and s
> It looks like you would have to modify the syslog logrotate script
> and add a second command in the postrotate section after it restarts
> syslogd. Does fail2ban accept a SIGHUP to close and reopen the log file?
Or make it do copy-truncate, which is meant just for these cases where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/2011 09:07 AM, Andre Speelmans wrote:
>> I was referring to the fail2ban RPM. This has to be a problem for
>> just about any installation that uses logrotate.
>
> Most daemons seem to use their own logfile and therefore c
> I was referring to the fail2ban RPM. This has to be a problem for
> just about any installation that uses logrotate.
Most daemons seem to use their own logfile and therefore can use their
own logrotate configuration script in /etc/logrotate.d.
But /var/log/secure is not handled by a sp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/2011 12:23 AM, Andre Speelmans wrote:
>> It sounds like fail2ban still has the old log file open. You need to
>> have logrotate tell fail2ban that the log file has changed.
>
> Change the config file for logrotate so that
> It sounds like fail2ban still has the old log file open. You need to
> have logrotate tell fail2ban that the log file has changed.
Change the config file for logrotate so that it does not create a new
file, but that it uses copy-and-truncate. The exact syntax is easily
found in the ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/24/2011 12:14 PM, Mike Wohlgemuth wrote:
> I've installed fail2ban on Fedora 15 to block repeated failed ssh
> connections. It works great up until logrotate kicks in. When it
> rotates /var/log/secure then fail2ban stops notic
On Mon, Oct 24, 2011 at 20:17, Marvin Kosmal wrote:
> Hi
>
> This does not address your problem directly.
>
> I use a program called denyhosts for blocking ssh attempts. It creates a
> list in /etc/hosts.deny.
>
> Great program.
>
+1 to denyhosts.
> Good luck
>
> Marvin
>
--
Suvayu
Open
On Mon, Oct 24, 2011 at 10:14 AM, Mike Wohlgemuth wrote:
> I've installed fail2ban on Fedora 15 to block repeated failed ssh
> connections. It works great up until logrotate kicks in. When it
> rotates /var/log/secure then fail2ban stops noticing failed ssh
> attempts. Usin
I've installed fail2ban on Fedora 15 to block repeated failed ssh
connections. It works great up until logrotate kicks in. When it
rotates /var/log/secure then fail2ban stops noticing failed ssh
attempts. Using fail2ban-client to reload the jail fixes the problem,
but it also c
logrotate: ALERT exited abnormally with [1]
in crontab daily i have shedule the cron job to rotatelog for specific time
2 0 * * * /usr/bin/logrotate /etc/logrotate.conf
priviously it was rotating log with no problem but from last some days
Colin McCabe wrote:
> Thanks for the helpful suggestions, guys! I appreciate it.
>
> I would like to submit this upstream, but I'm having a bit of
> difficulty finding the upstream for this project. Do you happen to
> have a home page or mailing list for the logrotate upst
On Thu, Mar 17, 2011 at 9:38 PM, Todd Zullinger wrote:
> Patrick O'Callaghan wrote:
>> The Fedora Bugzilla is at http://bugzilla.redhat.com. You can create
>> an account there and then report your bug (and patch) against the
>> logrotate package. If it needs to be repo
On Fri, 2011-03-18 at 06:26 -0500, Aaron Konstam wrote:
> > While I try to forward reports upstream as needed, I really don't
> want
> > to see anyone be discouraged from reporting bugs directly upstream.
> > That benefits us all, IMO.
> >
>
> OK, it is time to report ignorance. I have difficulty
On Fri, 2011-03-18 at 00:38 -0400, Todd Zullinger wrote:
> Patrick O'Callaghan wrote:
> > The Fedora Bugzilla is at http://bugzilla.redhat.com. You can create
> > an account there and then report your bug (and patch) against the
> > logrotate package. If it needs to
On Fri, 2011-03-18 at 00:38 -0400, Todd Zullinger wrote:
> Patrick O'Callaghan wrote:
> > The Fedora Bugzilla is at http://bugzilla.redhat.com. You can create
> > an account there and then report your bug (and patch) against the
> > logrotate package. If it needs to
Patrick O'Callaghan wrote:
> The Fedora Bugzilla is at http://bugzilla.redhat.com. You can create
> an account there and then report your bug (and patch) against the
> logrotate package. If it needs to be reported upstream, the package
> maintainer will do it.
As a package main
On Thu, 2011-03-17 at 16:51 -0700, Colin McCabe wrote:
> I was unable to create a ticket on the bug report system I found on
> https://fedorahosted.org/logrotate/
> It allows me to view tickets by clicking on "View Tickets," but I
> can't create one.
>
> Perhap
On Thu, 17 Mar 2011 16:51:29 -0700
Colin McCabe wrote:
> Hi Patrick,
>
> I was unable to create a ticket on the bug report system I found on
> https://fedorahosted.org/logrotate/
> It allows me to view tickets by clicking on "View Tickets," but I
> can't c
Hi Patrick,
I was unable to create a ticket on the bug report system I found on
https://fedorahosted.org/logrotate/
It allows me to view tickets by clicking on "View Tickets," but I
can't create one.
Perhaps I need to create an account, or perhaps there is another bug
tracker tha
On Wed, 2011-03-16 at 18:15 -0700, Colin McCabe wrote:
> This patch fixes a buffer overflow in logrotate. The diff was done
> against trunk on http://svn.fedorahosted.org/svn/logrotate/
>
> Sorry if this is the wrong place to post this. I didn't see a mailing
> list mentioned
This patch fixes a buffer overflow in logrotate. The diff was done
against trunk on http://svn.fedorahosted.org/svn/logrotate/
Sorry if this is the wrong place to post this. I didn't see a mailing
list mentioned on the project page at
https://fedorahosted.org/logrotate/
Fixed version with p
This patch fixes a buffer overflow in logrotate. The diff was done
against trunk on http://svn.fedorahosted.org/svn/logrotate/
Sorry if this is the wrong place to post this. I didn't see a mailing
list mentioned on the project page at
https://fedorahosted.org/logrotate/
Index: con
Am Donnerstag, den 04.03.2010, 14:45 +0530 schrieb Kaushal Shriyan:
> Hi,
>
> is there a way to scp or rsync the files to a remote host older than
> 15 days in the logrotate config and than delete it on localhost older
> than 15 days, so that at a time only 15 days of logs a
Hi,
is there a way to scp or rsync the files to a remote host older than
15 days in the logrotate config and than delete it on localhost older
than 15 days, so that at a time only 15 days of logs are available on
localhost.
Thanks,
Kaushal
--
users mailing list
users@lists.fedoraproject.org
To
Philip Rhoades wrote:
> People,
>
> Every day I want to run a script on the current, complete maillog file
> so I set it up in crontab for 04:01 - one minute before the cron.daily
> logrotate happens but all the maillog log files start with lines in the
> file that vary betwe
People,
Every day I want to run a script on the current, complete maillog file
so I set it up in crontab for 04:01 - one minute before the cron.daily
logrotate happens but all the maillog log files start with lines in the
file that vary between 03:00 and 04:02 - how is this possible
63 matches
Mail list logo
