ACSLS - STATUS_NI_FAILURE - Errno = 9 (Bad file number) (Doc ID 1509444.1)

Last updated on FEBRUARY 21, 2024

Applies to:

Symptoms

ACSLS was restarted multiple times but STATUS_NI_FAILURE and "Server system network interface failure" errors persist.

The STATUS_NI_FAILURE errors started just out of the blue:
------
2012-11-07 22:20:17 CSI[0]:
1024 N csi_client_proc.c 1 503
ONC RPC: st_send_packet(): status:STATUS_NI_FAILURE; failed: clnt_call()
Cannot send message to NI:discarded, RPC: Unable to send
Errno = 9 (Bad file number)
Remote Internet address: 111.222.333.444, Port: 56678

2012-11-07 22:20:17 ACSSA[0]:
1441 N sa_demux.c 1 296
Server system network interface failure.

2012-11-07 22:24:04 CSI[0]:
1024 N csi_client_proc.c 1 503
ONC RPC: st_send_packet(): status:STATUS_NI_FAILURE; failed: clnt_call()
Cannot send message to NI:discarded, RPC: Unable to send
Errno = 9 (Bad file number)
Remote Internet address: 111.222.333.444, Port: 56677


Error message that keeps popping up on cmd_proc operator console screen:
"Server system network interface failure"


traceroute and ping response times from the ACSLS server to the client server are not fast enough. traceroute and ping response times from the client server to the ACSLS server are optimal.

Changes

No known change according to the customer.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.