Error "Unable to login, status:525" when logging into Java administration console on Redhat Linux

Problem

Error "Unable to login, status: 525" when logging into Java administration console on Redhat Linux

Error Message

Unable to login, status: 525, Can not connect to the NB-Java authentication service via VNETD on <hostname> on port 13724.

Cause

If the above error is encountered when attempting to log into the NetBackup Java administration console on a Redhat Linux server, a possible cause is that xinetd, the extended Internet services daemon, is not running. xinetd is provided by the Linux operating system and acts as a listener for network applications like ftp and telnet. In the case of NetBackup it is listening for incoming connections to bpcd and vnetd.

Other possible causes include port 13724 needing to be opened, or naming resolution problems between the systems.

Solution

Run the following Linux RedHat command to verify that the xinetd package is installed:

rpm -qa | grep xinetd

If installed the output will look similar to:

xinetd-2.3.13-4.4E.1

If there is no output generated the xinetd package needs to be obtained from RedHat and installed on this client.

If the xinetd package is installed and the error is still being encountered, check that xinetd is running by executing the following command:

ps -ef | grep xinetd

If running, the output looks similar to:

root 5040 1 0 11:41 ? 00:00:00 xinetd -stayalive -pidfile /var/run/xinetd.pid

If xinetd is installed and not running, the Redhat operating system will need to be configured so that xinetd is started each time the system boots.

Once xinetd is installed and running, the following commands can be used to verify that vnetd and bpcd are listening:

netstat -a | grep bpcd
netstat -a | grep vnetd

The output from these commands should show the following outputs, respectively:

# netstat -a | grep bpcd
tcp 0 0 *:bpcd *:* LISTEN

# netstat -a | grep vnetd
tcp 0 0 *:vnetd *:* LISTEN

If bpcd and vnetd are in a listen state and backups continue to fail, additional troubleshooting needs to be performed and may require contacting NetBackup support.