[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #WBL-938424]: LDM Logging



Adam,

> Hupsyslog shows nothing:
> 
> address@hidden:~$ hupsyslog
> address@hidden:~$

What was the exit-status of the "hupsyslog" execution?

> ps shows:
> 
> address@hidden:~$ ps -ef |grep -F syslog
> syslog     735     1  0 14:08 ?        00:00:00 rsyslogd -c5
> ldm       1306  1054  0 14:59 pts/0    00:00:00 grep --color=auto -F syslog
> address@hidden:~$

You problem could be that the system logging process is owned by "syslog" and 
that user doesn't have permission to write into the LDM log file, which has 
protection "rw-rw-r--".

> All the information that should be in /data/logs/ldmd.log is showing up in
> the /var/log/syslog file.
> 
> selinux and apparmor show:
> 
> address@hidden:~$ sudo apt-get remove selinux
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package selinux is not installed, so not removed
> 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
> address@hidden:~$
> 
> address@hidden:~$ sudo apt-get remove apparmor
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package apparmor is not installed, so not removed
> 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
> address@hidden:~$
> 
> Yes, the system was rebooted after that packages were disabled and then
> again when removed.
> 
> Thanks,
> 
> Adam

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: WBL-938424
Department: Support LDM
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.