This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Adam, > Hupsyslog shows nothing: > > ldm@tornado:~$ hupsyslog > ldm@tornado:~$ What was the exit-status of the "hupsyslog" execution? > ps shows: > > ldm@tornado:~$ 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 > ldm@tornado:~$ 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: > > ldm@tornado:~$ 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. > ldm@tornado:~$ > > ldm@tornado:~$ 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. > ldm@tornado:~$ > > 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