All,
After quite a bit of trail and error I managed to get log collection
working. Here are the commands for /etc/syslog-ng/syslog-ng.conf:
source s_net { tcp(ip(10.0.0.1) port(514) max-connections (5000));
udp(ip(10.0.0.1) port(514)); };
destination cisco-remote { file("/var/log/cisc
Timothy M Butterworth <
>> timothy.m.butterwo...@gmail.com> wrote:
>>
>>>
>>>
>>> On Sun, Apr 13, 2025 at 10:31 PM Timothy M Butterworth <
>>> timothy.m.butterwo...@gmail.com> wrote:
>>>
>>>&g
On Sun, Apr 13, 2025 at 10:31 PM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
> All,
>
> I modified /etc/syslog-ng/syslog-ng.conf to the following:
>
>
> # Sources
>
> # Add the following line
&
On Sun, Apr 13, 2025 at 10:51 PM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
>
>
> On Sun, Apr 13, 2025 at 10:31 PM Timothy M Butterworth <
> timothy.m.butterwo...@gmail.com> wrote:
>
>> All,
>>
>> I modified /
Timothy M Butterworth <
>> timothy.m.butterwo...@gmail.com> wrote:
>>
>>> All,
>>>
>>> I modified /etc/syslog-ng/syslog-ng.conf to the following:
>>>
>>>
>>> # Sources
>>> #
All,
I modified /etc/syslog-ng/syslog-ng.conf to the following:
# Sources
# Add the following line
source s_net { tcp(ip(0.0.0.0) port(514) max-connections (5000)); udp(); };
# Destinations
cal system logging
module(load="imklog") # provides kernel logging support
#module(load="immark") # provides --MARK-- message capability
# provides UDP syslog reception
#module(load="imudp")
#input(type="imudp" port="514")
# provides TCP syslog r
atch to work
> properly.
rsyslogd.conf controls what logfiles rsyslogd would generate:
*.* -/var/log/syslog
auth,authpriv.* /var/log/auth.log
cron.* /var/log/cron.log
daemon.*,local7.* -/var/log/daemon.log
kern.* -/var/lo
On Tue, 21 Nov 2023, John Covici wrote:
> hmmm, I looked at the release notes, but it does not say how to
> restore the old behavior, it just says many files are no longer
> necessary and lists them. I am using logwatch and that program seems
> to be effected, I would be OK, if I could get logwat
eb John Covici:
> > > Hi. I am using bookworm with latest updates and /var/log/syslog is
> > > empty, even though rsyslog is runniing. I am also using logwatch and
> > > not getting at least some responses I should get such as fail2ban.
> > > These may be sepa
Am 21.11.2023 um 05:15:24 Uhr schrieb John Covici:
> hmmm, I looked at the release notes, but it does not say how to
> restore the old behavior, it just says many files are no longer
> necessary and lists them.
Please post you syslog configuration.
:35 -0500,
Christoph Brinkhaus wrote:
>
> [1 ]
> Am Mon, Nov 20, 2023 at 05:01:50PM -0500 schrieb John Covici:
> > Hi. I am using bookworm with latest updates and /var/log/syslog is
> > empty, even though rsyslog is runniing. I am also using logwatch and
> > not gettin
Am Mon, Nov 20, 2023 at 05:01:50PM -0500 schrieb John Covici:
> Hi. I am using bookworm with latest updates and /var/log/syslog is
> empty, even though rsyslog is runniing. I am also using logwatch and
> not getting at least some responses I should get such as fail2ban.
> These may
Hi. I am using bookworm with latest updates and /var/log/syslog is
empty, even though rsyslog is runniing. I am also using logwatch and
not getting at least some responses I should get such as fail2ban.
These may be separate problems, but any help on those would be
appreciated. I saw a previous
Michael,
You are a star.
I dont know what I did before but I re-installed rsyslog and changed the
PrivateTmp to no
It works now.
I can see /tmp/server.log is now pushing syslog contents
Thank you very much.
On Mon, Nov 13, 2023 at 10:24 AM Michael Biebl wrote:
> Am 13.11.23 um 10:13 schr
wards
# systemctl show -P PrivateTmp rsyslog.service
no
Btw, for your use case, a subdirectory in /run would be more suitable,
like say /run/syslog/.
Also, you currently have
*.* -/tmp/server.log
*and*
*.=info;*.=notice;*.=warn;\
auth,authpriv.none;\
I forgot to answer the question on why I am doing this
I am experimenting on a no-log system where there is no writes what-so-ever
to /var/log (except for mails) or systemd journal (currently kept volatile)
/tmp/ is tmpfs mounted
Attached is the rsyslog config as-it-is being used now.
On Sun, No
Am 12.11.23 um 08:18 schrieb Bhasker C V:
Hi,
I have tried removing PrivateTmp=no in the rsyslog service file and it
still doesnt work
I assume you mean PrivateTmp=yes?
I have removed the service file which I had created too.
I found that when I run the daemon manually, it works well. Hence
Hi,
I have tried removing PrivateTmp=no in the rsyslog service file and it
still doesnt work
I have removed the service file which I had created too.
I found that when I run the daemon manually, it works well. Hence I have
disabled rsyslog and I have put the daemon startup in my rc-local
But yes,
The service file you posted is not a good idea. Please remove it again.
If moving the log file out of /tmp is not an option, please run
systemctl edit rsyslog.service
and disable PrivateTmp via
[Service]
PrivateTmp=no
OpenPGP_signature.asc
Description: OpenPGP digital signature
000, Bhasker C V wrote:
>
> > I moved my syslog to a different location '/tmp/server.log'
>
> A rather strange decision, since /tmp is usually pruned on reboot.
>
> > This was working all fine until I moved to selinux in enforcing mode.
> >
> > I have t
On 2023-11-08 08:26 +, Bhasker C V wrote:
> I moved my syslog to a different location '/tmp/server.log'
A rather strange decision, since /tmp is usually pruned on reboot.
> This was working all fine until I moved to selinux in enforcing mode.
>
> I have tried putting
Hi,
I moved my syslog to a different location '/tmp/server.log'
This was working all fine until I moved to selinux in enforcing mode.
I have the file context as system_u:object_r:syslogd_runtime_t:s0
now, the file is empty
Strangely ...
lsof shows rsyslog is using this file
rsys
On Thu, Jul 06, 2023 at 08:21:18PM -0600, Charles Curley wrote:
> On Fri, 7 Jul 2023 10:53:10 +1200
> "C.T.F. Jansen" wrote:
>
> > The current default logging is unsatisfactory and needs to include a
> > text log.
>
> You can get much of the effect of /va
On Fri, 7 Jul 2023 10:53:10 +1200
"C.T.F. Jansen" wrote:
> The current default logging is unsatisfactory and needs to include a
> text log.
You can get much of the effect of /var/log/syslog with journalctl. "man
journactl" for the gory details. Of particular use
On 7/7/23 07:59, Greg Wooledge wrote:
As with many of the unpopular changes that Debian embraces, this is a
decision they made, and no matter how utterly daft and ridiculous it is,
no amount of griping by users will change their minds about it.
As I have taken the first step of changing one
On Fri, Jul 07, 2023 at 10:53:10AM +1200, C.T.F. Jansen wrote:
> To restore a readable and accessible syslog in Debian 12.0 enter
>
>apt-get install rsyslog
>
> One doesn't need to do anything with the journal suite.
> I installed rsyslog-doc as well. I
To restore a readable and accessible syslog in Debian 12.0 enter
apt-get install rsyslog
One doesn't need to do anything with the journal suite.
I installed rsyslog-doc as well. It is in:
/usr/share/doc/rsyslog-doc/html
The logs appear to be set up to rotate etc alrea
Hi everyone and for people dropping by having the same issue.
The problem is *solved* \o/
The issue was: missing /run/systemd/journal/socket
What solved the problem:
- apt-get install --reinstall systemd systemd-sysv libsystemd0
dbus-user-session
- /run/systemd/journal/socket and /run/sy
Hi.
On Sun, Feb 26, 2023 at 07:00:34AM +0800, jeremy ardley wrote:
> Any way to stop it? Or get syslog to send it to /dev/null ?
Of course there is.
cat > /etc/rsyslog.d/mateweather.conf << EOF
if (\$syslogtag containts 'org.mate.panel.applet.MateWeatherAppletFactory
My syslog gets a couple of dozen line like below every 10 mins or so.
Any way to stop it? Or get syslog to send it to /dev/null ?
Feb 26 06:50:22 client
org.mate.panel.applet.MateWeatherAppletFactory[3517]: Forecast for
Monday 27 February
Feb 26 06:50:22 client
> I've tried they sent me back here :/
>
> Le 02/02/2023 à 17:06, debian-u...@howorth.org.uk a écrit :
> >> On 01/02/2023 21:48, Freyja wrote:
> >>> Instead of just creating the folders, I've reinstalled some
> >>> packages:
> >> I would consider complete reinstall (install from scratch). It m
I need to look deeper in your recommendations, I will try them as soon
as I can.
Le 02/02/2023 à 17:28, songbird a écrit :
debian-u...@howorth.org.uk wrote:
...
Maybe it's worth asking on the systemd-devel mailing list?
did you reinstall rsyslog? did you purge the configs for it
(back th
I've tried they sent me back here :/
Le 02/02/2023 à 17:06, debian-u...@howorth.org.uk a écrit :
On 01/02/2023 21:48, Freyja wrote:
Instead of just creating the folders, I've reinstalled some
packages:
I would consider complete reinstall (install from scratch). It may be
faster even for a pers
liser-perl
libunicode-utf8-perl libunix-syslog-perl
liburi-escape-xs-perl liburi-perl libuuid-perl libvariable-magic-perl
libvte-2.91-0 libwant-perl libwbclient0 libwireshark14 libwiretap11
libwrap0 libwsutil12 libwww-perl libwww-robotrules-perl
libxdelta2 libxerces-c3.2 libxft2 libxml-libxml-pe
Are you using SELinux or AppApparmor ?
Have you tried disabling it?
OpenPGP_signature
Description: OpenPGP digital signature
debian-u...@howorth.org.uk wrote:
...
> Maybe it's worth asking on the systemd-devel mailing list?
did you reinstall rsyslog? did you purge the configs for it
(back them up if needed)? when i remove a package i have been
having troubles with i often purge it instead of uninstalling
it.
you
> On 01/02/2023 21:48, Freyja wrote:
> > Instead of just creating the folders, I've reinstalled some
> > packages:
>
> I would consider complete reinstall (install from scratch). It may be
> faster even for a person having experience with systemd
> troubleshooting. Something low level is affect
oting.
> Something low level is affected.
>
> However I find the problem interesting: how to get logs if journald can
> not start.
i always see something at least in other files because i
still use rsyslog.
restore the directory and file then, but if you have
/etc/syslog/journa
This is only a solution I'll look at as last resort.
There is too much work on that server.
But I agree it's something I was already thought of.
But we are not on Windows there, we should be able to do something.
The only time I had to do this is because dpkg was totally broken for an
unknown r
Deleted the folder, restarted and back to square 1.
--
❯ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● dbus.socket loaded failed failed D-Bus System
Message Bus Socket
● syslog.socket loaded failed failed Syslog
On Thu, Feb 02, 2023 at 02:27:33PM +0100, Freyja wrote:
> This [reinstalling] is only a solution I'll look at as last resort.
> There is too much work on that server.
>
> But I agree it's something I was already thought of.
>
> But we are not on Windows there, we should be able to do something.
This is only a solution I'll look at as last resort.
There is too much work on that server.
But I agree it's something I was already thought of.
But we are not on Windows there, we should be able to do something.
The only time I had to do this is because dpkg was totally broken for an
unknown r
On 01/02/2023 21:48, Freyja wrote:
Instead of just creating the folders, I've reinstalled some packages:
I would consider complete reinstall (install from scratch). It may be
faster even for a person having experience with systemd troubleshooting.
Something low level is affected.
However I
Freyja wrote:
...
> However journalctl still stucks on 24th Oct:
> --
> ❯ journalctl -b
> -- Journal begins at Sun 2022-10-23 19:55:11 CEST, ends at Mon
> 2022-10-24 14:14:33 CEST. --
> -- No entries --
if you are not concerned about keeping the last journals for
any reason i would remove the
On Wed, Feb 01, 2023 at 03:39:05PM +0100, Freyja wrote:
> But I've found that some processes were complaining that selinux filesystem
> was not mounted.
> I know I've disabled apparmor and selinux in the past because too many
> processes were blocked by them
I don't know much about SELinux. If t
Ok,
Instead of just creating the folders, I've reinstalled some packages:
--
❯ apt-get install --reinstall systemd systemd-sysv libsystemd0
dbus-user-session
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 4 reins
I don't remember all the steps I've made.
I tried so many things.
But I've found that some processes were complaining that selinux
filesystem was not mounted.
Mounted the filesystem with the command "cat /etc/systemd/system.conf"
and it helped starting some process.
That time, even if the fil
On Wed, 1 Feb 2023 13:26:58 +0100
Freyja wrote:
> For /run/systemd/journal/socket this is another story.
> The folder journal does not exist at all.
Well, that could be a problem. On one of my computers:
root@jhegaala:~# ll /run/systemd/journal/socket
srw-rw-rw- 1 root root 0 Jan 25 09:55 /run/
On Thu, 2 Feb 2023 at 00:07, Freyja wrote:
> I've already tried to solve this issue in December with some success
Hi, could you describe in detail what you did?
Can you also post the output of:
cat /etc/systemd/system.conf
Also, a small thing I happened to notice:
> root in /var/log
> ❯ ls
There is an interesting part: I've already tried to solve this issue in
December with some success except for 2 systemd services (udevd-control
& udevd-kernel).
It stopped again working the 25th of december.
--
I've found a journal related to 24th December in /var/log/journal:
root in /var/log
Hi greg,
--
❯ df /run
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1629236 3732 1625504 1% /run
--
For /run/systemd/journal/socket this is another story.
The folder journal does not exist at all.
--
❯ ls -la /run/systemd/
total 0
drwxr-xr-x 17 root r
On Wed, Feb 01, 2023 at 11:15:58AM +0100, deb...@sioban.net wrote:
> "journalctl -e" ends the 24th of October.
> ❯ journalctl -b
> -- Journal begins at Sun 2022-10-23 19:55:11 CEST, ends at Mon 2022-10-24
> 14:14:33 CEST. --
> -- No entries --
> ❯ systemctl start systemd-journald.service
> A depe
Hi max,
"journalctl -e" ends the 24th of October.
--
Oct 24 14:14:33 shax systemd[1]: Stopped Update UTMP about System
Boot/Shutdown.
Oct 24 14:14:33 shax systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Oct 24 14:14:33 shax systemd[1]: Stopped Create Volatile Files and
Directories.
Oct
On 31/01/2023 16:57, deb...@sioban.net wrote:
I'm contacting you because I'm clueless on what's happening.
Basically my issue is I don't have logs anymore :/
...
> systemctl start rsyslog.service
A dependency job for rsyslog.service failed. See 'journalctl -xe' for
details.
❯systemctl --fa
the result:
❯ systemctl status syslog.socket
● syslog.socket - Syslog Socket
Loaded: loaded (/lib/systemd/system/syslog.socket; static)
Active: failed (Result: resources)
Triggers: ● rsyslog.service
Docs: man:systemd.special(7)
https://www.freedesktop.org/wiki/Software/systemd
On Tue, Jan 31, 2023 at 05:22:23PM +0100, Sioban wrote:
> Here is the output.
>
> ❯ systemctl cat rsyslog.service
That looks exactly like mine. So that's probably fine.
> Requires=syslog.socket
This is the only part of it that looks like a "dependency". Maybe
this is the thing that's breaking
Here is the output.
❯ systemctl cat rsyslog.service
# /lib/systemd/system/rsyslog.service
[Unit]
Description=System Logging Service
Requires=syslog.socket
Documentation=man:rsyslogd(8)
Documentation=man:rsyslog.conf(5)
Documentation=https://www.rsyslog.com/doc/
[Service]
Type=notify
ExecStart=/u
On Tue, Jan 31, 2023 at 03:52:32PM +0100, deb...@sioban.net wrote:
> ❯ df /var/log /var/log/journal
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/md24 46096212 1620728 42101496 4% /var/log
> /dev/md24 46096212 1620728 42101496 4% /var/log
OK, not out of disk
Hi Greg,
I'm sorry, I was unsure what kind of logs to give, thanks for giving me some
instructions.
❯ df /var/log /var/log/journal
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md24 46096212 1620728 42101496 4% /var/log
/dev/md24 46096212 1620728 42101496 4% /
On Tue, Jan 31, 2023 at 11:09:59AM +0100, deb...@sioban.net wrote:
>
> Le 31/01/2023 à 11:08, Nicolas George a écrit :
> > deb...@sioban.net (12023-01-31):
> > > A dependency job for rsyslog.service failed. See 'journalctl -xe' for
> > > details.
> > Have you considered seeing journalctl -xe for
Le 31/01/2023 à 11:08, Nicolas George a écrit :
deb...@sioban.net (12023-01-31):
A dependency job for rsyslog.service failed. See 'journalctl -xe' for
details.
Have you considered seeing journalctl -xe for details?
Hi,
Yes, that was my first action.
The last line of log is from Oct 24 :/
deb...@sioban.net (12023-01-31):
> A dependency job for rsyslog.service failed. See 'journalctl -xe' for
> details.
Have you considered seeing journalctl -xe for details?
--
Nicolas George
ailed failed Fail2Ban Service
● dbus.socket loaded failed failed D-Bus System
Message Bus Socket
● syslog.socket loaded failed failed Syslog Socket
● systemd-fsckd.socket loaded failed failed fsck to fsckd
communication Socket
● systemd-journald-audit.socket
On Sat, Nov 05, 2022 at 05:12:40PM +0100, local10 wrote:
> Nov 5, 2022, 15:30 by g...@wooledge.org:
>
> >> > > local10 wrote:
> >> > >
> >> > > > Any ideas as to get the old syslog date format back?
> >>
> >
> > What
Nov 5, 2022, 14:53 by j...@k4vqc.com:
> On Sat, 2022-11-05 at 11:34 +0100, local10 wrote:
>
>> Nov 5, 2022, 09:55 by scdbac...@gmx.net:
>>
>> > Hi,
>> >
>> > local10 wrote:
>> >
>> > > Any ideas as to get the old syslo
> > > local10 wrote:
> > >
> > > > Any ideas as to get the old syslog date format back?
What caused a change? What version of Debian are you running? What
happened on the date in question (November 4) -- were some packages
updated? Which ones?
Here in Debia
On Sat, 2022-11-05 at 11:34 +0100, local10 wrote:
> Nov 5, 2022, 09:55 by scdbac...@gmx.net:
>
> > Hi,
> >
> > local10 wrote:
> >
> > > Any ideas as to get the old syslog date format back?
> > >
> >
> > The internet points to /etc/r
Nov 5, 2022, 09:55 by scdbac...@gmx.net:
> Hi,
>
> local10 wrote:
>
>> Any ideas as to get the old syslog date format back?
>>
>
> The internet points to /etc/rsyslog.conf and in there:
>
> #
> # Use traditional timestamp format.
> # To enable
Hi,
local10 wrote:
> Any ideas as to get the old syslog date format back?
The internet points to /etc/rsyslog.conf and in there:
#
# Use traditional timestamp format.
# To enable high precision timestamps, comment out the following line.
#
$ActionFileDefaultTempl
Hi,
It looks like the syslog date format has changed for some reason (see below)
and the change is definitely less readable for me. The change maybe related to
the rsyslog upgrade that happened around November 4, 2022:
[UPGRADE] rsyslog:amd64 8.2210.0-1 -> 8.2210.0-3
Any ideas as to
Original Message
*Subject: * Re: Strange syslog behaviour [Solved]
*From: * Tixy
*To: * Debian-user
*CC: *
*Date: * 2022-10-16 12:40 PM
On Sun, 2022-10-16 at 09:09 -0400, Wayne Sallee wrote:
It would be nice if updates presented "old file",
Original Message
*Subject: * Re: Strange syslog behaviour [Solved]
*From: * Charles Curley
*To: * Debian Users
*CC: *
*Date: * 2022-10-16 11:09 AM
When I do an upgrade I run the upgrade in one terminal, and have Emacs
running in another. As these
; > > The fix:
> > > diff /etc/logrotate.d/rsyslog.dpkg-dist /etc/logrotate.d/rsyslog
> > > edit /etc/logrotate.d/rsyslog
> > > Change from
> > > invoke-rc.d rsyslog rotate > /dev/null
> > > to
> > > /usr/li
On Sun, 2022-10-16 at 09:09 -0400, Wayne Sallee wrote:
> It would be nice if updates presented "old file", "new file", "combined
> file"; choice: (1), (2), (3).
It does offer several choices, one of them is to show a 'diff' of the
old and new files. Only you can know what changes you made and wan
On Sun, 16 Oct 2022 09:09:36 -0400
Wayne Sallee wrote:
> > You rejected the new file, which is why it was instead written to
> > /etc/logrotate.d/rsyslog.dpkg-dist (which you could have safely
> > left or removed—it's harmless).
>
> Yes, I rejected the new file, causing the other file to be th
Original Message
*Subject: * Re: Strange syslog behaviour [Solved]
*From: * David Wright
*To: * Debian-user
*CC: *
*Date: * 2022-10-16 01:27 AM
On Sat 15 Oct 2022 at 13:59:18 (-0400), Wayne Sallee obfuscated the following
with HTML:
Jeremy Ardley, did
/usr/lib/rsyslog/rsyslog-rotate
> Then delete /etc/logrotate.d/rsyslog.dpkg-dist
> I then rebooted my servers to get the syslog used.
> Then
> ls /var/log | grep syslog
> To see that it was working. I will know tomorrow if it is still working.
I think the point you've mi
While I was composing my second post in this thread,
On Tue 12 Apr 2022 at 06:38:34 (+0800), Jeremy Ardley wrote:
> On 11/4/22 12:00 pm, Jeremy Ardley wrote:
> > On 11/4/22 11:46 am, David Wright wrote:
> > >
> > > There are tabooext and taboopat directives for ignoring files in
> > > logrotated.d
On Sat, Oct 15, 2022 at 01:59:18PM -0400, Wayne Sallee wrote:
>edit /etc/logrotate.d/rsyslog
>Change from
> invoke-rc.d rsyslog rotate > /dev/null
>to
> /usr/lib/rsyslog/rsyslog-rotate
Hmm.
In /etc/init.d/rsyslog (which is what the old command c
tate > /dev/null
to
/usr/lib/rsyslog/rsyslog-rotate
Then delete /etc/logrotate.d/rsyslog.dpkg-dist
I then rebooted my servers to get the syslog used.
Then
ls /var/log | grep syslog
To see that it was working. I will know tomorrow
On Sat, Oct 15, 2022 at 10:13:05AM -0400, Wayne Sallee wrote:
> Original Message
> *Subject: * Strange syslog behaviour [Solved]
> *From: * Jeremy Ardley
> > Anyway long story short, at some stage some package updates must have
> > written an
Thanks for pointing this out.
I just noticed this problem a few days ago.
Wayne Sallee
wa...@waynesallee.com
http://www.WayneSallee.com
Original Message
*Subject: * Strange syslog behaviour [Solved]
*From: * Jeremy Ardley
*To: * Debian-user
*CC: *
*Date
On 12/4/22 6:38 am, Jeremy Ardley wrote:
And discovered that /etc/logrotate.d/inetutils-syslogd was also being
loaded. It had duplicates of many entries in /etc/logrotate.d/rsyslog
All I wanted was ping _traceroute_ but I got a world of hurt as well!
*this* seems likely to solve the probl
On Mon 11 Apr 2022 at 12:00:38 (+0800), Jeremy Ardley wrote:
> On 11/4/22 11:46 am, David Wright wrote:
> >
> > There are tabooext and taboopat directives for ignoring files in
> > logrotated.d, and I would have thought it reasonable to exclude
> > these sorts of housekeeping files by default, bec
On 11/4/22 12:00 pm, Jeremy Ardley wrote:
On 11/4/22 11:46 am, David Wright wrote:
There are tabooext and taboopat directives for ignoring files in
logrotated.d, and I would have thought it reasonable to exclude
these sorts of housekeeping files by default, because they're very
likely to conta
On 11/4/22 11:46 am, David Wright wrote:
There are tabooext and taboopat directives for ignoring files in
logrotated.d, and I would have thought it reasonable to exclude
these sorts of housekeeping files by default, because they're very
likely to contain some duplication. I would file a bug agai
On Mon 11 Apr 2022 at 10:07:53 (+0800), Jeremy Ardley wrote:
> I have systems (armbian) that had anomalous behaviour.
>
> This included sometimes writing to /var/log/syslog.1 rather than to
> /var/log/syslog (which was created, but zero size)
>
> Additionally the logrotate was
I have systems (armbian) that had anomalous behaviour.
This included sometimes writing to /var/log/syslog.1 rather than to
/var/log/syslog (which was created, but zero size)
Additionally the logrotate was happening daily or twice daily when
seemingly configured for weekly rotates
Anyway
Bob Weber writes:
> On 3/10/19 5:20 PM, Joe Pfeiffer wrote:
>
> Since a recent update, my /var/log/syslog is getting spammed with huge
> numbers of messages of the form
>
> Mar 10 14:02:25 snowball systemd-udevd[18681]: Process '/sbin/mdadm
> --incremental --export /
On 3/10/19 5:20 PM, Joe Pfeiffer wrote:
Since a recent update, my /var/log/syslog is getting spammed with huge
numbers of messages of the form
Mar 10 14:02:25 snowball systemd-udevd[18681]: Process '/sbin/mdadm
--incremental --export /dev/sda3 --offroot
/dev/disk/by-id/ata-ST3000
Since a recent update, my /var/log/syslog is getting spammed with huge
numbers of messages of the form
Mar 10 14:02:25 snowball systemd-udevd[18681]: Process '/sbin/mdadm
--incremental --export /dev/sda3 --offroot
/dev/disk/by-id/ata-ST3000DM001-1ER166_Z501MTQ3-part3
/dev/disk/by-par
Hello Support!
Any idea how to fix or troubleshoot this vulnerability ?
-vulnerability-
[medium] [6514/101915888/tls-syslog?] IETF X.509 SSL Certificate Signature
:
> *.debug,local6.none,local7.none /var/log/syslog
> # DHCP
> local7.debug/var/log/dhcp/dhcpd.log
>
> But
> What I really want is all the regular DHCP log stuff in a file
> /var/log/dhcp/dhcpd.log but.. I want errors li
Hi,
Plenty of examples on-line how to move logging from the isc-dhcp-server to a
different file using something like
log-facility local7;
in the dhcp.conf file and then in my syslog.conf:
*.debug,local6.none,local7.none /var/log/syslog
# DHCP
local7.debug
gracias!. era eso mismo. ya me estaba volviendo loco.
On 12/11/2018 11:41 AM, Greg Wooledge wrote:
On Tue, Dec 11, 2018 at 11:29:28AM -0500, Eriel Perez wrote:
(*system*) ERROR (Missing newline before EOF, this crontab file will be
ignored)
Add the missing newline. If you use vi/vim, this hap
On Tue, Dec 11, 2018 at 11:29:28AM -0500, Eriel Perez wrote:
> (*system*) ERROR (Missing newline before EOF, this crontab file will be
> ignored)
Add the missing newline. If you use vi/vim, this happens automatically
and you cannot stop it. If you use something else, maybe you just have
to press
colegas
tengo este error en el syslog
(*system*) ERROR (Missing newline before EOF, this crontab file will be
ignored)
Alguna idea? esta en el fichero de rotacion de las trazas.
40 8 * * * root /usr/local/sbin/trazas.sh
la linea arriba es la que esta en el crontab (/etc
Hi.
On Sat, Sep 08, 2018 at 12:30:13PM -0400, Jim Popovitch wrote:
> On Sat, 2018-09-08 at 19:18 +0300, Reco wrote:
> > Hi.
> >
> > On Sat, Sep 08, 2018 at 12:10:26PM -0400, Jim Popovitch wrote:
> > > How do I prevent/stop Gnome trivial errors fro
On Sat, 2018-09-08 at 19:18 +0300, Reco wrote:
> Hi.
>
> On Sat, Sep 08, 2018 at 12:10:26PM -0400, Jim Popovitch wrote:
> > How do I prevent/stop Gnome trivial errors from flooding syslog?
>
> By configuring your journald and syslog correctly.
> For insta
1 - 100 of 729 matches
Mail list logo
