Service Down Alert Offline Notification Emails contain incorrect timestamp


#1

There appears to be a bug with the “Service down alert” Notification Emails.

“Online” Email Notifications contain the correct timestamp whereas “Offline” notifications contain an incorrect timestamp.

e.g.
Received: 26/02/2019 05:52:
The MySQL Server connection on BW-CSI4-ESX1 is online as 26/02/2019 05:47:14

Received: 26/02/2019 05:47:
The MySQL Server connection on BW-CSI4-ESX1 is offline as 25/02/2019 11:07:59

We are using the latest version v12.2.1.


#2

Hi John_Randall,

Thanks for the issue reporting. Please give us some time to check this case.

Sorry for the inconvenience.


#3

Hi John_Randall,

We have fixed this issue in the alpha version. Could you please download it at https://sqlbackupandftp.com/download/alpha and check if it works?

Sorry for the inconvenience.


#4

Thanks. I have installed the alpha version and will let you know how we get on.


#5

Thank you. Please feel free to contact us on any issues or concerns.


#6

Hi Alexander, the problem has not been fixed in the new v12.2.3 alpha version but I can provide some more information. Please see extracts from 3 consecutive alert emails for the same MySQL Server connection below.

  1. I think it would be clearer if the time in the subject line of the “online” alerts stated the time that the service was restored (rather than the time that the service went down).

  2. As you can see, the time in the subject line of the “offline” alert has been incorrectly set as the time that the service was restored (“till”) from the body of the earlier alert.

Alert email extracts:

Received: 17/03/2019 23:32:
Subject: The MySQL Server connection on BW-CSI4-ESX1 is online as 17/03/2019 23:28:35
Body: … received no communication from MySQL Server 172.16.2.63:3306 from 17/03/2019 23:28:35 till 17/03/2019 23:32:00 …

Received: 17/03/2019 23:29
Subject: The MySQL Server connection on BW-CSI4-ESX1 is offline as 13/03/2019 22:42:00

Received: 13/03/2019 22:42
Subject: The MySQL Server connection on BW-CSI4-ESX1 is online as 13/03/2019 22:38:23
Body: … received no communication from MySQL Server 172.16.2.63:3306 from 13/03/2019 22:38:23 till 13/03/2019 22:42:00 …

Hope this helps.


#7

Hi John_Randall,

We have checked this issue again and everything works smoothly. Could you please make sure that you installed the latest alpha version https://sqlbackupandftp.com/download/alpha ?

Sorry for the inconvenience.


#8

Hi Alexander,
Very strange. I have downloaded and reinstalled the alpha version (same version number: v12.2.3) and will let you know how it goes…


#9

Thanks, yes, the version’s number should be the same. Please let us know if it works.

Sorry for the inconvenience.


#10

Hi Alexander
Afraid the problem is still there - See extracts from the alert emails below:

Received: 21/03/2019 00:32:
Subject: The MySQL Server connection on BW-CSI4-ESX1 is online as 21/03/2019 00:27:01
Body: … received no communication from MySQL Server 172.16.2.63:3306 from 21/03/2019 00:27:01 till 21/03/2019 00:31:29 …

Received: 21/03/2019 00:28
Subject: The MySQL Server connection on BW-CSI4-ESX1 is offline as 19/03/2019 18:06:25

Received: 19/03/2019 18:07
Subject: The MySQL Server connection on BW-CSI4-ESX1 is online as 19/03/2019 18:03:00
Body: … received no communication from MySQL Server 172.16.2.63:3306 from 19/03/2019 18:03:00 till 19/03/2019 18:06:25 …

Which individual application file contains the functionality? Would you like me to check its details (date/size/version) to confirm that it has been installed in the Program Files directory?


#11

Thanks for the reply, please give us some time to check this issue.

Sorry for the inconvenience.