ESMC 7 Bad file descriptor

[Shiv 0]

 

Hi there,

I was triaging network connectivity issue on my ERA server and noticed that my server stops accepting new connections because of a bad file descriptor. I noticed that a new stability patch would probably fix the issue and was released however, the module upgrade task doesn't seem to respond to that task. My ESET Security Management Center (Server),  is 7.0.471.0.

1. How do I resolve this?

2. How do manually initiated a module upgrade on the server without going through the webconsole?

 

Logs below:

2019-02-21 23:09:01 Information: Kernel [Thread 7f9a750f6740]: Started module AuthenticationModule (used -792 KB)
2019-02-21 23:09:01 Information: Kernel [Thread 7f9a750f6740]: Starting module CEncryptionModule
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3d7fa700]: Resolving ip address: 10.15.0.247
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3d7fa700]: Receiving ip address: 10.15.0.247 from cache
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3d7fa700]: Successfully received ip address: 10.15.0.247 from cache
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3d7fa700]: Socket accepted. Remote ip address: 10.15.0.247 remote port: 9679
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Resolving ip address: 10.15.0.247
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Receiving ip address: 10.15.0.247 from cache
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Successfully received ip address: 10.15.0.247 from cache
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Forcibly closing sessionId:13, isClosing:0
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Removing session 13
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Closing connection , session id:13
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Socket accepted. Remote ip address: 10.15.0.247 remote port: 9681
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3d7fa700]: Resolving ip address: 10.15.0.247
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3d7fa700]: Receiving ip address: 10.15.0.247 from cache
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Resolving ip address: 10.15.0.247
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Receiving ip address: 10.15.0.247 from cache
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Successfully received ip address: 10.15.0.247 from cache
2019-02-21 23:09:01 Information: NetworkModule [Thread 7f9a3cff9700]: Socket accepted. Remote ip address: 10.15.0.247 remote port: 9683
2019-02-21 23:09:01 Information: Kernel [Thread 7f9a750f6740]: Started module CEncryptionModule (used 0 KB)
2019-02-21 23:09:01 Information: Kernel [Thread 7f9a750f6740]: Used memory after modules start-up is 164312 KB
2019-02-21 23:09:01 Information: CDataMinersModule [Thread 7f9a3e7fc700]: CFunctionalityLogDataMiner: Scheduled first publishing of functionality logs with 5s delay
2019-02-21 23:09:02 Error: NetworkModule [Thread 7f9a27fff700]: remote_endpoint: Bad file descriptor
2019-02-21 23:09:03 Error: NetworkModule [Thread 7f9a27fff700]: remote_endpoint: Bad file descriptor
2019-02-21 23:09:05 Error: NetworkModule [Thread 7f9a27fff700]: remote_endpoint: Bad file descriptor

 

[MartinK 376]

7 hours ago, Shiv said:

1. How do I resolve this?

2. How do manually initiated a module upgrade on the server without going through the webconsole?

This is most probably caused by limits set in your Linux system. Please verify limit for open files in your system, or limits for services in case systemd is used.

In case you are using ESMC Appliance, please check following forum topic:

 

[Shiv 0]

Hi there, 

Thanks for the response. Upping the limit worked.