-
Titre
No DBSS - Instance Availability rule fired when server is rebooted -
Description
The SQL Server system was rebooted and no DBSS - Instance Availability alarm was fired from the Foglight SQL Server cartridge. -
Cause
The logic behind these two rules is as follows:- The Instance Availability rule will fire when the service status is 'stopped'
- The Usability Connection Availability rule will fire when the service status is running and we can't open a connection against the instance
-
Résolution
In this case only the Usability Connection Availability rule should fire an alarm when a server is rebooted.There could be also a situation in which a reboot take less then 5min which is the collection frequency. If this is the case there would be no alarm
Additional notesIf you are using an OS account that has Administrator rights.
When the SQL Server service is turned off, you should get
--> "Instance Down" printed in the Up Since
--> Usability, Instance Availability alarm fire
If you are using an OS account that does not have Administrator rights.
When the service is turned off, you should get
--> "-" printed in the Up Since
--> Credential Management Alarm fires like this">> Failure: Cannot establish connection to FOG-SQL2019: WinRM request to http://FOG-SQL2019:5985/wsman failed: received HTTP/401"
--> Usability OS Connection Availability Alarm fires like this
"The connection to the operating system failed. A connection could not be established"If you have the service running but you change the username in the DB agent.
--> "-" printed in the Up Since
--> "-" printed in the Workload