Solaris 10 Samba SWAT service enters maintenance mode when a connection is attempted (Doc ID 1446729.1)

Last updated on JULY 11, 2017

Applies to:

Solaris Operating System - Version 10 5/08 U5 to 10 1/13 U11 [Release 10.0]
Information in this document applies to any platform.

Symptoms

When a attempt is made to connection to the Samba SWAT, web based Samba administration tool, the swat SMF service goes into maintenance mode.

Errors such as the following are recorded in the /var/adm/messages file:


inetd[PID]: [ID 702911 daemon.error] Failed to bind to the port of service instance svc:/network/swat/tcp:default, proto tcp: Address already in use
inetd[PID]: [ID 702911 daemon.error] Too many bind failures for instance svc:/network/swat/tcp:default, transitioning to maintenance



The output of a a svcs -av command could appear as the following:


online - Mar_07 - svc:/network/swat:default
maintenance - Mar_07 - svc:/network/swat/tcp:default



svcs -l command output will report two swat services:


fmri svc:/network/swat/tcp:default
name swat
enabled true
state maintenance
next_state none
state_time Wed Mar 07 10:57:59 2012
restarter svc:/network/inetd:default


fmri svc:/network/swat:default
name swat
enabled true
state online
next_state none
state_time Wed Mar 07 10:57:19 2012
restarter svc:/network/inetd:default



There would be entries in the /etc/inetd.conf such as one or both of the following:


swat stream tcp nowait root /usr/sfw/swat swat
swat stream tcp nowait.400 root /usr/sfw/swat swat






Changes

The instructions in the Solaris 10 swat (1M) man page to configure swat to be under inetd control were used to configure and enable the swat service.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms