[CentOS] Odd failure of smbd to start from init.d - CentOS 5.4

Fri May 21 18:47:03 UTC 2010
Whit Blauvelt <whit at transpect.com>

On Fri, May 21, 2010 at 07:49:16AM -0400, Kwan Lowe wrote:

> My gut tells me it's not hardware but willing to take it :)
> 
> Have you tried adding a "set -x" to the top of the the smb startup
> scripts?  I didn't see any such output in your replies so far.

Here you go:

# ./smb start
+ '[' -f /etc/init.d/functions ']'
+ . /etc/init.d/functions
++ TEXTDOMAIN=initscripts
++ umask 022
++ PATH=/sbin:/usr/sbin:/bin:/usr/bin
++ export PATH
++ '[' -z '' ']'
++ COLUMNS=80
++ '[' -z '' ']'
+++ /sbin/consoletype
++ CONSOLETYPE=pty
++ '[' -f /etc/sysconfig/i18n -a -z '' ']'
++ . /etc/profile.d/lang.sh
+++ sourced=0
+++ for langfile in /etc/sysconfig/i18n '$HOME/.i18n'
+++ '[' -f /etc/sysconfig/i18n ']'
+++ . /etc/sysconfig/i18n
++++ LANG=en_US.UTF-8
++++ SYSFONT=latarcyrheb-sun16
+++ sourced=1
+++ for langfile in /etc/sysconfig/i18n '$HOME/.i18n'
+++ '[' -f /root/.i18n ']'
+++ '[' -n '' ']'
+++ '[' 1 = 1 ']'
+++ '[' -n en_US.UTF-8 ']'
+++ export LANG
+++ '[' -n '' ']'
+++ unset LC_ADDRESS
+++ '[' -n '' ']'
+++ unset LC_CTYPE
+++ '[' -n '' ']'
+++ unset LC_COLLATE
+++ '[' -n '' ']'
+++ unset LC_IDENTIFICATION
+++ '[' -n '' ']'
+++ unset LC_MEASUREMENT
+++ '[' -n '' ']'
+++ unset LC_MESSAGES
+++ '[' -n '' ']'
+++ unset LC_MONETARY
+++ '[' -n '' ']'
+++ unset LC_NAME
+++ '[' -n '' ']'
+++ unset LC_NUMERIC
+++ '[' -n '' ']'
+++ unset LC_PAPER
+++ '[' -n '' ']'
+++ unset LC_TELEPHONE
+++ '[' -n '' ']'
+++ unset LC_TIME
+++ '[' -n '' ']'
+++ unset LC_ALL
+++ '[' -n '' ']'
+++ unset LANGUAGE
+++ '[' -n '' ']'
+++ unset LINGUAS
+++ '[' -n '' ']'
+++ unset _XKB_CHARSET
+++ consoletype=pty
+++ '[' -z pty ']'
+++ '[' -n '' ']'
+++ '[' -n '' ']'
+++ '[' -n en_US.UTF-8 ']'
+++ case $LANG in
+++ '[' rxvt = linux ']'
+++ unset SYSFONTACM SYSFONT
+++ unset sourced
+++ unset langfile
++ '[' -z '' ']'
++ '[' -f /etc/sysconfig/init ']'
++ . /etc/sysconfig/init
+++ BOOTUP=color
+++ GRAPHICAL=yes
+++ RES_COL=60
+++ MOVE_TO_COL='echo -en \033[60G'
+++ SETCOLOR_SUCCESS='echo -en \033[0;32m'
+++ SETCOLOR_FAILURE='echo -en \033[0;31m'
+++ SETCOLOR_WARNING='echo -en \033[0;33m'
+++ SETCOLOR_NORMAL='echo -en \033[0;39m'
+++ LOGLEVEL=3
+++ PROMPT=yes
+++ AUTOSWAP=no
++ '[' pty = serial ']'
++ '[' color '!=' verbose ']'
++ INITLOG_ARGS=-q
++ __sed_discard_ignored_files='/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d'
+ unset TMPDIR
+ . /etc/sysconfig/network
++ NETWORKING=yes
++ NETWORKING_IPV6=no
++ HOSTNAME=skywalker.eis.local
+ '[' -f /etc/sysconfig/samba ']'
+ . /etc/sysconfig/samba
++ SMBDOPTIONS=-D
++ NMBDOPTIONS=-D
++ WINBINDOPTIONS=
+ '[' yes = no ']'
+ '[' -f /etc/samba/smb.conf ']'
+ RETVAL=0
+ '[' start = status ']'
+ '[' -w /etc/samba/smb.conf ']'
+ case "$1" in
+ start
+ KIND=SMB
+ echo -n 'Starting SMB services: '
Starting SMB services: + daemon smbd -D
+ local gotbase= force= nicelevel corelimit
+ local pid base= user= nice= bg= pid_file=
+ nicelevel=0
+ '[' smbd '!=' smbd ']'
+ '[' -z '' ']'
+ base=smbd
+ __pids_var_run smbd ''
+ local base=smbd
+ local pid_file=/var/run/smbd.pid
+ pid=
+ '[' -f /var/run/smbd.pid ']'
+ return 3
+ '[' -n '' -a -z '' ']'
+ corelimit='ulimit -S -c 0'
+ '[' -n '' ']'
+ '[' color = verbose -a -z '' ']'
+ '[' -z '' ']'
+ /bin/bash -c 'ulimit -S -c 0 >/dev/null 2>&1 ; smbd -D'
+ '[' 0 -eq 0 ']'
+ success 'smbd startup'
+ '[' color '!=' verbose -a -z '' ']'
+ echo_success
+ '[' color = color ']'
+ echo -en '\033[60G'
                                                           + echo -n '['
