Hello,
I seen another user here has posted this same exact problem. It was marked solved however it was not not resolved.
Everything was working perfectly we were using the platform with plugins and building out the monitoring. Then out of nowhere we get errors “ No plugin pack found” and Oops, something went wrong” Looking at output the server requests are getting 404 errors for page not found when attempting to connect to apo.imp.centreon.com resources
I have been through all the troubleshooting guidance from Centreon in regards to identifying the source problem.
We are moving towards acquiring 500+ host licenses, while we are working on that we are running IT-100 licensing at the moment.
This makes me believe it is not our instance that's the issue here.
Would love some guidance as this may be a deal breaker for our organizational use
Troubleshooting:
/etc/centreon/license.d/epp.license - License file is valid
Token installed
Network is reachable
NO PROXY IS USED
Centreon version:
centreon-web-21.10.5-2.el7.centos.noarch
Error Log:
2022-04-11 18:09|0|0|[RestNotFoundException] https://api.imp.centreon.com/v2/auth/instance : Page not found
2022-04-11 18:09|0|0|[RestNotFoundException] https://api.imp.centreon.com/v2/auth/instance : Page not found
2022-04-11 18:09|0|0|[RestNotFoundException] https://api.imp.centreon.com/v2/auth/instance : Page not found
2022-04-11 18:09|0|0|[RestNotFoundException] https://api.imp.centreon.com/api/pluginpack/pluginpack?page[offset]=0&page[limit]=9&filter[slugs]=base-generic,network-cisco-standard-snmp,hardware-servers-de$
2022-04-11 18:12|0|0|[RestNotFoundException] https://api.imp.centreon.com/v2/auth/instance : Page not found
2022-04-11 18:12|0|0|[RestNotFoundException] https://api.imp.centreon.com/v2/auth/instance : Page not found
dig api.imp.centreon.com
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.9 <<>> api.imp.centreon.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38494
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;api.imp.centreon.com. IN A
;; ANSWER SECTION:
api.imp.centreon.com. 60 IN A 52.208.183.126
api.imp.centreon.com. 60 IN A 52.215.52.31
api.imp.centreon.com. 60 IN A 52.16.83.37
;; Query time: 12 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Apr 20 14:46:53 BST 2022
;; MSG SIZE rcvd: 97
curl -v https://api.imp.centreon.com/api/monitoring
* About to connect() to api.imp.centreon.com port 443 (#0)
* Trying 52.16.83.37...
* Connected to api.imp.centreon.com (52.16.83.37) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* subject: CN=api.imp.centreon.com
* start date: May 10 00:00:00 2021 GMT
* expire date: Jun 08 23:59:59 2022 GMT
* common name: api.imp.centreon.com
* issuer: CN=Amazon,OU=Server CA 1B,O=Amazon,C=US
> GET /api/monitoring HTTP/1.1
> User-Agent: curl/7.29.0
> Host: api.imp.centreon.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 20 Apr 2022 13:47:21 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 15
< Connection: keep-alive
< x-amzn-RequestId: bd0a3700-5579-4a3f-952c-a882d4b3a4ff
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, centreon-imp-token
< x-amzn-Remapped-Content-Length: 15
< x-amzn-Remapped-Connection: keep-alive
< x-amz-apigw-id: Q4dEiFYoDoEF2Eg=
< X-Powered-By: Express
< Access-Control-Allow-Methods: GET
< Access-Control-Allow-Methods: POST
< Access-Control-Allow-Methods: PATCH
< Access-Control-Allow-Methods: OPTIONS
< ETag: W/"f-VaSQ4oDUiZblZNAEkkN+sX+q3Sg"
< x-amzn-Remapped-Date: Wed, 20 Apr 2022 13:47:21 GMT
<
* Connection #0 to host api.imp.centreon.com left intact
Best answer by brian2022
View original