Syslog_ng-2.0.2-Post install reboot problems
Hi All, Please sugget me the possible cause of the below error message. ********************************************************************************************************** The following error message is seen during a post install reboot. This appears to be related to the installation of the Syslog_ng-2.0.2 . These messages will appear during system startups and additional messages will be generated as a result of the setroubleshootd daemon not being present. Subsequent removal the Syslog_ng-2.0.2 corrects this issue. Starting setroubleshootd: [ OK ] Starting NFS statd: [ OK ] Traceback (most recent call last): File "/usr/sbin/setroubleshootd", line 59, in ? from setroubleshoot.config import cfg File "/usr/lib/python2.4/site-packages/setroubleshoot/__init__.py", line 24, in ? log_init(sys.argv[0]) File "/usr/lib/python2.4/site-packages/setroubleshoot/log.py", line 127, in log_init syslog = logging.handlers.SysLogHandler(address='/dev/log') File "/usr/lib64/python2.4/logging/handlers.py", line 602, in __init__ self._connect_unixsocket(address) File "/usr/lib64/python2.4/logging/handlers.py", line 617, in _connect_unixsocket self.socket.connect(address) File "<string>", line 1, in connect socket.error: (13, 'Permission denied') Starting RPC idmapd: [ OK ] Starting system message bus: [ OK ] Starting Bluetooth services: [ OK ] ***************************************************************************************************** Thanks --------------------------------- Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your freeaccount today.
On Thu, 2007-08-02 at 13:47 +0100, Shamim wrote:
Hi All, Please sugget me the possible cause of the below error message. ********************************************************************************************************** The following error message is seen during a post install reboot. This appears to be related to the installation of the Syslog_ng-2.0.2 . These messages will appear during system startups and additional messages will be generated as a result of the setroubleshootd daemon not being present. Subsequent removal the Syslog_ng-2.0.2 corrects this issue.
Starting setroubleshootd: [ OK ] Starting NFS statd: [ OK ] Traceback (most recent call last): File "/usr/sbin/setroubleshootd", line 59, in ? from setroubleshoot.config import cfg File "/usr/lib/python2.4/site-packages/setroubleshoot/__init__.py", line 24, in ? log_init(sys.argv[0]) File "/usr/lib/python2.4/site-packages/setroubleshoot/log.py", line 127, in log_init syslog = logging.handlers.SysLogHandler(address='/dev/log') File "/usr/lib64/python2.4/logging/handlers.py", line 602, in __init__ self._connect_unixsocket(address) File "/usr/lib64/python2.4/logging/handlers.py", line 617, in _connect_unixsocket self.socket.connect(address) File "<string>", line 1, in connect socket.error: (13, 'Permission denied')
setroubleshoot had no permission to access /dev/log. Check the owner/group/permission settings of /dev/log. -- Bazsi
participants (2)
-
Balazs Scheidler
-
Shamim