In Solaris 9 TCP wrappers are enabled by default.  If  
/etc/default/inetd contains the following line: 
ENABLE_TCPWRAPPERS=YES

Entries have to be added to /etc/hosts.allow as follows:
bpcd:           <master server IP>
vnetd:  <master server IP>

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of
Wilkinson, Alex
Sent: Tuesday, June 06, 2006 1:59 AM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] [vmd] terminating - daemon cannot obtain socket
(58)


Howdy all,

OS: Solaris 9. SAN Media Server.

When I exec() the /etc/init.d/netbackup script I am seeing the following
errors via syslog.

Jun  6 12:50:31 hostname.dsto.defence.gov.au vmd[28983]: [ID 625030
daemon.error] unable to obtain bound socket, no port number available
for vmd (0)
Jun  6 12:50:31 hostname.dsto.defence.gov.au vmd[28983]: [ID 423164
daemon.error] terminating - daemon cannot obtain socket (58)
Jun  6 12:50:31 hostname.dsto.defence.gov.au vmd[28983]: [ID 715111
daemon.error] volume daemon terminating because it received a signal
(15)
Jun  6 12:50:31 hostname.dsto.defence.gov.au vmd[28983]: [ID 164182
daemon.error] terminating - daemon terminated (7)

I cannot connect to port 13782 :(

There is a technote on seer.veritas about this error and it basically
says that
there this error will occur if the necessary services are not listed in
/etc/services. I
have checked and all required services are listed in /etc/services.

Essentially the problem is, is that vmd will not exec(), because it
cannot bind
to its socket/port (13701). I have even truss(1)'d the execuction of
vmd.

And no there are no other processes bound to port 13701.

Can anyone recommend why vmd would be unable to bind to its port ?

Cheers

 -aW
_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu