LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices



Reply
 
Search this Thread
Old 12-27-2009, 05:05 PM   #1
ShiningMasamune
LQ Newbie
 
Registered: Oct 2008
Posts: 7

Rep: Reputation: 0
Exclamation Boot problems after Karmic upgrade, Samba and OpenVPN not starting


Greetings all. I apologize for posting another thread when I already have one active, but this one is a bit more serious. I've just upgraded my Ubuntu server from Jaunty to Karmic, and it seems to have been a pretty rocky process. I have a number of problems, and I'm not sure how many are related, so I'll just list them:

Near the beginning of the boot process, I see: "init: ureadahead-other main process (705) terminated with status 4"

At a seemingly random (?!) point between the "Starting this or that" lines, I see "mountall: Event failed". I don't know what this is in relation to, but my filesystems are all mounted fine, it would seem.

About 1 or 2 seconds after I see the login prompt (?!!), more messages come in:
Stopping NTP server ntdp
Restarting OpenBSD Secure Shell server sshd
Starting NTP server ntpd

Finally, and most alarmingly, once all the dust settles it seems that not all my daemons have started successfully, despite no error messages related to them appearing. Specifically, neither the Samba nor OpenVPN daemons are running. "Starting Samba daemons" does appear when booting, but the daemon is not running when the boot is complete. Executing "/etc/init.d/samba restart" shows "no such process" when trying to stop the daemon, but after this, the daemon is started successfully and appears to work fine. Same for OpenVPN. Other daemons such as sshd appear to be working. I don't know if it's only those two, or what.

Once I restart them both, they appear to work fine, but this is still very alarming... Help!

Last edited by ShiningMasamune; 12-27-2009 at 05:08 PM.
 
Old 12-28-2009, 08:18 PM   #2
sonichedgehog
Member
 
Registered: Oct 2007
Location: London UK
Distribution: Fedora Core 17
Posts: 296

Rep: Reputation: 32
I upgraded, and found a variety of problems. Eg I note that samba is not installed on karmic by default. Some things just stopped working.

On a positive note, a clean Karmic install solved issues that needed special arrangments in 9.04, eg network card not supported, mp3 previously needed LAME built from source.

May I suggest clean install using karmic. If you have been using 9.04 for a while, you might consider using your home directory within the new OS- that will preserve email, bookmarks, desktop settings, etc. If you have /home in a separate partition, this is easy, but there are many ways of achieving this. Otherwise back up and do a fresh install.
 
Old 12-28-2009, 08:45 PM   #3
ShiningMasamune
LQ Newbie
 
Registered: Oct 2008
Posts: 7

Original Poster
Rep: Reputation: 0
Thanks for your reply, but unfortunately, reinstalling is not really an option for me.

I'd appreciate it if someone could at least tell me what logs I could be looking through to diagnose these problems.
 
Old 12-29-2009, 06:46 AM   #4
sonichedgehog
Member
 
Registered: Oct 2007
Location: London UK
Distribution: Fedora Core 17
Posts: 296

Rep: Reputation: 32
From your posts I believe you will be able to interpret the logs as well as, if not better than, I could. /var/log is the path, the various dmesg files and syslog files will show your history. My daemon.log appears to have similar content to syslog.

I don't know whether it will help you to compare your startup scripts with mine (a recent install without significant modification). Here are 2 key areas, which might be a good starting point:

Code:
:/etc/rc5.d$ ls -l
total 4
-rw-r--r-- 1 root root 677 2009-11-10 09:44 README
lrwxrwxrwx 1 root root  20 2009-12-14 20:31 S20kerneloops -> ../init.d/kerneloops
lrwxrwxrwx 1 root root  15 2009-12-25 11:45 S20samba -> ../init.d/samba
lrwxrwxrwx 1 root root  27 2009-12-14 20:31 S20speech-dispatcher -> ../init.d/speech-dispatcher
lrwxrwxrwx 1 root root  19 2009-12-14 20:31 S25bluetooth -> ../init.d/bluetooth
lrwxrwxrwx 1 root root  14 2009-12-14 20:31 S50cups -> ../init.d/cups
lrwxrwxrwx 1 root root  20 2009-12-14 20:31 S50pulseaudio -> ../init.d/pulseaudio
lrwxrwxrwx 1 root root  15 2009-12-14 20:31 S50rsync -> ../init.d/rsync
lrwxrwxrwx 1 root root  15 2009-12-14 20:31 S50saned -> ../init.d/saned
lrwxrwxrwx 1 root root  19 2009-12-14 20:31 S70dns-clean -> ../init.d/dns-clean
lrwxrwxrwx 1 root root  18 2009-12-14 20:31 S70pppd-dns -> ../init.d/pppd-dns
lrwxrwxrwx 1 root root  24 2009-12-14 20:31 S90binfmt-support -> ../init.d/binfmt-support
lrwxrwxrwx 1 root root  22 2009-12-14 20:31 S99acpi-support -> ../init.d/acpi-support
lrwxrwxrwx 1 root root  21 2009-12-14 20:31 S99grub-common -> ../init.d/grub-common
lrwxrwxrwx 1 root root  21 2009-12-14 20:31 S99laptop-mode -> ../init.d/laptop-mode
lrwxrwxrwx 1 root root  18 2009-12-14 20:31 S99ondemand -> ../init.d/ondemand
lrwxrwxrwx 1 root root  18 2009-12-14 20:31 S99rc.local -> ../init.d/rc.local
lrwxrwxrwx 1 root root  18 2009-12-14 22:11 S99timidity -> ../init.d/timidity
Take a look at samba, which is one of your problem areas:

Code:
:/etc/init.d$ cat samba
#!/bin/sh

### BEGIN INIT INFO
# Provides:          samba
# Required-Start:    $network $local_fs $remote_fs
# Required-Stop:     $network $local_fs $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Should-Start:      slapd
# Should-Stop:       slapd
# Short-Description: start Samba daemons (nmbd and smbd)
### END INIT INFO


# Defaults
RUN_MODE="daemons"

# Reads config file (will override defaults above)
[ -r /etc/default/samba ] && . /etc/default/samba

PIDDIR=/var/run/samba
NMBDPID=$PIDDIR/nmbd.pid
SMBDPID=$PIDDIR/smbd.pid

# clear conflicting settings from the environment
unset TMPDIR

# See if the daemons are there
test -x /usr/sbin/nmbd -a -x /usr/sbin/smbd || exit 0

. /lib/lsb/init-functions

case "$1" in
	start)
		log_daemon_msg "Starting Samba daemons"
		# Make sure we have our PIDDIR, even if it's on a tmpfs
		install -o root -g root -m 755 -d $PIDDIR

		NMBD_DISABLED=`testparm -s --parameter-name='disable netbios' 2>/dev/null`
		if [ "$NMBD_DISABLED" != 'Yes' ]; then
			log_progress_msg "nmbd"
			if ! start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/nmbd -- -D
			then
				log_end_msg 1
				exit 1
			fi
		fi

		if [ "$RUN_MODE" != "inetd" ]; then
			log_progress_msg "smbd"
			if ! start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/smbd -- -D; then
				log_end_msg 1
				exit 1
			fi
		fi

		log_end_msg 0
		;;
	stop)
		log_daemon_msg "Stopping Samba daemons"
		log_progress_msg "nmbd"

		start-stop-daemon --stop --quiet --pidfile $NMBDPID
		# Wait a little and remove stale PID file
		sleep 1
		if [ -f $NMBDPID ] && ! ps h `cat $NMBDPID` > /dev/null
		then
			# Stale PID file (nmbd was succesfully stopped),
			# remove it (should be removed by nmbd itself IMHO.)
			rm -f $NMBDPID
		fi

		if [ "$RUN_MODE" != "inetd" ]; then
			log_progress_msg "smbd"
			start-stop-daemon --stop --quiet --pidfile $SMBDPID
			# Wait a little and remove stale PID file
			sleep 1
			if [ -f $SMBDPID ] && ! ps h `cat $SMBDPID` > /dev/null
			then
				# Stale PID file (nmbd was succesfully stopped),
				# remove it (should be removed by smbd itself IMHO.)
				rm -f $SMBDPID
			fi
		fi

		log_end_msg 0

		;;
	reload)
		log_daemon_msg "Reloading /etc/samba/smb.conf" "smbd only"

		start-stop-daemon --stop --signal HUP --pidfile $SMBDPID

		log_end_msg 0
		;;
	restart|force-reload)
		$0 stop
		sleep 1
		$0 start
		;;
        status)
		status="0"
		NMBD_DISABLED=`testparm -s --parameter-name='disable netbios' 2>/dev/null`
		if [ "$NMBD_DISABLED" != "Yes" ]; then
			status_of_proc -p $NMBDPID /usr/sbin/nmbd nmbd || status=$?
		fi
		if [ "$RUN_MODE" != "inetd" ]; then
			status_of_proc -p $SMBDPID /usr/sbin/smbd smbd || status=$?
		fi
		if [ "$NMBD_DISABLED" = "Yes" -a "$RUN_MODE" = "inetd" ]; then
			status="4"
		fi
		exit $status
		;;
	*)
		echo "Usage: /etc/init.d/samba {start|stop|reload|restart|force-reload|status}"
		exit 1
		;;
esac

exit 0
For now, I won't add any more to this lengthy reply, but please let me know if it will help you to compare anything else.
 
  


Reply

Tags
karmic koala, openvpn, samba, server, upgrade


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Upgrade to karmic has killed all sound blastradius Ubuntu 2 12-06-2009 04:01 AM
How to starting OpenVPN at boot time? Vitalka Linux - General 2 11-08-2007 10:54 AM
sshd not starting up on boot after upgrade babis Linux - Software 1 03-18-2004 08:04 PM
RH9 Upgrade=KDE starting problems SenorPedo Linux - Software 12 08-26-2003 01:15 PM
Starting Samba at boot time. Unknown_User Linux - Software 3 04-26-2003 04:30 AM


All times are GMT -5. The time now is 11:30 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration