LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Starting system logger fails (https://www.linuxquestions.org/questions/linux-newbie-8/starting-system-logger-fails-24049/)

dwynter 06-22-2002 10:26 AM

Starting system logger fails
 
Hi,

Simple question here. I wait with "Starting system logger" on the screen for 5 minutes on my Duron 1200 box and it seems to have no disk access and it then fails. Is there, perchance, a log that will tells me what is going on, or is this the actual log setup that is failing. In the latter case how do you find out what is going on? MDK 8.2 on a AMD Duron 1200 with ECS K7S5A m'board.

Thanks

David

Mara 06-22-2002 03:12 PM

Look if you have enough free space for logs - it's /var/log directory. Mandrake likes to create a separate partition for /var, so look if it's not too small.

dwynter 06-24-2002 03:13 AM

Hi,

I have 30GB free. I tried to delete the content of syslog file in /var/log and the advanced editor refused to(?). So I deleted the file altogether assuming the init would recreate it. This did not happen and therefore there is no syslog file.

I ran the syslog script for the restart to see ow it went. It gave the error as follows:
rm '/var/run/syslogd.pid' is a directory [FAILED]

I had a look and sure enough it is. I have not changed or even known this script existed. Does this mean the standard syslog script installed with MDK 8.2 is incorrect???? Probably some other cnfiguration wizard I used to set up my network and ADSL modem screwed it up?

David

Mara 06-25-2002 04:29 PM

Hmm... Have you removed the whole /var/log ? If it's true, the easiest solution is to install syslogd again (from rpm, force installation).

trickykid 06-25-2002 04:41 PM

You could maybe try this. If you don't have a syslog file in /var/log then try:

touch /var/log/syslog

this will create a new file syslog of course.. then try this to restart the syslogd services if you currently having a syslogd running:

kill -SIGHUP `cat /var/run/syslogd.pid`

dwynter 06-26-2002 03:38 PM

I solved this by reinstalling.

One thing weird was happening, not sure if had anything to do with the syslog failing. It was attempting to delete (rm) /var/run/syslogd.pid during init and failed because there was a sub directory.

The subdirectory was called /examples and had python files in it. I didn't put it there so can only assume that one of the flaky gui config tools in the Mandrake distro did it.

It should come with a warning for newbies "The X configure tools can really screw up your system use at your own risk" I know the configuration of my Speedtouch ADSL modem does it every time, as does Connection Sharing, both in the Mandrake Control Centre.


All times are GMT -5. The time now is 04:46 AM.