Question

Samba restart/stopping problem /etc/init.d/samba

Asked by: phlipmode

Hey folks,

i have a small problem, not really very important, but i would like to understand, why i can not stop the samba service?!

Here my problem in detail.

i installed samba, configured it yesterday, works fine so far.
today i wanted to connect to a share of my samba service and it wasnt possible...

so i decided to restart the samba service over /etc/init.d/samba restart

the message
Stopping Samba daemons: nmbd
appears, and nothing more happen after this.

i also tried to kill all processes of samba manually, this works for sure. i can start it again over init.d but i can not stop it again. its always hanging to shutdown the nmbd daemon i guess.

anyone a clue why this happens?

thanks for any help

by the way, i didnt find any intersting entries in the log-files  

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2009-08-06 at 01:57:08ID24630697
Tags

samba

,

init.d

,

restart

,

stop

Topics

Samba File Server

,

Debian Linux

,

Linux Networking

Participating Experts
2
Points
200
Comments
8

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. samba
    i'm using redhat 7.0 i want to use samba GUI which is already provided by redhat. i just click samba configuration tools but the browser display nothing. the browser http://localhost:901/ how can i see what is in the http://localhost:901
  2. Samba Error - Running on Debian Linux 3.0
    Hi I have recently installed and configured Samba 3.00 on my Debian server, which does work fine. When i restart samba i get the following: root@xbox:~# /etc/init.d/samba restart Stopping Samba daemons: nmbd smbd. Starting Samba daemons: nmbd smbd/usr/sbin/smbd: /usr/lib/li...
  3. samba log rotate
    I upraded samba to 2.0.10-0.62 and then I got an error about a couple logs not being present, so I touched them and now I'm getting the following message in the cron daemon notification. /etc/cron.daily/logrotate: nmbd: no process killed error running postrotate script smbd...
  4. init.d question
    I've noticed some people say to edit inetd.conf to start/stop services. Some say to do a cd /etc/init.d and edit the services manually (ie: vi sshd) Which is it? Thanks

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: phlipmodePosted on 2009-08-06 at 05:08:13ID: 25032273

ok, now its getting even more weired.

i can not stop any other service.
there is always the message showing up, that the service is getting stopped, but it never ends, and no service is stopped...

anyone an idea, why this happens?

thx

 

by: it4sohoPosted on 2009-08-06 at 09:25:31ID: 25035264

The behavior you describe can be caused by either:
 1) The user running the service script is not the root user (UID=0)
 2) The process is blocking on an I/O operation, and cannot stop until it completes

Assuming you ARE running as a root user (either logged in as root [bad admin], or using su or sudo to gain root privs [good admin]), then the issue appears to be one tied to an I/O operation (there are a few other possibilities, but they are RARE when compared to I/O blocks).

Check your system syslog message file (/var/log/messages) and see if you are perhaps having disk problems.

you might also post here the following:
 a) the contents of /etc/init.d/smb (it is USUALLY named smb, not samba)
 b) the output of the command "ps -aefww | grep bd" performed BEFORE you try to stop Samba
 c) the output of the command "bash -x /etc/init.d/smb stop" (this will stop samba, and the output will be long!)
 d) the output of the command "ps -aefww | grep bd" performed AFTER you try to stop Samba
 e) the output of the command "bash -x /etc/init.d/smb start" (this will start samba, and the output will be long!)
 d) the output of the command "ps -aefww | grep bd" performed AFTER you try to start Samba

Of course, if your samba init.d file really IS named sambe, run /etc/init.d/samba above, instead of smb.

I look forward to your reply!

Dan
IT4SOHO

 

by: phlipmodePosted on 2009-08-06 at 14:03:43ID: 25038036

Hi IT4SOHO,

first thanks for your detailed answer.

i will try all these steps tomorrow morning at work :)

today i was wondering why my firewall also didnt do what it should do.
so i tried to figured out what produces this errors.
first we did a memory check, but this went fine, later i also thought, it just can be a hardware problem, i never had such strange problems in a row.

tomorrow i will check the harddisk, i guess this could be the problem.
i will inform you! :)

thanks for help

 

by: phlipmodePosted on 2009-08-07 at 01:33:56ID: 25040767

So,

the syslog only shows some entries about my clock, that the time went backwards...
i think the error is not because of the clock, or?

On the current Debian-Distro the service-script is called samba.

