Sun Fire E25K Server
 
Sun Fire 12K Server
 
Sun Fire 15K Server
 
Sun Fire E20K Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-Exxk
 
_Old GCS Categories>Sun Microsystems>Servers>High-End Servers
 

Applies to:

Symptoms

The smsconnectsc command fails with "all ports busy" or just hangs.

From the System Management Services Reference Manual:

"The smsconnectsc command creates a remote tip console session from a local SC, in order to reach a hung remote SC console."

This document discusses what happens when the smsconnectsc command fails with "all ports busy" or just hangs.

Running the smsconnectsc command might succeed, but hang:


sc0:sms-svc> smsconnectsc
Attempting to determine remote SC power state. This may take some time.
Attempting to get TTY connection state. This may take some time.
TTY connection is OFF.
About to connect to other SC. Do you want to continue (yes/no)? y
Attempting to set TTY connection state. This may take some time.
connected
<No response to input>
~.
[EOT]
sc0:sms-svc>

Running the smsconnectsc command might fail, displaying the following errors:


sc0:sms-svc>smsconnectsc
Attempting to determine remote SC power state. This may take some time.
Attempting to get TTY connection state. This may take some time.
TTY connection is OFF.
About to connect to other SC. Do you want to continue (yes/no)? yes
Attempting to set TTY connection state. This may take some time.
tip: can't create files in lock file directory /var/spool/locks ****
all ports busy
Attempting to set TTY connection state. This may take some time.
sc0:sms-svc>

Running the smsconnectsc command might fail, displaying the following errors:


sc0:sms-svc> smsconnectsc
Attempting to determine remote SC power state. This may take some time.
Attempting to get TTY connection state. This may take some time.
TTY connection is OFF.
About to connect to other SC. Do you want to continue (yes/no)? yes
Attempting to set TTY connection state. This may take some time.
all ports busy
Attempting to set TTY connection state. This may take some time.
sc0:sms-svc>

Changes

Cause

The smsconnectsc command is built on top of the tip command (/bin/tip). Tip writes a lock file in /var/spool/locks(see the manual page of tip for details).
The smsconnectsc command uses tip to talk to system 'hardwire', as defined in the /etc/remote file.

Solution

smsconnectsc hangs:

   The smsconnectsc command only works in the absence of an external connection
to the remote SC. If the remote SC does have an external serial connection,
smsconnectsc will connect but will not respond to any input. Check the
smsconnectsc manual page for more details. In this case you must use the
available serial connection of the remote SC to get to it.

smsconnectsc reports 'can't create files in lock file directory /var/spool/locks' and exits:

   Tip first complains about not being able to write the lock file, then
complains about all ports being busy and exits; this is caused by invalid
ownership settings of /bin/tip; To allow tip to write its lock files into
/var/spool/locks, the tip command must be owned by user uucp and have its
setuid bit set:
# ls -la /bin/tip
-r-s--x--x   1 uucp     bin        54740 Apr  7  2002 /bin/tip
Check these settings, and correct them if necessary.

smsconnectsc reports 'all ports busy' and exits:

Tip complains about all ports being busy and exits; this is caused by
another process already talking to system 'hardwire'; follow procedures
as described in Doc ID: 1011540.1  'How to resolve "All ports busy" or free up
hung serial ports Solaris[TM] 2.x Operating Environments', to free up the
system 'hardwire' for use by smsconnectsc.

Additional Information
manual pages:

- smsconnectsc
- remote
- tip

Doc ID:  1011540.1  'How to resolve "All ports busy" or free up hung serial ports Solaris[TM] 2.x Operating Environments'

smsconnectsc, all ports busy, hang
Previously Published As 80441

This solution has no attachment