[Samba] Samba on RHEL issue

Shuaib Ilyas (shilyas)

unread,

Jul 13, 2009, 4:00:11 PM7/13/09

to

Hi,

I am trying to install samba on the RHEL. The installation completes but
after that I get the smbd dead message upon checking the status:

[root@usps-dc1-pc12 share]#

[root@usps-dc1-pc12 share]# service smb status

smbd dead but pid file exists

nmbd (pid 8078) is running...

[root@usps-dc1-pc12 share]#

The version of RHEL and samba are as follows:

[root@usps-dc1-pc12 samba]# cat /etc/redhat-release

Red Hat Enterprise Linux Server release 5.3 (Tikanga)

[root@usps-dc1-pc12 samba]#

[root@usps-dc1-pc12 samba]# yum install samba

Loaded plugins: rhnplugin, security

Setting up Install Process

Parsing package install arguments

Package samba-3.0.33-3.7.el5_3.1.i386 already installed and latest
version

Nothing to do

[root@usps-dc1-pc12 samba]#

Any pointers to fix the issue will be helpful.

Thank you.

Shuaib

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba

Jonathon Doran

unread,

Jul 13, 2009, 4:30:13 PM7/13/09

to

Quoting "Shuaib Ilyas (shilyas)" <shi...@cisco.com>:

> I am trying to install samba on the RHEL. The installation completes but
> after that I get the smbd dead message upon checking the status:

What does the samba logfile say about this? On Fedora (which should have
the same layout as RHEL), the samba logfile is in /var/log/samba/log.smbd

Have you ran testparm to check smb.conf?

MargoAndTodd

unread,

Jul 13, 2009, 4:30:14 PM7/13/09

to

Shuaib Ilyas (shilyas) wrote:
> Hi,
>
> I am trying to install samba on the RHEL. The installation completes but
> after that I get the smbd dead message upon checking the status:
>
> [root@usps-dc1-pc12 share]#
>
> [root@usps-dc1-pc12 share]# service smb status
>
> smbd dead but pid file exists
>
> nmbd (pid 8078) is running...
>
> [root@usps-dc1-pc12 share]#

Hi Shuaib,

Seems to me I had the same problem on CentOS 5.2 a
few months back.

Try this:

1) stop the service:
/etc/rc.d/init.d/smb stop

2) erase any stray PID's:
rm /var/run/smbd.pid
rm /var/run/nmbd.pid

3) restart the service:
/etc/rc.d/init.d/smb start

If that does not work, try rebooting.

HTH,
-T

Shuaib Ilyas (shilyas)

unread,

Jul 13, 2009, 6:00:17 PM7/13/09

to

Thanks for the reply.

I followed the steps but it still did not work.

In step 2, there were no smbd.pid or nmbd.pid files found.

In step 3, even after starting the service, when checking status, smbd
id dead.

Even after the reboot, same status.

Shuaib

Shuaib Ilyas (shilyas)

unread,

Jul 13, 2009, 6:10:11 PM7/13/09

to

Hi Jonathon,
Thanks for looking into it.

The log messages are as follows:

[root@usps-dc1-pc12 samba]#
[root@usps-dc1-pc12 samba]#
[root@usps-dc1-pc12 samba]# tail smbd.log
bind failed on port 445 socket_addr = 0.0.0.0.
Error = Address already in use
[2009/07/13 14:38:00, 0] smbd/server.c:main(944)
smbd version 3.0.33-3.7.el5_3.1 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/07/13 14:38:00, 1] param/loadparm.c:service_ok(3038)
NOTE: Service printers is flagged unavailable.
[2009/07/13 14:38:00, 0] lib/util_sock.c:open_socket_in(822)
bind failed on port 445 socket_addr = 0.0.0.0.
Error = Address already in use
[root@usps-dc1-pc12 samba]#

The output of testparm to check the config smb.conf is a s follows:

root@usps-dc1-pc12 samba]# testparm /etc/samba/smb.conf
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[printers]"
NOTE: Service printers is flagged unavailable.
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
workgroup = WRKGRP
netbios name = SMBSERVER
security = SHARE
default service = global
path = /home
cups options = raw
available = No

