All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
RE: syslogd failing to start
|
Logged in as: Guest |
Users viewing this topic: none |
|
Login  |
|
|
RE: syslogd failing to start - Jan. 1, '05, 12:07:16 PM
|
|
|
Rodney
Posts: 2916
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Okay I look over there.
I'm having to work-around a FIFO bug so, not too surprising something crops up.
|
|
|
RE: syslogd failing to start - Jan. 1, '05, 2:58:10 PM
|
|
|
Rodney
Posts: 2916
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
The openssh-3.9.0.1.2 is just an update for syslog (compared to 3.9.0.1.1).
So no other changes.
|
|
|
RE: syslogd failing to start - Feb. 6, '06, 4:08:46 PM
|
|
|
Cthulhu
Posts: 14
Joined: Mar. 3, '04,
Status: offline
|
Hi,
I have similar problem: at my hosts syslogd works only on domain controlers, but not on workstations/member servers. Syslogd version: 1.1.3.2
/etc/services: checked and converted
OS: XP Pro SP2 Polish/2003 Std English
firewals: none or wipfw.
When I try to start syslogd
/etc/init.d/syslog start
I receive syslog started message but nothing was happened - ps -eX unix show no syslogd process
When I try
/usr/sbin/syslogd - the same
I have no idea what should I do to force syslogd to run :(
|
|
|
RE: syslogd failing to start - Feb. 6, '06, 5:01:02 PM
|
|
|
Rodney
Posts: 2916
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Version 1.1.3.2 is the latest version.
When you start syslogd use the '-d' option (debug on; more
details on the man page). See what it shows. Post the results here
if that doesn't point to the problem.
< Message edited by Rodney -- Feb. 10, '06, 12:55:54 AM >
|
|
|
RE: syslogd failing to start - Feb. 8, '06, 3:32:42 AM
|
|
|
Cthulhu
Posts: 14
Joined: Mar. 3, '04,
Status: offline
|
WindowsXP:
bash-3.00$ /usr/sbin/syslogd -d
setsockopt(SO_EXCLUSIVEADDRUSE): success
syslogd: bind: Address already in use
Active ports shows:
psxss.exe 1892 0.0.0.0 514 LISTEN UDP \??\C:\WINDOWS\system32\psxss.exe
why?
Windows2003:
setsockopt(SO_EXCLUSIVEADDRUSE): success
off & running....
init
cfline(*.err;kern.*;auth.notice;authpriv.none;mail.crit /dev/console)
cfline(*.notice;*.info;authpriv,ftp.none;kern.debug;mail.crit /var/adm/log/mes
sages)
cfline(mail.* /var/adm/log/mai
l)
cfline(ftp.* /var/adm/log/ftp
)
cfline( daemon.* /var/adm/log/dae
mon)
syslogd: unknown facility name " daemon"
logmsg: pri 53, flags 4, from fluent-2, msg syslogd: unknown facility name " dae
mon"
cfline( *.alert EE+Administrator)
cfline( *.err,authpriv.none EE+Administrator)
cfline( *.notice;auth.debug EE+Administrator)
8 3 2 3 5 3 3 3 3 3 X 3 3 3 3 3 3 3 3 3 3 3 3 3 X CONSOLE: /dev/console
7 6 2 6 6 6 6 6 6 6 X X 6 6 6 6 6 6 6 6 6 6 6 6 X FILE: /var/adm/log/messages
X X 8 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/adm/log/mail
X X X X X X X X X X X 8 X X X X X X X X X X X X X FILE: /var/adm/log/ftp
X X X X X X X X X X X X X X X X X X X X X X X X X UNUSED:
X X X X X X X X X X X X X X X X X X X X X X X X X WALL:
X X X X X X X X X X X X X X X X X X X X X X X X X WALL:
X X X X X X X X X X X X X X X X X X X X X X X X X WALL:
logmsg: pri 56, flags 4, from fluent-2, msg syslogd: restart
Logging to FILE /var/adm/log/messages
syslogd: restarted
readfds = 0x8
readfds = 0x8 and so on...
sometimes appear:
logmsg: pri 6, flags c, from fluent-2, msg -- MARK --
< Message edited by Cthulhu -- Feb. 8, '06, 4:09:39 AM >
|
|
|
RE: syslogd failing to start - Feb. 8, '06, 4:28:46 AM
|
|
|
Rodney
Posts: 2916
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> syslogd: bind: Address already in use
Okay, so this is the answer as to why syslogd won't start.
> psxss.exe 1892 0.0.0.0 514 LISTEN UDP \??\C:\WINDOWS\system32\psxss.exe
> why?
Because all of the Interix socket calls go through the Interix subsystem (PSXSS.EXE).
So there is another Interix program running that has 514/UDP.
Take another look at the process list and see if there is already another "syslogd" program running.
A "ps -A -Xunix" will show just the Interix processes (Active and zombies).
You should see that syslogd is already running and logging.
If not then something is odd and I'd just reboot the system. This should clear everything and
a syslogd should get started as part of the reboot.
|
|
|
RE: syslogd failing to start - Feb. 8, '06, 6:13:32 AM
|
|
|
Cthulhu
Posts: 14
Joined: Mar. 3, '04,
Status: offline
|
quote:
ORIGINAL: Rodney
> syslogd: bind: Address already in use
Okay, so this is the answer as to why syslogd won't start.
> psxss.exe 1892 0.0.0.0 514 LISTEN UDP \??\C:\WINDOWS\system32\psxss.exe
> why?
Because all of the Interix socket calls go through the Interix subsystem (PSXSS.EXE).
So there is another Interix program running that has 514/UDP.
Take another look at the process list and see if there is already another "syslogd" program running.
A "ps -A -Xunix" will show just the Interix processes (Active and zombies).
You should see that syslogd is already running and logging.
If not then something is odd and I'd just reboot the system. This should clear everything and
a syslogd should get started as part of the reboot.
hmmm... ok, I am tired a little bit... :)
On my XP everything works well, but on W2k3 something is going wrong, but I'll be back with this case later (now I lost connection with this machine)
Big thanks Rodney!
|
|
|
RE: syslogd failing to start - Feb. 8, '06, 7:11:14 AM
|
|
|
Cthulhu
Posts: 14
Joined: Mar. 3, '04,
Status: offline
|
The saga continues :)
bash-3.00$ syslogd -d
syslogd: syslog/udp: unknown service
logmsg: pri 053, flags 0x4, from fluent-2, msg syslogd: syslog/udp: unknown service
bash-3.00$ cat /etc/services |grep 514
cmd 514/tcp shell
syslog 514/udp
|
|
|
RE: syslogd failing to start - Feb. 10, '06, 12:41:37 AM
|
|
|
markfunk
Posts: 622
Joined: Mar. 31, '03,
Status: offline
|
syslogd uses the api getservbyname() to find this info.
It does not look directly at /etc/services.
The Interix getservbyname() api relys directly on the
WinSOCK getservbyname() api, which eventually uses
the file %windir%/system32/drivers/etc/services.
|
|
|
RE: syslogd failing to start - Feb. 10, '06, 1:15:16 AM
|
|
|
Rodney
Posts: 2916
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
But earlier Cthulhu said he is using syslogd 1.1.3.2 which is linked
with the newer BIND which uses it's own getservbyname(), not the Interix subsystem version.
And libbind does look at /etc/services. It shouldn't have a line ending problem (DOS vs Unix)
because that's been programmed into BIND to handle it.
Maybe some other invisible character is in the /etc/services file though?
|
|
|
RE: syslogd failing to start - Feb. 10, '06, 2:52:25 PM
|
|
|
markfunk
Posts: 622
Joined: Mar. 31, '03,
Status: offline
|
He also says that he's using /usr/sbin/syslogd.
The Interop pkgs are installing in /usr/local/bin, right ? (I sure hope so).
|
|
|
RE: syslogd failing to start - Feb. 10, '06, 6:08:48 PM
|
|
|
Rodney
Posts: 2916
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> He also says that he's using /usr/sbin/syslogd.
Did he? okay. Some confusion to sort out then.
> The Interop pkgs are installing in /usr/local/bin, right ? (I sure hope so).
The /Tools syslogd installs in /usr/local/sbin.
Cthulhu:
The startup script /etc/init.d/syslog should, after the /Tools syslogd is installed,
point at the /usr/local/sbin/syslogd binary.
Try starting "/usr/local/sbin/syslogd -d" to see what the output is.
|
|
|
RE: syslogd failing to start - Feb. 12, '06, 12:09:29 PM
|
|
|
Cthulhu
Posts: 14
Joined: Mar. 3, '04,
Status: offline
|
quote:
ORIGINAL: Rodney
> He also says that he's using /usr/sbin/syslogd.
Did he? okay. Some confusion to sort out then.
> The Interop pkgs are installing in /usr/local/bin, right ? (I sure hope so).
The /Tools syslogd installs in /usr/local/sbin.
Cthulhu:
The startup script /etc/init.d/syslog should, after the /Tools syslogd is installed,
point at the /usr/local/sbin/syslogd binary.
Try starting "/usr/local/sbin/syslogd -d" to see what the output is.
bash-3.00$ /usr/local/sbin/syslogd -d
syslogd: syslog/udp: unknown service
logmsg: pri 053, flags 0x4, from warta11, msg syslogd: syslog/udp: unknown servi
ce
bash-3.00$
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
|
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|