i dont know if its usefull, but its the normal debian samba-service script down there.
I haven't changed anything.

after this, the executed the commands you showed in a row.

if you like, take a look.

is there a way to easy check the harddisk for errors?




server:/var/log# cat /etc/init.d/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
                ;;
        *)
                echo "Usage: /etc/init.d/samba {start|stop|reload|restart|force-reload}"
                exit 1
                ;;
esac
 
exit 0
 
 
 
 
-------------------------
 
server:/var/log# /etc/init.d/samba start
Starting Samba daemons: nmbd smbd.
server:/var/log# ps -aefww | grep bd
104      15499     1  0 05:59 ?        00:00:00 /usr/sbin/exim4 -bd -q30m
root     18016     1  0 09:29 ?        00:00:00 /usr/sbin/smbd -D
root     18017 18016  0 09:29 ?        00:00:00 /usr/sbin/smbd -D
root     18565     1  0 09:29 ?        00:00:00 /usr/sbin/nmbd -D
root     18573 18545  0 09:29 pts/0    00:00:00 grep bd
 
 
 
-----------------------------
 
 
server:/var/log# bash -x /etc/init.d/samba stop
+ RUN_MODE=daemons
+ '[' -r /etc/default/samba ']'
+ . /etc/default/samba
++ RUN_MODE=daemons
+ PIDDIR=/var/run/samba
+ NMBDPID=/var/run/samba/nmbd.pid
+ SMBDPID=/var/run/samba/smbd.pid
+ unset TMPDIR
+ test -x /usr/sbin/nmbd -a -x /usr/sbin/smbd
+ . /lib/lsb/init-functions
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ case "$1" in
+ log_daemon_msg 'Stopping Samba daemons'
+ '[' -z 'Stopping Samba daemons' ']'
+ log_daemon_msg_pre 'Stopping Samba daemons'
+ :
+ '[' -z '' ']'
+ echo -n 'Stopping Samba daemons:'
Stopping Samba daemons:+ return
+ log_progress_msg nmbd
+ '[' -z nmbd ']'
+ echo -n ' nmbd'
 nmbd+ start-stop-daemon --stop --quiet --pidfile /var/run/samba/nmbd.pid
+ sleep 1
 
THIS NEVER ENDS!
 
-----------------------
 
server:/var/log# ps -aefww | grep bd
104      15499     1  0 05:59 ?        00:00:00 /usr/sbin/exim4 -bd -q30m
root     18016     1  0 09:29 ?        00:00:00 /usr/sbin/smbd -D
root     18017 18016  0 09:29 ?        00:00:00 /usr/sbin/smbd -D
root     18578 18545  0 09:29 pts/0    00:00:00 grep bd
 
-------------------
 
 
server:/var/log# bash -x /etc/init.d/samba start
+ RUN_MODE=daemons
+ '[' -r /etc/default/samba ']'
+ . /etc/default/samba
++ RUN_MODE=daemons
+ PIDDIR=/var/run/samba
+ NMBDPID=/var/run/samba/nmbd.pid
+ SMBDPID=/var/run/samba/smbd.pid
+ unset TMPDIR
+ test -x /usr/sbin/nmbd -a -x /usr/sbin/smbd
+ . /lib/lsb/init-functions
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ case "$1" in
+ log_daemon_msg 'Starting Samba daemons'
+ '[' -z 'Starting Samba daemons' ']'
+ log_daemon_msg_pre 'Starting Samba daemons'
+ :
+ '[' -z '' ']'
+ echo -n 'Starting Samba daemons:'
Starting Samba daemons:+ return
+ install -o root -g root -m 755 -d /var/run/samba
++ testparm -s '--parameter-name=disable netbios'
+ NMBD_DISABLED=No
+ '[' No '!=' Yes ']'
+ log_progress_msg nmbd
+ '[' -z nmbd ']'
+ echo -n ' nmbd'
 nmbd+ start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/nmbd -- -D
+ '[' daemons '!=' inetd ']'
+ log_progress_msg smbd
+ '[' -z smbd ']'
+ echo -n ' smbd'
 smbd+ start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/smbd -- -D