[homes]
comment = Home Directories
path = /home/share
valid users = smbuser
admin users = smbuser
force user = root
read only = No
guest ok = Yes
browseable = No
available = Yes

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No

[root@usps-dc1-pc12 samba]#
[root@usps-dc1-pc12 samba]#

Any ideas?

-----Original Message-----
From: samba-bounces+shilyas=cisc...@lists.samba.org
[mailto:samba-bounces+shilyas=cisc...@lists.samba.org] On Behalf Of
Jonathon Doran
Sent: Monday, July 13, 2009 1:23 PM
To: sa...@lists.samba.org
Subject: Re: [Samba] Samba on RHEL issue

Linux Addict

unread,

Jul 14, 2009, 9:30:11 AM7/14/09

to

On Mon, Jul 13, 2009 at 6:00 PM, Shuaib Ilyas (shilyas)
<shi...@cisco.com>wrote:

Check if the selinux is disabled..

Shuaib Ilyas (shilyas)

unread,

Jul 14, 2009, 2:20:07 PM7/14/09

to

Hi,

Here is the setting:

[root@usps-dc1-pc12 share]# getenforce

Disabled

[root@usps-dc1-pc12 share]#

Is this correct?

Thanks,

Shuaib

From: Linux Addict [mailto:linuxa...@gmail.com]
Sent: Tuesday, July 14, 2009 6:29 AM
To: Shuaib Ilyas (shilyas)

Frank Murphy

unread,

Jul 14, 2009, 2:20:08 PM7/14/09

to

On 14/07/09 19:02, Shuaib Ilyas (shilyas) wrote:
> Hi,
>
>
>
> Here is the setting:
>
>
>
> [root@usps-dc1-pc12 share]# getenforce
>
> Disabled
>
> [root@usps-dc1-pc12 share]#
>
>
>
> Is this correct?
>
>
>
> Thanks,
>
>
>
> Shuaib
>
>

su setenforce 0

Regards,

Frank

Jonathon Doran

unread,

Jul 14, 2009, 3:10:08 PM7/14/09

to

Quoting Frank Murphy <fran...@gmail.com>:

> su setenforce 0

For the benefit of others, under Fedora I edit /etc/sysconfig/selinux
to turn this off.

Please recognize the risks you may be adding to your network by
disabling selinux. For some people, this is an acceptable situation
(me for one), but in other environments this could be a bad thing.

I think it is often advisable to try temporarily selinux and/or
iptables in an environment where things aren't working properly. This
can be done for a short period of time, so the risk of compromise is
lessened. Knowing that one of these two products is behind your
troubles is well worth the risk, in my opinion.

I have spent considerable time on a new Fedora 11 install tweaking iptables.

Frank Murphy

unread,

Jul 14, 2009, 4:10:08 PM7/14/09

to

On 14/07/09 20:01, Jonathon Doran wrote:
> Quoting Frank Murphy <fran...@gmail.com>:
>
>> su setenforce 0
>
> For the benefit of others, under Fedora I edit /etc/sysconfig/selinux to
> turn this off.
>

On Fedora it's just as easy to do setenforce 0\1 as the case may be.
No conf editing required.

Ckeck:
https://www.redhat.com/mailman/listinfo/fedora-selinux-list

fedora is also pretty good at answering CentOS\RHEL Q's

Regards,

Frank

Linux Addict

unread,

Jul 14, 2009, 5:20:09 PM7/14/09

to

Looks like selinux is disabled.

Lets try this.

Stop the smbd and winbind

/etc/init.d/smbd stop
/etc/init.d/winbind stop

Update the smb.conf with "log level = 10" and Start the smbd on Interactive
mode.

smbd -i

Observer the log it generates and attach it on a file . The last line must
be "waiting for a connection".

John Doe

unread,

Jul 15, 2009, 4:40:11 AM7/15/09

to

From: Shuaib Ilyas (shilyas) <shi...@cisco.com>

> [root@usps-dc1-pc12 samba]# tail smbd.log
> bind failed on port 445 socket_addr = 0.0.0.0.
> Error = Address already in use

If you stop all the samba daemons, is there something listening on port 445...?

JD