Comments
2 comments
-
Is anyone able to help us out with this?
-
Hi Peter,
I know I just replied to the ticket you raised as well, but for anyone else seeing this -
The update process starts with the webserver and then does the Base Monitor service. On a single server this happens at essentially the same time, but on separate servers, there will be some period of time in which the weberver is on a later version than the Base Monitor.
In this state, while the data from the Base Monitor is not visible in the web frontend (or you can't open the web frontend due to the mismatch being on the primary Base Monitor), the Base Monitor is still gathering data, alerting on that and sending notifications. So, while you will not be able to see this in the web frontend, the data is still being gathered, alerted on and having notifications sent until the two are on the same version.
Kind regards,
Alex
Add comment
Please sign in to leave a comment.
The question is hoe to do this without temporary loose access to the servers. We have until know this manually but I did notice that when first updating the we server to the new version then it lost the connection to the base monitors until they also were updating the the same version. Is there some way that the update can be done without loosing the connectivity? Or is the only option to get teh automation done and carefully schedule the updating of the base monitor and keep fingers scrossed that the update is working smoothly?
Thanks,
Peter Åkerlund
Senior DevOps DBA
RELEX Solutions