Bo Larses
2002-Jan-20 13:58 UTC
Problems with Samba, INIT during boot, respawning too fast...
Hi, I administer a LinuxPPC-server (June 1999, kernel 2.2.6 on a B&W G3) running with Samba 2.0.6 which serves about 10 Windows-clients and Netatalk for a few Mac:s. I am not totally new to Linux, but still bit of a newbie. Suddenly the Windows-clients couldn?t connect to the Linux server. But Mac/netatalk works perfectly. I tried to restart Samba through SWAT. The status of smbd shows "running" and nmbd is "not running". It is not possible to change this by clicking on stop/start/restart, nothing happens. Earlier nmbd sometimes stopped for no obvious reason, but could be started again by clicking on "start nmbd" a few times. So there is something wrong here I guess. Then I rebooted the linux box (for the first time in several months). On startup there was several problems with the file systems, so the whole thing halted at something like this: ------------------ /dev/sdb5 : UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY (e.g.without -a or -p options[FAILED] *** An error occured during the filesystem check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. Give root password for maintenance (or type ctrl-D for manual startup). >> ------------------------ So I did run "fsck /dev/sdb5" and there was a lot of faults and fixing (I answered the default "Yes" on every prompt). Then reboot again. It worked a little bit better now, no problems with sdb5, but some checking on the other disks. They came out OK. But during startup: ------------------------------------------ INIT: version 2.74 booting [FAILED] ---------------------------------------------- (the rest is OK, ant then after linuxconf is started:) ------------------------------------------- linux_server login: gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting INIT: Id "x" respawning too fast: disabled for 5 minutes. -------------------------------------------------------------- And the whole thing looped until I pressed Enter and a login prompt came up. Xwindow did not start as it used to before. Trying to solve the respawning problem I did what they recommend at: http://www.linuxppc.com/support/updates/product/archive.php3?category=general&subject=respawning-too-fast --------------------------------- "Boot up the computer, and when it gets to the "Choose your OS" screen, press the delete key. This will stop the boot process. Delete anything that is in the "More kernel arguments" field. In that field, type in "single". Then click Linux to start Linux. Linux will boot in single user mode, which is a special maintenance mode. Instead of booting up and displaying a login prompt, it will come to a prompt: sh-2.0.3# At this prompt, type: /usr/X11R6/bin/Xautoconfig [Return] It will look like nothing happened, but the Xautoconfig program actually ran. I t should properly set up your X configuration." ------------------------------------------- It did not solve the problem, though. When I reboot there is still problems with "INIT: version 2.74 booting [FAILED]" and the "respawning too fast"-thing. But I can login as root and start Xwindow manually thru "startx". When (in Xwindow) I start a terminal window the prompt is "sh2.03#". Single user mode? Why? And the most important issue - to get the filesharing thru Samba going - is still to be solved. It is critical that I fix this asap because the company relies on computers working. I am running out of clues on how to fix all this. Are all these problems connected, and how do I solve them? Any ideas? Thanks. -------------- next part -------------- HTML attachment scrubbed and removed
Bo Larses
2002-Jan-20 13:59 UTC
Problems with Samba, INIT during boot, respawning too fast...
Hi, I administer a LinuxPPC-server (June 1999, kernel 2.2.6 on a B&W G3) running with Samba 2.0.6 which serves about 10 Windows-clients and Netatalk for a few Mac:s. I am not totally new to Linux, but still bit of a newbie. Suddenly the Windows-clients couldn?t connect to the Linux server. But Mac/netatalk works perfectly. I tried to restart Samba through SWAT. The status of smbd shows "running" and nmbd is "not running". It is not possible to change this by clicking on stop/start/restart, nothing happens. Earlier nmbd sometimes stopped for no obvious reason, but could be started again by clicking on "start nmbd" a few times. So there is something wrong here I guess. Then I rebooted the linux box (for the first time in several months). On startup there was several problems with the file systems, so the whole thing halted at something like this: ------------------ /dev/sdb5 : UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY (e.g.without -a or -p options[FAILED] *** An error occured during the filesystem check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. Give root password for maintenance (or type ctrl-D for manual startup). >> ------------------------ So I did run "fsck /dev/sdb5" and there was a lot of faults and fixing (I answered the default "Yes" on every prompt). Then reboot again. It worked a little bit better now, no problems with sdb5, but some checking on the other disks. They came out OK. But during startup: ------------------------------------------ INIT: version 2.74 booting [FAILED] ---------------------------------------------- (the rest is OK, ant then after linuxconf is started:) ------------------------------------------- linux_server login: gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting INIT: Id "x" respawning too fast: disabled for 5 minutes. -------------------------------------------------------------- And the whole thing looped until I pressed Enter and a login prompt came up. Xwindow did not start as it used to before. Trying to solve the respawning problem I did what they recommend at: http://www.linuxppc.com/support/updates/product/archive.php3?category=general&subject=respawning-too-fast --------------------------------- "Boot up the computer, and when it gets to the "Choose your OS" screen, press the delete key. This will stop the boot process. Delete anything that is in the "More kernel arguments" field. In that field, type in "single". Then click Linux to start Linux. Linux will boot in single user mode, which is a special maintenance mode. Instead of booting up and displaying a login prompt, it will come to a prompt: sh-2.0.3# At this prompt, type: /usr/X11R6/bin/Xautoconfig [Return] It will look like nothing happened, but the Xautoconfig program actually ran. I t should properly set up your X configuration." ------------------------------------------- It did not solve the problem, though. When I reboot there is still problems with "INIT: version 2.74 booting [FAILED]" and the "respawning too fast"-thing. But I can login as root and start Xwindow manually thru "startx". When (in Xwindow) I start a terminal window the prompt is "sh2.03#". Single user mode? Why? And the most important issue - to get the filesharing thru Samba going - is still to be solved. It is critical that I fix this asap because the company relies on computers working. I am running out of clues on how to fix all this. Are all these problems connected, and how do I solve them? Any ideas? Thanks.
Michael Heironimus
2002-Jan-20 14:29 UTC
Problems with Samba, INIT during boot, respawning too fast...
It seems fairly obvious that you have severe filesystem corruption.
Samba stopped working as a result. I would say you should just wipe that
filesystem (/dev/sdb5) and reinstall or restore from backup, but that
still leaves the question of why your filesystem became corrupted in the
first place. I assume that sdb5 is your root filesystem, gdm tries and
fails to start because its configuration file was lost in the
corruption.
--
That feeling just came over me.
-- Albert DeSalvo, the "Boston Strangler"
Joel Hammer
2002-Jan-20 14:33 UTC
Problems with Samba, INIT during boot, respawning too fast...
If no one with a better idea chimes in, I would say you have got a hardware problem. Now is when you find out if your backup system is going to work. It suggests your hard drive is bad. Now, you do not need swat to run samba. You can run samba fine from the command line (telinit 3). You can start smbd and nmbd from a startup script. You should know where samba is keeping its lock files and pid files. If you don't know, one way is to use the string command, eg: strings `which smbd` | grep / | less Mine are in /usr/local/samba/var/locks, despite what this startup script below says. Joel #!/bin/bash case "$1" in start) killall smbd killall nmbd /usr/local/samba/bin/smbd -D /usr/local/samba/bin/nmbd -D ;; stop) killall smbd killall nmbd ;; reload) kill -SIGHUP `cat /var/lock/samba/smbd.pid` kill -SIGHUP `cat /var/lock/samba/nmbd.pid` ;; *) echo Usage: echo start stop reload ;; esac exit 0 Joel> Hi, > I administer a LinuxPPC-server (June 1999, kernel 2.2.6 on a B&W G3) running with Samba 2.0.6 which serves about 10 Windows-clients and Netatalk for a few Mac:s. I am not totally new to Linux, but still bit of a newbie. > > Suddenly the Windows-clients couldn?t connect to the Linux server. But Mac/netatalk works perfectly. > > I tried to restart Samba through SWAT. The status of smbd shows "running" and nmbd is "not running". It is not possible to change this by clicking on stop/start/restart, nothing happens. Earlier nmbd sometimes stopped for no obvious reason, but could be started again by clicking on "start nmbd" a few times. So there is something wrong here I guess. > > Then I rebooted the linux box (for the first time in several months). On > startup there was several problems with the file systems, so the whole > thing halted at something like this: > ------------------<ul> > /dev/sdb5 : UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY (e.g.without -a or -p options[FAILED] > > *** An error occured during the filesystem check. > *** Dropping you to a shell; the system will reboot > *** when you leave the shell. > Give root password for maintenance > (or type ctrl-D for manual startup). >> > ------------------------ > So I did run "fsck /dev/sdb5" and there was a lot of faults and fixing (I answered the default "Yes" on every prompt). Then reboot again. It worked a little bit better now, no problems with sdb5, but some checking on the other disks. They came out OK. > > > But during startup: > ------------------------------------------ > INIT: version 2.74 booting [FAILED] > ---------------------------------------------- > (the rest is OK, ant then after linuxconf is started:) > ------------------------------------------- > linux_server login: gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting > gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting > gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting > gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting > gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting > gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting > gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting > gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting > gdm_config_parse: no configuration file: /etc/X11/gdm.conf. Aborting > INIT: Id "x" respawning too fast: disabled for 5 minutes. > -------------------------------------------------------------- > > And the whole thing looped until I pressed Enter and a login prompt came up. Xwindow did not start as it used to before. > > Trying to solve the respawning problem I did what they recommend at: > > http://www.linuxppc.com/support/updates/product/archive.php3?category=general&subject=respawning-too-fast > --------------------------------- > "Boot up the computer, and when it gets to the "Choose your OS" screen, press the delete key. This will stop the boot process. > Delete anything that is in the "More kernel arguments" field. In that field, type in "single". Then click Linux to start Linux. > > Linux will boot in single user mode, which is a special maintenance mode. Instead of booting up and displaying a login prompt, it will come to a prompt: > sh-2.0.3# > At this prompt, type: /usr/X11R6/bin/Xautoconfig [Return] > > It will look like nothing happened, but the Xautoconfig program actually ran. I t should properly set up your X configuration." > ------------------------------------------- > > It did not solve the problem, though. When I reboot there is still problems with "INIT: version 2.74 booting [FAILED]" and the "respawning too fast"-thing. But I can login as root and start Xwindow manually thru "startx". > When (in Xwindow) I start a terminal window the prompt is "sh2.03#". Single user mode? Why? > > And the most important issue - to get the filesharing thru Samba going - is still to be solved. It is critical that I fix this asap because the company relies on computers working. > > I am running out of clues on how to fix all this. Are all these problems connected, and how do I solve them? Any ideas? Thanks. > >