Did you try running vmd with the -v options and also increasing log
verbosity for the volume manager to get more information?

On 6/6/06, Wilkinson, Alex <alex.wilkinson at dsto.defence.gov.au> wrote:
>
> 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
>