Java GUI fails to connect with status 505, a telnet to port 13722 fails with "Request daemon can't accept sessions."

Article:TECH33805  |  Created: 2004-01-12  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH33805
Article Type
Technical Solution


Environment

Issue



Java GUI fails to connect with status 505, a telnet to port 13722 fails with "Request daemon can't accept sessions."

Error



Request daemon can't accept sessions

Solution



The error message "Request daemon can't accept sessions" occurs when another instance of bpjava-msvc tries to run when bpjava-msvc is already registered with inetd. This can be caused when a manual attempt is made to start bpjava-msvc or if the /etc/inetd.conf has a typo in the entry for bpjava-msvc.

The Java GUI will fail with the following error:

 Unable to login, status: 505
 Can not connect to the NB-Java authentication service on
 master on the configured port - 13722

 Exception: java.lang.NumberFormatException: another
 Exception message: another

If this error occurs, then try to telnet to port 13722 on the system. If it fails with the following error, then there is most likely a typo in the /etc/inetd.conf file.  

 # telnet master 13722
 Trying...
 Connected to master.
 Escape character is '^]'.
   request daemon can't accept sessions
   another instance may already be running.
   Address already in use
 Connection closed by foreign host.

Then check the /etc/inetd.conf file for errors. A typo with the -transient option can trigger this error.

An incorrect entry that would trigger this error would be:
bpjava-msvc     stream  tcp     nowait  root    /usr/openv/netbackup/bin/bpjava-msvc bpjava-msvc -transient

To correct this problem do the following:

1. Edit the /etc/inetd.conf file and make sure the bpjava-msvc line is setup as follows:
bpjava-msvc     stream  tcp     nowait  root    /usr/openv/netbackup/bin/bpjava-msvc bpjava-msvc -transient

Note: This should all be on one line. The -transient should be one word with no spaces.

2. Save the file

3. Then send a SIGHUP to inetd
# ps -ef |grep inetd

  This will show the <PID> for inetd. Use this in the next command:
# kill -HUP <PID>

  This will cause inetd to re-read its configuration file.

4. Then try to log in via the GUI



Legacy ID



270238


Article URL http://www.symantec.com/docs/TECH33805


Terms of use for this information are found in Legal Notices