From: Luca Ferrari <fluca1978@virgilio.it>
To: linux-admin@vger.kernel.org
Subject: Re: syslog does not start
Date: Thu, 4 Mar 2004 18:51:03 +0100 [thread overview]
Message-ID: <200403041851.03011.fluca1978@virgilio.it> (raw)
In-Reply-To: <Pine.SOL.4.33.0403011827120.21790-200000@cupid.che.iitb.ac.in>
On Tuesday 02 March 2004 00:27 Upendra L. Gandhi's cat walking on the keyboard
wrote:
> I know ssh does not work in 2.6.3
>
>
> ~Upen
>
> > From: Luca Ferrari <fluca1978@virgilio.it>
> > Reply-To: fluca1978REMOVE_THIS_STRING@virgilio.it
> > To: linux-admin@vger.kernel.org
> > Subject: syslog does not start
> >
> > Hi,
> > I'm compiling the 2.6.3 kernel to run on my suse 8.2 laptop. A lot of
> > things start to work now, but I've got several services that does not
> > run, such as ssh, cups, etc. The problem is that syslog does not start
> > too. I believe that it could be a network problem, but it appears ok,
> > since the loopback interface is rightly configured. What can be the
> > problem?
> >
On Wednesday 03 March 2004 00:14 Jay Goodman's cat walking on the keyboard
wrote:
> try starting syslog by hand in debugging mode
> and capture/tee
>
>
> /sbin/syslogd -d | tee syslog_debug.out
>
> (will pipe output to screen and the file syslog_debug.out)
>
Mabe I'm misuderstanding the file produced as syslog output, but it seems ok
if I run it manually. So what can be that produces syslog to fail during
startup? I've checked my startup scripts and simply invoke syslog without
strange flags, so I'm quite confused.
Below there's the output of the debug mode :
Allocated parts table for 1024 file descriptors.
Starting.
Called init.
Called allocate_log, nlogs = -1.
cfline(kern.warn;*.err;authpriv.none /dev/tty10)
symbolic name: warn ==> 4
symbolic name: kern ==> 0
symbolic name: err ==> 3
symbolic name: none ==> 16
symbolic name: authpriv ==> 80
leading char in action: /
filename: /dev/tty10
Called allocate_log, nlogs = 0.
cfline(kern.warn;*.err;authpriv.none |/dev/xconsole)
symbolic name: warn ==> 4
symbolic name: kern ==> 0
symbolic name: err ==> 3
symbolic name: none ==> 16
symbolic name: authpriv ==> 80
leading char in action: |
filename: |/dev/xconsole
Called allocate_log, nlogs = 1.
cfline(*.emerg *)
symbolic name: emerg ==> 0
leading char in action: *
write-all
Called allocate_log, nlogs = 2.
cfline(mail.* -/var/log/mail)
symbolic name: * ==> 255
symbolic name: mail ==> 16
leading char in action: /
filename: /var/log/mail
Called allocate_log, nlogs = 3.
cfline(mail.info -/var/log/mail.info)
symbolic name: info ==> 6
symbolic name: mail ==> 16
leading char in action: /
filename: /var/log/mail.info
Called allocate_log, nlogs = 4.
cfline(mail.warn -/var/log/mail.warn)
symbolic name: warn ==> 4
symbolic name: mail ==> 16
leading char in action: /
filename: /var/log/mail.warn
Called allocate_log, nlogs = 5.
cfline(mail.err /var/log/mail.err)
symbolic name: err ==> 3
symbolic name: mail ==> 16
leading char in action: /
filename: /var/log/mail.err
Called allocate_log, nlogs = 6.
cfline(news.crit -/var/log/news/news.crit)
symbolic name: crit ==> 2
symbolic name: news ==> 56
leading char in action: /
filename: /var/log/news/news.crit
Called allocate_log, nlogs = 7.
cfline(news.err -/var/log/news/news.err)
symbolic name: err ==> 3
symbolic name: news ==> 56
leading char in action: /
filename: /var/log/news/news.err
Called allocate_log, nlogs = 8.
cfline(news.notice -/var/log/news/news.notice)
symbolic name: notice ==> 5
symbolic name: news ==> 56
leading char in action: /
filename: /var/log/news/news.notice
Called allocate_log, nlogs = 9.
cfline(*.=warn;*.=err -/var/log/warn)
symbolic name: warn ==> 4
symbolic name: err ==> 3
leading char in action: /
filename: /var/log/warn
Called allocate_log, nlogs = 10.
cfline(*.crit /var/log/warn)
symbolic name: crit ==> 2
leading char in action: /
filename: /var/log/warn
Called allocate_log, nlogs = 11.
cfline(*.*;mail.none;news.none -/var/log/messages)
symbolic name: * ==> 255
symbolic name: none ==> 16
symbolic name: mail ==> 16
symbolic name: none ==> 16
symbolic name: news ==> 56
leading char in action: /
filename: /var/log/messages
Called allocate_log, nlogs = 12.
cfline(local0,local1.* -/var/log/localmessages)
symbolic name: * ==> 255
symbolic name: local0 ==> 128
symbolic name: local1 ==> 136
leading char in action: /
filename: /var/log/localmessages
Called allocate_log, nlogs = 13.
cfline(local2,local3.* -/var/log/localmessages)
symbolic name: * ==> 255
symbolic name: local2 ==> 144
symbolic name: local3 ==> 152
leading char in action: /
filename: /var/log/localmessages
Called allocate_log, nlogs = 14.
cfline(local4,local5.* -/var/log/localmessages)
symbolic name: * ==> 255
symbolic name: local4 ==> 160
symbolic name: local5 ==> 168
leading char in action: /
filename: /var/log/localmessages
Called allocate_log, nlogs = 15.
cfline(local6,local7.* -/var/log/localmessages)
symbolic name: * ==> 255
symbolic name: local6 ==> 176
symbolic name: local7 ==> 184
leading char in action: /
filename: /var/log/localmessages
Opened UNIX socket `/dev/log'.
symbolic name: local3 ==> 152
leading char in action: /
filename: /var/log/localmessages
Called allocate_log, nlogs = 14.
cfline(local4,local5.* -/var/log/localmessages)
symbolic name: * ==> 255
symbolic name: local4 ==> 160
symbolic name: local5 ==> 168
leading char in action: /
filename: /var/log/localmessages
Called allocate_log, nlogs = 15.
cfline(local6,local7.* -/var/log/localmessages)
symbolic name: * ==> 255
symbolic name: local6 ==> 176
symbolic name: local7 ==> 184
leading char in action: /
filename: /var/log/localmessages
Opened UNIX socket `/dev/log'.
0: 1F F F F F F F F F F X F F F F F F F F F F F F F F
TTY: /dev/tty10
1: 1F F F F F F F F F F X F F F F F F F F F F F F F F
PIPE: |/dev/xconsole
2: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
WALL:
3: X X FF X X X X X X X X X X X X X X X X X X X X X X
FILE: /var/log/mail
4: X X 7F X X X X X X X X X X X X X X X X X X X X X X
FILE: /var/log/mail.info
5: X X 1F X X X X X X X X X X X X X X X X X X X X X X
FILE: /var/log/mail.warn
6: X X F X X X X X X X X X X X X X X X X X X X X X X
FILE: /var/log/mail.err
7: X X X X X X X 7 X X X X X X X X X X X X X X X X X
FILE: /var/log/news/news.crit
8: X X X X X X X F X X X X X X X X X X X X X X X X X
FILE: /var/log/news/news.err
9: X X X X X X X 3F X X X X X X X X X X X X X X X X X
FILE: /var/log/news/news.notice
10: 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18
FILE: /var/log/warn
11: 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7
FILE: /var/log/warn
12: FF FF X FF FF FF FF X FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FILE: /var/log/messages
13: X X X X X X X X X X X X X X X X FF FF X X X X X X X
FILE: /var/log/localmessages
14: X X X X X X X X X X X X X X X X X X FF FF X X X X X
FILE: /var/log/localmessages
15: X X X X X X X X X X X X X X X X X X X X FF FF X X X
FILE: /var/log/localmessages
16: X X X X X X X X X X X X X X X X X X X X X X FF FF X
FILE: /var/log/localmessages
logmsg: syslog.info<46>, flags 4, from linux, msg syslogd 1.4.1: restart.
Called fprintlog, logging to FILE /var/log/messages
syslogd: restarted.
Debugging disabled, SIGUSR1 to turn on debugging.
Thanks,
Luca
--
Luca Ferrari,
fluca1978@virgilio.it
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2004-03-04 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOL.4.33.0403011827120.21790-200000@cupid.che.iitb.ac.in>
2004-03-04 17:51 ` Luca Ferrari [this message]
2004-03-04 20:29 ` syslog does not start terry white
2004-03-04 21:52 ` Glynn Clements
2004-03-04 21:58 ` Thomas Steudten
2004-03-14 11:23 ` Luca Ferrari
2004-03-17 19:41 ` Thomas Steudten
2004-03-01 12:58 Luca Ferrari
2004-03-01 17:09 ` terry white
2004-03-02 8:05 ` Luca Ferrari
2004-03-02 12:18 ` terry white
2004-03-02 23:14 ` Jay Goodman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200403041851.03011.fluca1978@virgilio.it \
--to=fluca1978@virgilio.it \
--cc=fluca1978REMOVE_THIS_STRING@virgilio.it \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).