topic Re: SAMBA + ServiceGuard + RHEL 4 in Operating System - Linux

SAMBA + ServiceGuard + RHEL 4

Vladimir_78 — Wed, 11 Jan 2006 11:16:42 GMT

I'm trying to configure SAMBA package on ServiceGuard cluster. It doesn't start.
In nmbd.log:
Failed to open nmb socket on interface 10.13.7.94 for port 137. Error was Cannot assign requested address

Re: SAMBA + ServiceGuard + RHEL 4

melvyn burnard — Wed, 11 Jan 2006 12:26:06 GMT

First question, can SAMBA be started outside of Serviceguard? If not, then fix that first.
Second question, are you using the SAMBA toolkit from http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T2341BA

or even better:
http://h20293.www2.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=SGLXTOOLS

Re: SAMBA + ServiceGuard + RHEL 4

Ivan Ferreira — Wed, 11 Jan 2006 13:06:26 GMT

This is always my first question when using RHEL4, did you disable SELinux?

Re: SAMBA + ServiceGuard + RHEL 4

Steven E. Protter — Wed, 11 Jan 2006 13:39:33 GMT

Shalom Vladimir,

netstat -an | grep ":37 "

I bet you'll see Samba already running on the port.

To make Samba open in SG, which is quite possible, you must make sure its not already running. The package script needs to start it.

SEP

Re: SAMBA + ServiceGuard + RHEL 4

Vladimir_78 — Thu, 12 Jan 2006 03:56:45 GMT

1. SAMBA works outside SG.
2. samba-toolkit-A.02.00-0.product.redhat.i386.rpm
3. SElinux was in warning mode, now it's disabled.
4. SAMBA isn't running on the port.

I've installed Apache package.
It doesn't work too.

Jan 12 00:41:49 - Node "hp1": Starting Apache daemons.
(98)Address already in use: make_sock: could not bind to address [::]:80
no listening sockets available, shutting down
Unable to open logs
ERROR: Function start_server: Failed to start Apache daemons.
ERROR: Jan 12 00:41:49 - Failed to start HTTP.
ERROR: Function customer_defined_run_cmds; Failed to RUN customer commands

Re: SAMBA + ServiceGuard + RHEL 4

melvyn burnard — Thu, 12 Jan 2006 04:45:49 GMT

Well the error says it all:
Jan 12 00:41:49 - Node "hp1": Starting Apache daemons.
(98)Address already in use: make_sock: could not bind to address [::]:80

There is already something listening on the socket you are trying to use.

Re: SAMBA + ServiceGuard + RHEL 4

Stuart Browne — Thu, 12 Jan 2006 06:31:05 GMT

'netstat -ntulp', and see what's there.

Re: SAMBA + ServiceGuard + RHEL 4

Vladimir_78 — Thu, 12 Jan 2006 10:59:36 GMT

Nothing like this.

Re: SAMBA + ServiceGuard + RHEL 4

Steven E. Protter — Thu, 12 Jan 2006 11:59:36 GMT

Shalom again Vladimir,

Clarly ther eis nothing running on netstat. What does the port 137 entry look like in /etc/services

The web server is more curious. Daemons starting up wanting to bind to ports under 1024 require root access.

I assume root is trying the start but I'd like to check this.

SEP

Re: SAMBA + ServiceGuard + RHEL 4

Stuart Browne — Thu, 12 Jan 2006 18:34:18 GMT

I guess somethign to consider is the SELinux state.

I recently installed some 3rd party stuff on a FC4 box (SELinux enabled) and ran into odd issues. SELinux was enforcing, and I didn't have any new targeted policies to put in.

As it's the ServiceGuard which will probably be trying to do something with the port, does it have Targeted Policies to allow the access? (Sorry, I don't have any SG here to check).