https://community.hpe.com/t5/operating-system-linux/no-log-registry/m-p/2843157#M2854 I am not exactly sure what your problem is, but I would look at the /etc/syslog.conf file to make sure first that it exists and also check the permissions (should be 644 owned by user and group of root)<BR /><BR />Also if all of this is correct look at the file and make sure everything appears to be right. <BR /><BR />Type: ps -ef|grep syslogd to make sure that your syslog daemon is running. If it isn't you can start it with the command: service syslog start<BR /><BR />Then you need to type: setup and check the box for syslog.<BR /><BR />If all of this is correct already then I am at a loss.<BR /><BR />Just a point for you, most of your logs should be 600 instead of giving everyone read access. Some of them give information about your system that you might not want to share.<BR /><BR />Hope some of this helps. If not, happy hunting.<BR /><BR />Jeff Tue, 12 Nov 2002 17:59:47 GMT Jeffrey S. Sims 2002-11-12T17:59:47Z https://community.hpe.com/t5/operating-system-linux/no-log-registry/m-p/2843156#M2853 <BR />I have a tremendus problem about my logs:<BR />One day just like this, all my logs stops:<BR /><BR />-rw-r--r-- 1 root root 0 Nov 10 04:02 boot.log<BR />-rw-r--r-- 1 root root 0 Nov 3 04:02 boot.log.1<BR />-rw-r--r-- 1 root root 0 Nov 10 04:02 cron<BR />-rw-r--r-- 1 root root 0 Nov 3 04:02 cron.1<BR />-rw-r--r-- 1 root root 0 May 9 2002 htmlaccess.log<BR />-rw-r--r-- 1 root root 0 Nov 10 04:02 maillog<BR />-rw-r--r-- 1 root root 0 Nov 3 04:02 maillog.1<BR />-rw-r--r-- 1 root root 0 Nov 10 04:02 messages<BR />-rw-r--r-- 1 root root 0 Nov 3 04:02 messages.1<BR />-rw-r--r-- 1 root root 0 Nov 1 04:02 netconf.log<BR />-rw-r--r-- 1 root root 0 Oct 1 04:02 netconf.log.1<BR />-rw-r--r-- 1 root root 0 Sep 1 04:02 netconf.log.2<BR />-rw-r--r-- 1 root root 0 Feb 16 2002 reconfig.log<BR />-rw-r--r-- 1 root root 0 Nov 10 04:02 secure<BR />-rw-r--r-- 1 root root 0 Nov 3 04:02 secure.1<BR />-rw-r--r-- 1 root root 0 Nov 10 04:02 spooler<BR />-rw-r--r-- 1 root root 0 Nov 3 04:02 spooler.1<BR />-rw-r--r-- 1 root root 0 Oct 27 04:02 spooler.2<BR />-rw-r--r-- 1 root root 0 Oct 20 04:02 spooler.3<BR />-rw-r--r-- 1 root root 0 Oct 13 04:02 spooler.4<BR /><BR />Does any one know a comun problem of it?<BR />I'm working under Linux Red Hat 7.2<BR /><BR />PLZ some one help me!!!!<BR /> Tue, 12 Nov 2002 14:34:01 GMT https://community.hpe.com/t5/operating-system-linux/no-log-registry/m-p/2843156#M2853 Samuel Martinez 2002-11-12T14:34:01Z https://community.hpe.com/t5/operating-system-linux/no-log-registry/m-p/2843157#M2854 I am not exactly sure what your problem is, but I would look at the /etc/syslog.conf file to make sure first that it exists and also check the permissions (should be 644 owned by user and group of root)<BR /><BR />Also if all of this is correct look at the file and make sure everything appears to be right. <BR /><BR />Type: ps -ef|grep syslogd to make sure that your syslog daemon is running. If it isn't you can start it with the command: service syslog start<BR /><BR />Then you need to type: setup and check the box for syslog.<BR /><BR />If all of this is correct already then I am at a loss.<BR /><BR />Just a point for you, most of your logs should be 600 instead of giving everyone read access. Some of them give information about your system that you might not want to share.<BR /><BR />Hope some of this helps. If not, happy hunting.<BR /><BR />Jeff Tue, 12 Nov 2002 17:59:47 GMT https://community.hpe.com/t5/operating-system-linux/no-log-registry/m-p/2843157#M2854 Jeffrey S. Sims 2002-11-12T17:59:47Z