bptestbpcd fails on self

[KEELIN_HART_2]

This is a new Solaris 10 NBU6.5 media server.

'bptestbpcd -verbose' returns:

13:52:15.997 [16825] <2> bptestbpcd: VERBOSE = 0
13:52:16.007 [16825] <2> vnet_async_connect: vnet_vnetd.c.3955: connect failed: 146 0x00000092
13:52:16.008 [16825] <2> logconnections: BPCD CONNECT FROM 10.37.228.221.740 TO 10.37.228.221.13782
13:52:47.197 [16825] <2> vnet_pop_byte: vnet.c.184: errno: 2 0x00000002
13:52:47.197 [16825] <2> vnet_pop_byte: vnet.c.186: Function failed: 9 0x00000009
13:52:47.197 [16825] <2> vnet_pop_string: vnet.c.266: Function failed: 9 0x00000009
13:52:47.197 [16825] <2> vnet_pop_signed: vnet.c.310: Function failed: 9 0x00000009
13:52:47.198 [16825] <2> vnet_pop_status: vnet.c.388: Function failed: 9 0x00000009
13:52:47.198 [16825] <2> vnet_begin_connect_back: vnet_vnetd.c.720: status: 9 0x00000009
13:52:47.198 [16825] <2> ConnectToBPCD: bpcd_connect_and_verify(nbumed5-mpc-01-bu, nbumed5-mpc-01-bu) failed: 0
<16>bptestbpcd main: Function ConnectToBPCD(nbumed5-mpc-01-bu) failed: 25
13:52:47.199 [16825] <16> bptestbpcd main: Function ConnectToBPCD(nbumed5-mpc-01-bu) failed: 25
<2>bptestbpcd: cannot connect on socket
13:52:47.199 [16825] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
13:52:47.199 [16825] <2> bptestbpcd: EXIT status = 25
cannot connect on socket

But I am able to run bptestbpcd commands from other servers in the domain to this media server, and similarly, out from this server to other servers in the domain. The bpclntcmd functions return as expected and telnet to the bpcd port succeeds. This server is NOT behind a firewall.

Any suggestions would be very much appreciated!

Thanks ;o)

[CRZ]

From the media server, does `telnet 10.37.228.221 13782` give the expected results?

(The hostname does resolve to 10.37.228.221 on your other machines where the connection works, I am assuming?)

EDIT: How do you spell "telnet" again?  ;)

Message Edited by CRZ on 02-25-2009 11:56 AM

[KEELIN_HART_2]

Thanks for your response Chris.

Yes, telnet using the IP address also works...

[KEELIN_HART_2]

In the interest of information sharing -

The vnetd port was not listening. Executing '/usr/openv/bin/vnetd -standalone &' has resolved the issue.

[CRZ]

Good stuff!

If you don't want to constantly restart vnetd in standalone mode, you might want to do some troubleshooting on that host and see if your inetd/SMF setup includes vnetd and is correctly configured for it.

This TechNote was written for Java issues, but the vnetd information is good for any Solaris 10 system:

STATUS CODE: 525, occurs when trying to log into a Solaris 10 NetBackup server using a NetBackup Java Administration console

 http://support.veritas.com/docs/282709

[KEELIN_HART_2]

Thanks for that Chris. Very useful technote. It looks like the service isn't even recognised:

/root> inetadm  -l /network/vnetd/tcp:default
Pattern '/network/vnetd/tcp:default' doesn't match any instances

/root> svcadm enable svc:/network/vnetd/tcp:default
svcadm: Pattern 'svc:/network/vnetd/tcp:default' doesn't match any instances

any ideas?

Many thanks

[Andy_Welburn · Accepted solution]

Did you run the inetconv command (translates the inetd.conf entries into the new Solaris 10 SMF descriptors)?

Once done, you should then be able to run the command svcs *vnetd* to give  something like:

STATE          STIME    FMRI
online         May_27   svc:/network/vnetd/tcp:default

If showing offline try svcadm enable *vnetd*

[KEELIN_HART_2]

That did the trick Andy! Thank you very much. ;o)

[Andy_Welburn]

Good job I've only just got back from my "Solaris 10 Features" course!!