+ log_end_msg 0
+ '[' -z 0 ']'
+ retval=0
+ log_end_msg_pre 0
+ :
+ log_use_fancy_output
+ TPUT=/usr/bin/tput
+ EXPR=/usr/bin/expr
+ '[' -t 1 ']'
+ '[' xxterm '!=' '' ']'
+ '[' xxterm '!=' xdumb ']'
+ '[' -x /usr/bin/tput ']'
+ '[' -x /usr/bin/expr ']'
+ /usr/bin/tput hpa 60
+ /usr/bin/tput setaf 1
+ '[' -z ']'
+ FANCYTTY=1
+ case "$FANCYTTY" in
+ true
++ /usr/bin/tput setaf 1
+ RED=''
++ /usr/bin/tput setaf 3
+ YELLOW=''
++ /usr/bin/tput op
+ NORMAL=''
+ '[' 0 -eq 0 ']'
+ echo .
.
+ log_end_msg_post 0
+ :
+ return 0
+ exit 0
 
 
----------------
 
 
server:/var/log# ps -aefww | grep bd
104      15499     1  0 05:59 ?        00:00:00 /usr/sbin/exim4 -bd -q30m
root     18016     1  0 09:29 ?        00:00:00 /usr/sbin/smbd -D
root     18017 18016  0 09:29 ?        00:00:00 /usr/sbin/smbd -D
root     18584     1  0 09:29 ?        00:00:00 /usr/sbin/nmbd -D
root     18592 18545  0 09:29 pts/0    00:00:00 grep bd
                                              
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:
148:
149:
150:
151:
152:
153:
154:
155:
156:
157:
158:
159:
160:
161:
162:
163:
164:
165:
166:
167:
168:
169:
170:
171:
172:
173:
174:
175:
176:
177:
178:
179:
180:
181:
182:
183:
184:
185:
186:
187:
188:
189:
190:
191:
192:
193:
194:
195:
196:
197:
198:
199:
200:
201:
202:
203:
204:
205:
206:
207:
208:
209:
210:
211:
212:
213:
214:
215:
216:
217:
218:
219:
220:
221:
222:
223:
224:
225:
226:
227:
228:
229:
230:
231:
232:
233:
234:
235:
236:
237:
238:
239:
240:
241:
242:
243:
244:
245:
246:
247:

Select allOpen in new window

 

by: MadShivaPosted on 2009-08-07 at 01:41:33ID: 25040805

Dear phlipmode,

For found the error you could do : dmesg in a console. This will show if the hard drive has failure, but also the other error that you maybe have.

The best way to check the hard drive is to use S.M.A.R.T.

There is a tool on Debian called smartmontools.

Best Regards

 

by: it4sohoPosted on 2009-08-07 at 07:21:33ID: 25042946

OK... so based upon your entry that the 'sleep loop' never ends, we can see why the SMBD daemon never stops.

In my somewhat limited Debian experience, you typically want to include the --exec portion to start-stop-daemon for ALL actions, primarily to make sure that there hasn't been some change to the PID or some other process running with a similar name or ID.

In addition, it appears your start option doesn't write the NMBDPID (because start-stop-daemon isn't told to).

So, with that in mind, please update your /etc/init.d/samba file as shown below:

Good Luck!

Dan
IT4SOHO

PS: If this doesn't work, please provide a fresh output of "bash -x /etc/init.d/samba stop"

cat /etc/init.d/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 --pidfile $NMBDPID --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 --pidfile $SMBDPID --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 --exec /usr/sbin/nmbd -- -D
    # 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 --exec /usr/sbin/smbd -- -D
      # 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 --exec /usr/sbin/smbd -- -D
 
    log_end_msg 0
    ;;
 
  restart|force-reload)
    $0 stop
    sleep 2
    $0 start
    ;;
 
  *)
    echo "Usage: /etc/init.d/samba {start|stop|reload|restart|force-reload}"
    exit 1
    ;;
esac
 
exit 0

                                              
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:

Select allOpen in new window

 

by: phlipmodePosted on 2009-08-18 at 04:44:36ID: 25122056

Hello,

sorry for my late response, but last week i took a vacation so the problem wasn't mine anymore :P

So over the last week, we get a new server, because there was a strong suspicion, that the hardware (mainboard - ide) controller was broken.

So we get the new one and everything is working like a charm:)

Thanks, for any help here! And espiacally you, It4soho!

This one is closed!

 

by: phlipmodePosted on 2009-08-18 at 04:46:59ID: 31612312

nice tips to get closer to the error itself, but it wasnt the samba server or init.d scipt, just a broken mainboard! :(

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...