RE: RHEL 4 Syslog refuses to work

["Collins, Kevin (MindWorks)" <KCollins chevron com>]

You can try:

sh -vx  /etc/init.d/syslog start

Tracing the shell script may (or may not) give a clue to the problem...

Kevin

-----Original Message-----
From: nahant-list-bounces redhat com
[mailto:nahant-list-bounces redhat com] On Behalf Of Andrew Gnezdilov
Sent: Thursday, July 14, 2005 12:22 AM
To: nahant-list redhat com
Subject: RHEL 4 Syslog refuses to work

Hi,

The problem: Syslog daemon ceases to work when /var subtree is located
on a separate logical disk.

Environment:

Red Hat Enterprise Linux ES release 4
kernel-smp-2.6.9-11.EL.i686
lvm2-2.01.08-1.0.RHEL4.i386
sysklogd-1.4.1-26_EL.i386

Disk space is controlled by LVM. There are several logical volumes
created within one volume group. Here is my /etc/fstab:

# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/SystemRoot /                    ext3    defaults
1 1
LABEL=/boot             /boot                   ext3    defaults
1 2
/dev/VolGroup00/SystemData /var                 ext3    defaults
1 2
/dev/VolGroup00/SystemWorkspace /tmp            ext2    defaults
1 2
/dev/VolGroup00/SystemUsers /home               ext3    defaults
1 2
/dev/VolGroup00/Apps /opt                       ext3    defaults
1 2
/dev/VolGroup00/Distribs /srv                   ext3    defaults
0 0
none                    /dev/pts                devpts  gid=5,mode=620
0 0
none                    /dev/shm                tmpfs   defaults
0 0
none                    /proc                   proc    defaults
0 0
none                    /sys                    sysfs   defaults
0 0
/dev/VolGroup00/SystemSwap swap                    swap    defaults
0
0
/dev/hda                /media/cdrom            auto
pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0
0
/dev/fd0                /media/floppy           auto
pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0
0

When I try to start Syslog daemon by command:

/etc/init.d/syslog start

it waits some time and fails to start syslogd with no
explanations. After that, /dev/log socket is created but have somewhat
strange access permissions: "srwxr-xr-x" instead of
"srw-rw-rw-". /var/run/syslogd.pid and /var/lock/subsys/syslog are not
created.

If I try to run Syslog daemon in debuging mode by command

syslogd -d

it starts but doesn't work and prints no messages, though /dev/log in
that case has right permissions: "srw-rw-rw-".

Andrew.

--
nahant-list mailing list
nahant-list redhat com
http://www.redhat.com/mailman/listinfo/nahant-list