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

Re: Broken startup; syslogd hangs...



Interesting, and thanks for the note.

The notable thing here is that this system was perfectly working before the re-boot,
running X, Apache, servlets, etc..

Then the re-boot killed stuff. I had unintentionally laid the problem basis, resorted an old fstab, and .. now, what else!

So, I don't think it is any hardware.

I scanned the tar archive, but couldn't find anything else dangerous that got restored..

Greg



At 11:39 AM 05/14/2000 +0930, John Pearson wrote:
On Sat, May 13, 2000 at 01:39:20PM -0500, Gregory Guthrie wrote
> At 10:10 AM 05/13/2000 +0930, John Pearson wrote:
> >On Fri, May 12, 2000 at 04:49:21PM -0500, Gregory Guthrie wrote
> > > Help!!
> > >
> > > I had a working system, and after several weeks up we were moving some
> > > (Apache) files around and wanted to make sure that the system setup for
> > > Apache was OK, se we re-booted.
> > >
> > > At re-boot I now get:
> >...
> >It's trying to fsck your extneded partition, rather than your true root
> >partition.  My guess is that /etc/fstab is wrong, and that it lists
> >/dev/hda1 as root instead of /dev/hda6.  The fact that you get to
> >single-user mode means that hte kernel and LILO are configured correctly.
>
> -- John, Bingo. Thanks.
>
> I now have another problem..
>
> The boot goes into
>
> INIT: entering run level 2
> Starting system log daemon: syslogd
>
> and hangs...
>

Funny thing - I had the *exact same thing* the other day setting
up a new machine.  I didn't formally diagnose the problem, but
noticed that the fancy new MB (MB 6136PRO) I was using had
assigned the same IRQ to 2 network cards and my SCSI controller.
I fixed it by shuffling cards and re-installing (after tearing
my hair out for an hour or three, and on a machine with no user
data on it, it seemed the expedient thing).

Assuming you already have good hardware and no resource conflicts,
try re-installing the sysklogd package in case the problem is a
corrupt file.

> I edited /etc/rc2.d/S10sysklogd -> /etc/init.d/sysklogd to give hello
> messages, and find that is hangs on the actual call to start /sbin/syslogd.
> Commenting out this call and everything seems to run OK as far as I can
> tell. Trying to manually start syslogd also hangs. I notice that during
> boot a ctl-break shows a ps like table of processes, and that does show two
> instances of syslogd running.
>
> Any ideas?
>
> The other broken symptom is that networking does not work; ifconfig reports
> everything fine, but ping hangs, and the hub shows the link not active.
> During boot the ethernet card shows proper initialization, and seems OK.
>

This is almost uncanny - the one unresolved issue with the
machine I mentioned above is a 3c905 Bommerand card that
configures OK, but passes no packets; ping, telnet, etc. all
return no output, and the packet counters shown by ifconfig are
stuck at zero.  I'm back to the site today with a DOS boot disk
and 3Com's configuration utility to see if disabling Plug'n'Play
mode (or some similar trick) fixes things.  Maybe you should
look into that?


John P.
--
huiac@camtech.net.au
john@huiac.apana.org.au
http://www.mdt.net.au/~john Debian Linux admin & support:technical services

--------------------------------------------------------
Dr. Gregory Guthrie
guthrie@mum.edu         (515)472-1125    Fax: -1103
       Computer Science Department
       College of Science and Technology
       Maharishi University of Management
      (Maharishi International University 1971-1995)
        http://www.mum.edu/cs_dept
--------------------------------------------------------



Reply to: