Jump to content

ICAP/1.0 500 Server Error


Go to solution Solved by JimmyBK,

Recommended Posts

Add more informations

# systemctl status efs.service

Feb 10 16:37:16 localhost icapd[52325]: ESET Server Security Error: Error sending log to the logging service
Feb 10 16:37:16 localhost icapd[52325]: ESET Server Security Warning: Cannot localize text (Cannot accept connection: ${Reason}:#{Reason}=336592946)
Feb 10 16:37:16 localhost icapd[52325]: ESET Server Security Error: Error sending log to the logging service
Feb 10 16:37:16 localhost icapd[52325]: ESET Server Security Warning: Cannot localize text (Cannot accept connection: ${Reason}:#{Reason}=336592946)
Feb 10 16:37:16 localhost icapd[52325]: ESET Server Security Error: Error sending log to the logging service
Feb 10 16:37:16 localhost icapd[52325]: ESET Server Security Warning: Cannot localize text (Cannot accept connection: ${Reason}:#{Reason}=336592946)
Feb 10 16:37:16 localhost icapd[52325]: ESET Server Security Error: Error sending log to the logging service
Feb 10 16:37:16 localhost icapd[52325]: ESET Server Security Warning: Cannot localize text (Cannot accept connection: ${Reason}:#{Reason}=336592946)
Feb 10 16:37:16 localhost icapd[52325]: ESET Server Security Error: Error sending log to the logging service

 

Link to comment
Share on other sites

  • ESET Staff

Hi JimmyBK,

is it possible to specify when this error occurs? is it some special request on icap server? After this error icap server doesn't handle requests anymore? Currently only option to restart it, is to disable and enable it again or directly killing icapd service (it will start again on new request).

Regards,

Peter

Link to comment
Share on other sites

  • ESET Staff

Hi,

I'm glad to hear that you have found solution. But still I would like to investigate cause of this errors, would it be possible to provide us tcpdump of this problematic communication?

Thanks,

Peter.

Link to comment
Share on other sites

Sorry, I can not produce tcpdump.

I have clients on different Linux CentOS version  7.9 and 8.5  and the problem happened only client on CentOS 8.5 that socket connection keep filled up so I have to change to socket connection with timeout limit to make sure that connection will be closed.

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...