Task #3157
closed
Improve the nagios check for the Smartgears (not the smart executor ones) nodes
100%
Description
The check needs to get the /whn-manager/gcube/resource/ URL and search for the The resource is active string
Related issues
Updated by Andrea Dell'Amico over 9 years ago
- Related to Task #850: Investigate a new way for check smartgears container by nagios added
Updated by Andrea Dell'Amico over 9 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 80
The check is now active. The following hosts seems not to be running a smartgear service:
dewn03.madgik.di.uoa.gr dewn08.madgik.di.uoa.gr dewn09.madgik.di.uoa.gr dl17.di.uoa.gr dl23.di.uoa.gr node13.p.d4science.research-infrastructures.eu node31.p.d4science.research-infrastructures.eu node51.p.d4science.research-infrastructures.eu
@roberto.cirillo@isti.cnr.it could you check? In the list attached in #3140 all those hosts are indicated as SMART
Updated by Roberto Cirillo over 9 years ago
Andrea Dell'Amico wrote:
The check is now active. The following hosts seems not to be running a smartgear service:
dewn03.madgik.di.uoa.gr dewn08.madgik.di.uoa.gr dewn09.madgik.di.uoa.gr dl17.di.uoa.gr dl23.di.uoa.gr node13.p.d4science.research-infrastructures.eu node31.p.d4science.research-infrastructures.eu node51.p.d4science.research-infrastructures.eu
These hosts are smartgears containers.
@roberto.cirillo@isti.cnr.it could you check? In the list attached in #3140 all those hosts are indicated as SMART
All nodes indicated in the list as SMART are smartgears containers while the gCore container are indicated as "GCORE". I'm sorry for the confusion.
Updated by Andrea Dell'Amico over 9 years ago
Roberto Cirillo wrote:
Andrea Dell'Amico wrote:
The check is now active. The following hosts seems not to be running a smartgear service:
dewn03.madgik.di.uoa.gr dewn08.madgik.di.uoa.gr dewn09.madgik.di.uoa.gr dl17.di.uoa.gr dl23.di.uoa.gr node13.p.d4science.research-infrastructures.eu node31.p.d4science.research-infrastructures.eu node51.p.d4science.research-infrastructures.euThese hosts are smartgears containers.
All nodes indicated in the list as SMART are smartgears containers while the gCore container are indicated as "GCORE". I'm sorry for the confusion.
It's me that is confused now: I agree that those hosts are smartgears containers, and the active check is the smartgears one. But it's failing because the URL /whn-manager/gcube/resource/ does not exist (404).
Updated by Andrea Dell'Amico over 9 years ago
Could it be a problem caused by the whn-manager version? I see that node31.p.d4science.research-infrastructures.eu is running common-smartgears-1.2.0-3.1.0-probe and whn-manager-1.0.0-3.1.0, installed on april 2014.
Updated by Roberto Cirillo over 9 years ago
The problem is not the whn-manager version but the whn-manager deployment. The whn-manager has been deployed with the version in the war name.
For example, if you try this url: http://dewn03.madgik.di.uoa.gr:8080/whn-manager-1.0.0-3.1.0/gcube/resource/ it works. So, the nagios check is correct.
I'm going to open a ticket for this task.
Updated by Roberto Cirillo over 9 years ago
- Related to Task #3159: Delete whn-manager version from whn-manager war name added
Updated by Andrea Dell'Amico over 9 years ago
- Status changed from In Progress to Closed
