Skip to main content

Hi,
Since few days, I have following errors in /var/log/centreon-gorgone/gorgoned.log

  

Last week, errors were

 

gorgoned.log-20250629:2025-06-28 03:40:47 - ERROR -  proxy] Send message problem for '10': 
gorgoned.log-20250629:2025-06-28 03:41:47 - ERROR - proxy] Send message problem for '10':

 

And since 2 days, I have this :

2025-06-30 09:23:57 - ERROR - Rproxy] container 1: Receiving DIE: Usage: EV::Loop::io(loop, fh, events, cb) at /usr/share/perl5/vendor_perl/gorgone/class/clientzmq.pm line 399.
2025-06-30 09:29:17 - ERROR - Rproxy] container 1: Receiving DIE: Usage: EV::Loop::io(loop, fh, events, cb) at /usr/share/perl5/vendor_perl/gorgone/class/clientzmq.pm line 399.
2025-06-30 09:34:37 - ERROR - Rproxy] container 1: Receiving DIE: couldn't do /usr/local/lib64/perl5/auto/share/dist/FFI-Platypus/config.pl Too many open files at /usr/local/lib64/perl5/FFI/Platypus/ShareConfig.pm line 45.
2025-06-30 09:34:37 - ERROR - Rproxy] container 1: Receiving DIE: couldn't do /usr/local/lib64/perl5/auto/share/dist/FFI-Platypus/config.pl Too many open files at /usr/local/lib64/perl5/FFI/Platypus/ShareConfig.pm line 45.

 

There's an issue that recommends rebuilding /var/lib/centreon-gorgone/history.sdb.

What do you think?

[solved]

Problem solved on my own.

The bottom line is that some joker had changed the Poller's VIP address. This meant that communication between Central and Poller was inevitably less effective. Once the IP address was corrected and the Gorgoned services restarted on both sides, the problem disappeared.

 

What put me on the trail

2025-07-02 09:02:37 - INFO -  proxy] Ping timeout from ‘10’
2025-07-02 09:02:37 - INFO - Fproxy] Ping max timeout reached from ‘10’
2025-07-02 09:02:37 - INFO - -proxy] Close connection for 10

 


Reply