Not my day.

10:11:01.420 [19750] <2> vnet_version_accept: vnetd.c.1133: 
*actual_version: 4 0x00000004
10:11:01.452 [19750] <2> ProcessRequests: vnetd.c.336: msg: Request 
VN_REQUEST_SERVICE_SOCKET(6)
10:11:01.452 [19750] <2> process_service_socket: vnetd.c.1515: 
service_name: vmd
10:11:05.492 [19750] <2> vnet_connect_by_vnetd: vnet_vnetd.c.1457: status: 
10 0x0000000a
10:11:05.492 [19750] <2> process_service_socket: vnetd.c.1568: 
vnet_connect_by_vnetd failed: 10 0x0000000a
10:11:05.492 [19750] <2> ProcessRequests: vnetd.c.338: status: 10 
0x0000000a
10:11:05.493 [19750] <2> vnet_pop_byte: vnet.c.163: errno: 111 0x0000006f
10:11:05.493 [19750] <2> vnet_pop_byte: vnet.c.164: Function failed: 42 
0x0000002a
10:11:05.493 [19750] <2> vnet_pop_string: vnet.c.251: Function failed: 42 
0x0000002a
10:11:05.493 [19750] <2> vnet_pop_signed: vnet.c.301: Function failed: 42 
0x0000002a
10:11:05.493 [19750] <2> ProcessRequests: vnetd.c.286: vnet_pop_signed 
failed: 42 0x0000002a
10:11:05.493 [19750] <2> ListenForConnection: vnetd.c.597: Function 
failed: 42 0x0000002a


On Wed, 14 Jun 2006, Justin Piszcz wrote:

> $ sudo /usr/openv/volmgr/bin/tpconfig -d
> EMM interface initialization failed, status = 77
>
> Anyone know what may be wrong here?
> Also have a ticket open with Symantec..
>