Task #2228
closed
Nagios: renamining VM for mongodb nodes
100%
Description
nagios shows the old names for mongodb nodes:
node58.p.d4science.research-infrastructures.eu node67.p.d4science.research-infrastructures.eu node73.p.d4science.research-infrastructures.eu node80.p.d4science.research-infrastructures.eu node84.p.d4science.research-infrastructures.eu
could you change these host names with the new host names, please?
monogo1-p-d4s.d4science.org monogo2-p-d4s.d4science.org monogo3-p-d4s.d4science.org monogo4-p-d4s.d4science.org monogo5-p-d4s.d4science.org
Updated by Andrea Dell'Amico over 9 years ago
- Status changed from New to In Progress
What about this one?:
mongo6-p-d4s.d4science.org #node85.p.d4science.research-infrastructures.eu
Updated by Andrea Dell'Amico over 9 years ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
I changed the other hostnames.
Updated by Andrea Dell'Amico over 9 years ago
- % Done changed from 100 to 80
And now we have some errors and warnings.
Updated by Roberto Cirillo over 9 years ago
mongo6 is a backup node it isn't attached to the replicaSet system. Of course, you can rename it as mongo6.
(You mean, from node85.p.d4science.research-infrastructures.eu to mongo6-p-d4s.d4science.org)
Updated by Roberto Cirillo over 9 years ago
Andrea Dell'Amico wrote:
And now we have some errors and warnings.
The warnings are due to the upgrade of the nodes as reported here: #2121
After the upgrade I'm going to recheck these warnings.
Updated by Roberto Cirillo over 9 years ago
Roberto Cirillo wrote:
mongo6 is a backup node it isn't attached to the replicaSet system. Of course, you can rename it as mongo6.
(You mean, from node85.p.d4science.research-infrastructures.eu to mongo6-p-d4s.d4science.org)
yes, exactly what I mean
Updated by Andrea Dell'Amico over 9 years ago
Roberto Cirillo wrote:
Andrea Dell'Amico wrote:
And now we have some errors and warnings.
The warnings are due to the upgrade of the nodes as reported here: #2121
After the upgrade I'm going to recheck these warnings.
No, it's the check behaviour that changed. I'm trying to understand if the code can be easily modified to not return errors when executed on non master nodes. Otherwise we shall need to disable some checks on the slave nodes, but the situation will become inconsistent if the master changes.
Updated by Andrea Dell'Amico over 9 years ago
- % Done changed from 80 to 100
The mongodb check has been fixed.
@tommaso.piccioli@isti.cnr.it tells me that mongo6 is an instance only used when a recovery is needed, so its availability is not guaranteed. I think it should not be monitored.