[+ '[' color = color ']'
+ echo -en '\033[0;32m'
+ echo -n '  OK  '
  OK  + '[' color = color ']'
+ echo -en '\033[0;39m'
+ echo -n ']'
]+ echo -ne '\r'
+ return 0
+ return 0
+ RETVAL=0
+ echo

+ KIND=NMB
+ echo -n 'Starting NMB services: '
Starting NMB services: + daemon nmbd -D
+ local gotbase= force= nicelevel corelimit
+ local pid base= user= nice= bg= pid_file=
+ nicelevel=0
+ '[' nmbd '!=' nmbd ']'
+ '[' -z '' ']'
+ base=nmbd
+ __pids_var_run nmbd ''
+ local base=nmbd
+ local pid_file=/var/run/nmbd.pid
+ pid=
+ '[' -f /var/run/nmbd.pid ']'
+ return 3
+ '[' -n '' -a -z '' ']'
+ corelimit='ulimit -S -c 0'
+ '[' -n '' ']'
+ '[' color = verbose -a -z '' ']'
+ '[' -z '' ']'
+ /bin/bash -c 'ulimit -S -c 0 >/dev/null 2>&1 ; nmbd -D'
+ '[' 0 -eq 0 ']'
+ success 'nmbd startup'
+ '[' color '!=' verbose -a -z '' ']'
+ echo_success
+ '[' color = color ']'
+ echo -en '\033[60G'
                                                           + echo -n '['
[+ '[' color = color ']'
+ echo -en '\033[0;32m'
+ echo -n '  OK  '
  OK  + '[' color = color ']'
+ echo -en '\033[0;39m'
+ echo -n ']'
]+ echo -ne '\r'
+ return 0
+ return 0
+ RETVAL2=0
+ echo

+ '[' 0 -eq 0 -a 0 -eq 0 ']'
+ touch /var/lock/subsys/smb
+ return 0
+ exit 0

So that's two Ok's and RETVAL's of 0, but immediately afterwards:

# ps aux | grep mbd | grep -v grep
root      5504  0.0  0.0 107732  1544 ?        Ss   14:40   0:00 nmbd -D

So once again smbd has gone immediately away.

But 
# smbd -D
# ps aux | grep mbd | grep -v grep
root      5504  0.0  0.0 107732  1544 ?        Ss   14:40   0:00 nmbd -D
root      5664  0.0  0.0 135580  2596 ?        Ss   14:43   0:00 smbd -D
root      5665  0.0  0.0 135580  1408 ?        S    14:43   0:00 smbd -D
rec_user  5666  0.0  0.0 135888  2712 ?        S    14:43   0:00 smbd -D

... it's quite possible to run it directly.

So it remains strange and hard to explain.

Whit