Guys, this is two days now and not a single reply from the Team and there’s already two threads with maybe similar problems (

) for the currently released new Major-Version. This is really not how you get us to think about a costly license to use the advanced features, seeing how the support works :(

Hi @TA-FFM, sorry you don't have an answer to your problem yet. I will do my best to get you an answer asap. Cheers, 

Hi TA-FFM,

Several conditions need to be matched in order to get resource status working.

First could you please check that you have the unified-sql output correctly configured ?

In Configuration → Pollers → Broker configuration - centreon-broker-master under the “Output” tab.

Second, you will need the BBDO protocol set to the version 3. This can be found in the same form under the “General” tab - Advanced options

This configuration will ensure that the centreon_storage.resources table in correctly filled (it is the table used by resource status). If changes are made to the engine/broker configuration do not forget to restart the dedicated services.

Regards

Hi Adrien,

first, thank you very much for your answer.

I habe my BBDO set to 2.0.0 on the whole Plattform. So prob that is using my Problems. I already looked in the centreon_storage reosurces table and there is whole lot of data in there which seems to show that the unified sql is working? I also checked the DB-Access creds and tehy work from the Central Server logging into the seperate DB.

Is there an order in which i should change the setting and restart the Central, Remotes and pollers or just restart them all at the same time?

Regards

Timo

BTW, would have been nice to see one of those yellow Warning Blocks in the Upgrade-Instructions telling about the need to have BBDO 3 on all of them……maybe add one? ;)

https://docs.centreon.com/docs/upgrade/upgrade-from-22-04/

Okay, I am currently seeking for information regarding this procedure with the dedicated Team.

Just in case, this might be a simple “cache issue” regarding PHP, could you please try this

> Connect with a terminal on the Central Server
sudo -u apache /usr/bin/php /usr/share/centreon/bin/console c:c

Regards

Hi Adrien, unfortunately that didn’t work:

droot@c2-central-web01 ~]# sudo -u apache /usr/bin/php /usr/share/centreon/bin/console c:c

 // Clearing the cache for the prod environment with debug false                                                        

                                                                                                                        
  OK] Cache for the "prod" environment (debug=false) was successfully cleared.                                          
                                                                                                                        

 root@c2-central-web01 ~]# 

Okay,

I just to ensure that this might be a PHP issue could you please check those files ?

> cat /usr/share/centreon/config/packages/Centreon.yaml | grep Resource -C 3
> cat /usr/share/centreon/config/packages/Centreon.yaml | grep parameters -A 8
> cat /usr/share/centreon/.env*

And FYI, if you are using Unified SQL with BBDO 2.0 you might see some errors here

tail -f /var/log/centreon-broker/central-broker-master.log

Thanks !

Regards

Adrien, The Outputs as requested:

>root@c2-central-web01 ~]# cat /usr/share/centreon/config/packages/Centreon.yaml | grep Resource -C 3
    _instanceof:
        Core\Infrastructure\RealTime\Hypermedia\HypermediaProviderInterface:
            tags:  'realtime.hypermedia']
        Core\Domain\RealTime\ResourceTypeInterface:
            tags:  'monitoring.resource.type']
        Core\Resources\Infrastructure\Repository\ResourceACLProviders\ResourceACLProviderInterface:
            tags:  'monitoring.resource.acl']
        Core\Security\ProviderConfiguration\Application\Repository\ReadProviderConfigurationsRepositoryInterface:
            tags:  'authentication.provider.repositories']
>root@c2-central-web01 ~]# 

>root@c2-central-web01 ~]# cat /usr/share/centreon/config/packages/Centreon.yaml | grep parameters -A 8
parameters:
    api.header: "Api-Version"
    api.version.latest: "22.10"
    debug_log_file: '%log_path%/centreon-web.log'
    env(DEBUG_LEVEL): !php/const Monolog\Logger::NOTICE
    curl.timeout: 60
    debug_level: "%env(int:DEBUG_LEVEL)%"
    env(DEBUG_CONTACT): null

>root@c2-central-web01 ~]# 

>root@c2-central-web01 ~]# cat /usr/share/centreon/.env*
APP_ENV=prod
APP_SECRET=3060d6e24a3aa0fcb3271db089d1e987acfea1e272a892ef6f4c0a4404eb8b45
<?php

// This file was generated by running "composer dump-env prod"

return array (
  'APP_ENV' => 'prod',
  'APP_SECRET' => '3060d6e24a3aa0fcb3271db089d1e987acfea1e272a892ef6f4c0a4404eb8b45',
);
>root@c2-central-web01 ~]# 

Yes ok thanks everything looks pretty normal.

I think you should switch the version of BBDO to 3.0.0 and restart cbd and engine. That will fix your issue.

Adrien, i’ll try asap in a downtime and report back to you.

Anything from your devs about the order of restarts on the remotes/pollers? I assume first the central and then the peripherals?

Regards

Timo

Team lead regarding this subject is OFF today. I did not have the needed information. I guess you are right regarding the order.

Let me know if you issue has been fixed by doing this change

Regards

Hi TA-FFM,

I have fixed an issue on Resource Status, which lead to a new version release.

https://docs.centreon.com/docs/releases/centreon-os/#22101

This is supposed to fix an issue regarding duplicated lines, but when I found the issue I also experienced an empty page.

Could you update your platform to 22.10.1 and tell me if the issue is still occurring ?

Regards

Adrien

HI Adrien, will do this evening after the colleques went home and report back to you.

Regards

Timo

Hi Adrien,

unfortunately it didn’t change my empty resources status-Page.

Regards

Timo

I will also do the BBDO-Change from 2.0.0 to 3.0.0 tonight and report aftewards

Hi,

I’ve followed all the recipies in this thread and still got the same result : Monitoring > Resource Status page is empty since 22.10 update !

Our Centreon instance is installed from OVA for 2 years and has been updated several times. With success until this time !

Regards

BTW, it appears as if my resources-table in centreon_storage is not getting updatet since the update after all, plus all entries are set to “enabled=0”

@Adrien Morais-Mestre  Does this help in finding the Problem?

Multiple reboot didn’t change anything, but this solved my problem :

# centreon -u admin -p passw0rd -a POLLERTEST -v Central
# centreon -u admin -p passw0rd -a POLLERRESTART -v Central
# centreon -u admin -p passw0rd -a APPLYCFG -v Central

That’s very stange. You did nothing else then restart your Central Poller ,but through the old clapi.

If a reboot didn’t restart your engine/Broker you might want to check if it is enabled in systemctl and if the config is correct regarding Engine and Broker.

Unf. it doesn’t help me

Regards

Timo

Oh, and you should change your Password.

All required Centreon Systemd services are enabled. I’ve then rebooted the VM and resource page is still full of items !

Next time, I will make a snapshot before upgrading !

@Adrien Morais-Mestre - good news.

The change for the whole platform (1 Central, 6 Remotes, 15 Pollers) from bbdo 2.0.0 to 3.0.0 really did it and brought the resources-Page back to life.

As written earlier - you might want to highlight that as a dependency on the Upgrade-Documentation. It was all working for me with 2.0.0. before 22.10 and i found it a bit scary to being forced to revert to the deprecatet pages ;)

Regards

Timo

TA-FFM that is a great news ! Thanks for your patience hope you’ll continue to enjoy Resource Status page then !

Regards

Adrien

> Connect with a terminal on the Central Server
sudo -u apache /usr/bin/php /usr/share/centreon/bin/console c:c

Thank you. I upgraded from 21.10 to 22.10 and was getting the issue with empty resources. That did the job