-
Notifications
You must be signed in to change notification settings - Fork 15
Broker Error Log: feeder: error occured while processing client #131
Comments
Hi, During a such situation, did you try to keep telnet running long enough ? Is it not interrupted after several minutes ? Another question, on your poller output you can configure the retry interval to reduce the time between too connections. Did you try to change it with a small value, 5 seconds or so ? Regards. |
Hi, the last time we changed the value to 60. Since this moment, there are only 2 log entries since today night. Much better than before. Now we changed the value to 5 as you suggested. Let`s wait a couple of days, what happen in the logs. Regards |
Unfortunately the log will be filled every few seconds: |
It seems to be similar, my poller shows as not running and none of its host appear at the monitoring tab: OS: CentOS 7.4 (AArch64) Every time I restart the poller's
|
Hi, For your Centreon Broker output on distant poller:
Regards, |
The error tag is too much in those logs. The connection is lost, broker or cbd see that, the connection is established again and data are sent. |
Hi,
one of our customer has sometimes problems with a outside poller connection. Sometimes the status icon from the display counter is in a red/error state. While the problem was present the vpn was working fine and a test telnet connection to bbdo port 5669 was successfully. Only the broker itself was disconnected. We investigated much time in troubleshooting and increased the log. The monitoring system is the only system with problems, other applications are working well via VPN include important applications like SAP ( user will report immediately if an error occured).
Display Poller Broker Logsettings:
Centreon Versions:
centreon-broker-cbmod-3.0.8-1.el6.x86_64
centreon-broker-storage-3.0.8-1.el6.x86_64
centreon-syslog-frontend-1.5.4-1.el6.noarch
centreon-engine-1.7.2-3.el6.x86_64
centreon-connector-1.1.2-1.el6.x86_64
centreon-common-2.8.12-7.el6.noarch
centreon-bam-server-3.5.5-1.el6.noarch
centreon-bi-server-3.1.5-1.el6.noarch
centreon-broker-3.0.8-1.el6.x86_64
centreon-connector-ssh-1.1.2-1.el6.x86_64
centreon-perl-libs-2.8.12-7.el6.noarch
centreon-poller-centreon-engine-2.8.12-7.el6.noarch
centreon-pp-manager-2.2.0-4.el6.noarch
centreon-2.8.12-7.el6.noarch
centreon-engine-daemon-1.7.2-3.el6.x86_64
centreon-connector-perl-1.1.2-1.el6.x86_64
centreon-release-3.4-4.el6.noarch
centreon-base-config-centreon-engine-2.8.12-7.el6.noarch
centreon-syslog-server-1.2.5-6.el6.noarch
centreon-engine-extcommands-1.7.2-3.el6.x86_64
centreon-broker-cbd-3.0.8-1.el6.x86_64
centreon-clib-1.4.2-1.el6.x86_64
centreon-broker-core-3.0.8-1.el6.x86_64
centreon-trap-2.8.12-7.el6.noarch
centreon-web-2.8.12-7.el6.noarch
centreon-license-manager-1.0.1-3.el6.noarch
OS: CentOS 6.9
Additional environment details :Hardware maschine with a central and a display poller. Display poller is located in the US and connected via MPLS from Telekom.
Broker log from display poller with a human readable dateformat:
[Thu Sep 28 06:23:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13866': TCP peer '1.2.3.4:37084' is disconnected
[Thu Sep 28 06:28:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13867': TCP peer '1.2.3.4:38130' is disconnected
[Thu Sep 28 06:33:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13868': TCP peer '1.2.3.4:39174' is disconnected
[Thu Sep 28 06:38:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13869': TCP peer '1.2.3.4:40220' is disconnected
[Thu Sep 28 06:43:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13870': TCP peer '1.2.3.4:41272' is disconnected
[Thu Sep 28 06:48:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13871': TCP peer '1.2.3.4:42326' is disconnected
[Thu Sep 28 06:53:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13872': TCP peer '1.2.3.4:43376' is disconnected
[Thu Sep 28 06:58:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13873': TCP peer '1.2.3.4:44426' is disconnected
[Thu Sep 28 07:03:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13874': TCP peer '1.2.3.4:45478' is disconnected
[Thu Sep 28 07:08:10 2017] error: feeder: error occured while processing client 'central-broker-master-input-13875': TCP peer '1.2.3.4:46524' is disconnected
[Thu Sep 28 07:13:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13876': TCP peer '1.2.3.4:47568' is disconnected
[Thu Sep 28 07:18:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13877': TCP peer '1.2.3.4:48616' is disconnected
[Thu Sep 28 07:23:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13878': TCP peer '1.2.3.4:49668' is disconnected
[Thu Sep 28 07:28:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13879': TCP peer '1.2.3.4:50714' is disconnected
[Thu Sep 28 07:33:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13880': TCP peer '1.2.3.4:51766' is disconnected
[Thu Sep 28 07:38:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13881': TCP peer '1.2.3.4:52812' is disconnected
[Thu Sep 28 07:43:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13882': TCP peer '1.2.3.4:53864' is disconnected
[Thu Sep 28 07:48:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13883': TCP peer '1.2.3.4:54916' is disconnected
[Thu Sep 28 07:53:09 2017] error: feeder: error occured while processing client 'central-broker-master-input-13884': TCP peer '1.2.3.4:55966' is disconnected
The log reports every few minutes problems with the connection but the status of the display counter is ok. The problem is rare and sporadic, log is constant.
Regards
The text was updated successfully, but these errors were encountered: