-
Notifications
You must be signed in to change notification settings - Fork 240
Synchronization between Central and Remote #6939
Comments
Hi, Can you open two terminal, 1 on Centreon centraland 1 on Remote Server and watch /var/log/centreon/worker.log Can you put the result of both logs file? |
ok, so there is the result of /var/log/centreon/workger.log on the central : [2018:11:06 03:47:44] Checking for pending export tasks: #1 On the remote : |
@aurelienfx thank you for your answer. To continue the debug, can you execute the following SQL request on both servers:
Then can you send me by private message the content of /usr/share/centreon/filesGeneration/export/<poller_id> directory? (poller_id is the ID of the Remote Server) |
On the RS : https://slack-files.com/T08DULM43-FDW9JBEUQ-639c554e7b The private is message is coming |
Content of the directory sent by slack |
Ok the import task crash on your Remote Server. You need to execute the following command on your remote server using 'centreon' user:
<encrypt_password> is the encrypted password of the or use directly:
Can you send put here the result? |
Can you let me know if on the Remote Server you have the following files:
|
When I pass the command it answer : Invalid credentials The result is ok The 3 .conf are present on the /etc/centreon. |
To select the encrypted password of admin user please execute this request:
|
The result of : on the remote server |
@aurelienfx so if you check the centreon.task table on Remote Server, all task must be "complete"? |
The content of the tables : what do you mean by centreon.task must be complete ? |
@aurelienfx I was expecting the content of the table not the description of the schema ;) |
lpinsivy This is the 3 tables on the zip : https://slack-files.com/T08DULM43-FDY084U8H-c17b9e46ba |
mysql> use centreon;
|
This is the result of previous command : |
Thank you for the result. Everything works perfectly on Centreon Central server. Can you:
|
content sent by slack |
After analysis, the data import process is stopped by the centcore process because the timeout has been reached. The previous error message was:
Now the /var/log/centreon/worker.log file contains complete logs:
|
BUG REPORT INFORMATION
Centreon Web version: 18.10
Centreon Engine version: 18.10
Centreon Broker version: 18.10
OS: CentOS 7 up to date
Additional environment details (AWS, VirtualBox, physical, etc.):
physical server, 4Go of RAM, time synchronised by chrony on a domain ntp server
Steps to reproduce the issue:
2.Launch all services (cbd, centcore, centegine, centreontrapd)
# /usr/share/centreon/bin/centreon -u admin -p centreon -a enableRemote -o CentreonRemoteServer -v @IP_CENTREON_CENTRAL
Describe the results you received:
On the central the configuration is ok :
https://slack-files.com/T08DULM43-FDUGPVDUJ-6723ee5766
But when I try to consult a host on the remote :
https://slack-files.com/T08DULM43-FDUNJG8VB-47f243ccaa
Describe the results you expected:
Can consult correctly the host
Additional information you think important (e.g. issue happens only occasionally):
On the central, I've a status unknown on broker-stats for the remote.
The text was updated successfully, but these errors were encountered: