ode 0755
$Umask 0022
#
# Where to place spool and state files
#
$WorkDirectory /var/spool/rsyslog
#
# Include all config files in /etc/rsyslog.d/
#
$IncludeConfig /etc/rsyslog.d/*.conf
###
RULES
###
#
# Log anything besides private authentication messages to a
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
e.
Most of the stuff in /var/log haven't been touched since my upgrade, like
/var/log/messages and /var/log/syslog.
After updating from squeeze to wheezy I had yesterday just the same problem.
Fortunately, the installation of rsyslog (5.8.11-3, i386) worked. Now,
/dev/xconsole and the loggi
On Lu, 17 iun 13, 09:42:29, amber gilchrist wrote:
> The other strange part of this is that the rsyslog package isn't on my
> system anymore, and when I tried to install it, I got this warning:
> initscripts breaks rsyslog (<< 5.8.2-2)
This doesn't sound right, wheezy has 5.8.11-3. Please post th
anymore. Most of
the stuff in /var/log haven't been touched since my upgrade, like
/var/log/messages and /var/log/syslog.
The other strange part of this is that the rsyslog package isn't on my system
anymore, and when I tried to install it, I got this warning:
initscripts breaks rsyslog (&
> System Events
> =-=-=-=-=-=-=
> ***
> *** This could indicate tampering.
> *** WARNING ***: Log file /var/log/syslog is smaller than last time
> checked!
Hum... could it be because logrotate made its job and cutted the syslog
file while logcheck was analyzing it?
It could be ju
/log/syslog is smaller than last time checked!
--
Tell the truth or trump--but get the trick.
-- Mark Twain, "Pudd'nhead Wilson's Calendar"
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Camaleón writes:
> On Tue, 18 May 2010 20:08:02 +0200, Merciadri Luca wrote:
>
>> Camaleón writes:
>
>>> Just review your "/var/log/Xorg.0.log". If X crashed there must
>>> something there :-?
>> Nothing really interesting there. Just:
>>
>> ==
>> A
On Tue, 18 May 2010 20:08:02 +0200, Merciadri Luca wrote:
> Camaleón writes:
>> Just review your "/var/log/Xorg.0.log". If X crashed there must
>> something there :-?
> Nothing really interesting there. Just:
>
> ==
> AUDIT: Tue May 18 18:01:04 2010: 3716 X: client 33 rejected from local
> host
t nothing worked, except launching another tty, and restarting gdm.
>> Here is the interesting output I obtained by looking at /var/log/syslog
>> and dmesg:
>>
>> ==
>> [24892.623421] atkbd.c: Unknown key pressed (translated set 2, code 0xbb
>> on isa0060/serio
sting output I obtained by looking at /var/log/syslog
> and dmesg:
>
> ==
> [24892.623421] atkbd.c: Unknown key pressed (translated set 2, code 0xbb
> on isa0060/serio0).
(...)
That seems to be unrelated with a X freeze. Looks like a keyboard key
mapping error but nothing serio
Hi,
I realized that my computer (this one, Debian Lenny, w. k.
2.6.26-2-686-bigmem) was frozen. I tried escaping from the screensaver,
but nothing worked, except launching another tty, and restarting gdm.
Here is the interesting output I obtained by looking at /var/log/syslog
and dmesg
ystem halt" messages than does /var/log/syslog.
# zgrep halt syslog.*.gz | wc -l; zgrep halt messages.*.gz | wc -l
2
16
My hypothesis is that kdm is logging through syslog, while shutdown
is logging through messages...but it seem odd that kdm doesn't
use shutdown. Can anyone explain this disc
I had something like this in my server with some crashes. I changed the network
card and resolved.
Probably your network card is crashed too.
Gilberto
On Tue, 18 Apr 2006 11:07:21 +0200
KLEIN Stéphane <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've strange message in my
KLEIN Stéphane wrote:
> Unable to handle kernel paging request at virtual address 064b0008 ...
This is called a kernel oops. It means that something in your kernel
crashed and it might be dangerous to continue running.
It may indicate either a bug in the kernel, or hardware failure, but I
am not
Hello,
I've strange message in my /var/log/syslog file.
Unable to handle kernel paging request at virtual address 064b0008 ...
Full message is in my attached file.
Thanks for your help,
--Stéphane
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
eth1:
H. S. wrote:
I installed sensord a couple of days ago and since then I am getting
these messages repeatedly and I am not sure what to make of them. Should
I be worried? If not, then how can I stop these messages(apart from
uninstalling sensord)? If yes, what could be wrong?
Here is one cycle wh
I installed sensord a couple of days ago and since then I am getting
these messages repeatedly and I am not sure what to make of them. Should
I be worried? If not, then how can I stop these messages(apart from
uninstalling sensord)? If yes, what could be wrong?
Here is one cycle which is repeat
Hi List,
I just experienced a pseudo denial of service issue. A server of ours
runs woody and bind seems to have filled syslog and daemon.log with
about 1.3g worth of messages along the lines of
Apr 18 18:25:38 server named[241]: sysquery: no addrs found for root NS
(A.ROOT-SERVERS.NET)
Apr 18
>
> hello
Hi,
>
> Can someone tell me how to automatically backup and compress
> /var/log/syslog into gzip format or something. Aparently my computer did
> this for sometime but then stoped doing it and now the file ir over
> 3megabyte.
see /etc/crontab whether /etc/cron.
hello
Can someone tell me how to automatically backup and compress
/var/log/syslog into gzip format or something. Aparently my computer did
this for sometime but then stoped doing it and now the file ir over
3megabyte.
regards
J.A.Serralheiro
On Tue, Oct 10, 2000 at 09:48:49AM +0200, Rob Kaper wrote:
> On Tue, Oct 10, 2000 at 10:37:32AM +0300, Debian User wrote:
> > My /var/log/messages and /var/log/syslog files looks very strange. I
> > attached them to this mail. Can you tell me why the lines are marked like
&g
On Tue, Oct 10, 2000 at 10:37:32AM +0300, Debian User wrote:
> My /var/log/messages and /var/log/syslog files looks very strange. I
> attached them to this mail. Can you tell me why the lines are marked like
> this ? I have installed potato.
> Oct 8 08:11:16 ady -- MARK --
Th
Don't worry about it.
-- MARK -- is there to tell you that the sytem was up and runing.
So with the marks you can see if your system has been down for example
between1am and 5am.
/Ingemar
Debian User wrote:
> My /var/log/messages and /var/log/syslog files looks very strange. I
&g
My /var/log/messages and /var/log/syslog files looks very strange. I
attached them to this mail. Can you tell me why the lines are marked
like this ? I have installed potato.
Adrian Nims
Oct 8 06:48:12 ady syslogd 1.3-3#33.1: restart.
Oct 8 07:11:16 ady -- MARK --
Oct 8 07:31:16 ady
Matthew Thompson wrote:
> Hello,
>
> I'm getting TONS of this:
>
> Jun 12 06:30:03 doma kernel: Packet log: input REJECT eth0 PROTO=17
> 216.39.146.44:513 216.39.146.255:513 L=88 S=0x00 I=56637 F=0x T=64
> (#5)
> Jun 12 06:33:03 doma kernel: Packet log: input REJECT eth0 PROTO=17
> 216.39.146.
06:39:03 doma kernel: Packet log: input REJECT eth0 PROTO=17
> 216.39.146.44:513 216.39.146.255:513 L=88 S=0x00 I=56686 F=0x0000 T=64
> (#5)
>
> ...in /var/log/syslog (running potato with ipchains over 2 NIC's). Is
> this common for a firewall with strong rules, or do I
T=64
(#5)
...in /var/log/syslog (running potato with ipchains over 2 NIC's). Is
this common for a firewall with strong rules, or do I have something
amiss?
TIA :)
Matthew Thompson http://mattyt.net
[EMAIL PROTECTED] http://www.oz.net/~mattyt
--Someday, I'll have a web page.--
34 matches
Mail list logo