proper upgrade method from 4.3.27 to 4.3.30
One of my Xymon servers is running Ubuntu v16.04 and Xymon Server v4.3.27 I was gonna build a brand new VM and install the Xymon v4.3.30 and go through all the config edits, but if I can just upgrade Xymon instead that will save me a lot of time, but I'm unclear on the correct method.? I'd like all the configs and paths to stay intact. Is it as simple as unzipping the 4.3.30.tar.gz and running ./configure ?
I will of course be snapshoting my server prior to trying this, but I thought I'd ask if anyone has attempted this and run into any issues they could share.
-- Kris Springer
Hi,
Yes, simply running a 'make install' is enough. The only thing you really need is the content of the etc directory and optionally the tmp directory (for the checkpoint files).
Stef
On 2021-05-28 22:16, Kris Springer wrote:
One of my Xymon servers is running Ubuntu v16.04 and Xymon Server v4.3.27 I was gonna build a brand new VM and install the Xymon v4.3.30 and go through all the config edits, but if I can just upgrade Xymon instead that will save me a lot of time, but I'm unclear on the correct method. I'd like all the configs and paths to stay intact. Is it as simple as unzipping the 4.3.30.tar.gz and running ./configure ?
I will of course be snapshoting my server prior to trying this, but I thought I'd ask if anyone has attempted this and run into any issues they could share.
I ran ./configure make make install
All seemed to install ok.? I rebooted for good measure.? All the *http* tests are red and the *sslcert* tests have gone purple.? All the other tests seem ok though.
The failing https tests say things like ?? Connected, but got empty response (code: 0) ?? and ?? Bad Request
xymonnet.log shows this. Unspecified SSL error in SSL_connect to https (47873/tcp) on host REDACTED: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
What's going on?? Is there a quick fix?
Kris Springer
On 5/30/21 4:06 AM, Stef Coene wrote:
Hi,
Yes, simply running a 'make install' is enough. The only thing you really need is the content of the etc directory and optionally the tmp directory (for the checkpoint files).
Stef
On 2021-05-28 22:16, Kris Springer wrote:
One of my Xymon servers is running Ubuntu v16.04 and Xymon Server v4.3.27 I was gonna build a brand new VM and install the Xymon v4.3.30 and go through all the config edits, but if I can just upgrade Xymon instead that will save me a lot of time, but I'm unclear on the correct method. I'd like all the configs and paths to stay intact. Is it as simple as unzipping the 4.3.30.tar.gz and running ./configure ?
I will of course be snapshoting my server prior to trying this, but I thought I'd ask if anyone has attempted this and run into any issues they could share.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
A temporary work-around might be to find (or compile) a copy of the older xymonnet binary and run that version instead of the newer version (eg by tweaking tasks.cfg). I've had to do the reverse in the past, to provide support for newer HTTPS implementations without going through the down-time (and change management bureaucracy) to replace the whole product.
Once you have your tests working again, you have time to troubleshoot the new xymonnet (eg by running from the command-line in debug mode). Or if the tests don't start working again with the old xymonnet, you've at least ruled out one component from being the cause.
J
On Mon, 31 May 2021 at 15:32, Kris Springer <kspringer at innovateteam.com> wrote:
I ran ./configure make make install
All seemed to install ok. I rebooted for good measure. All the *http* tests are red and the *sslcert* tests have gone purple. All the other tests seem ok though.
The failing https tests say things like Connected, but got empty response (code: 0) and Bad Request
xymonnet.log shows this. Unspecified SSL error in SSL_connect to https (47873/tcp) on host REDACTED: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
What's going on? Is there a quick fix?
Kris Springer
On 5/30/21 4:06 AM, Stef Coene wrote:
Hi,
Yes, simply running a 'make install' is enough. The only thing you really need is the content of the etc directory and optionally the tmp directory (for the checkpoint files).
Stef
On 2021-05-28 22:16, Kris Springer wrote:
One of my Xymon servers is running Ubuntu v16.04 and Xymon Server v4.3.27 I was gonna build a brand new VM and install the Xymon v4.3.30 and go through all the config edits, but if I can just upgrade Xymon instead that will save me a lot of time, but I'm unclear on the correct method. I'd like all the configs and paths to stay intact. Is it as simple as unzipping the 4.3.30.tar.gz and running ./configure ?
I will of course be snapshoting my server prior to trying this, but I thought I'd ask if anyone has attempted this and run into any issues they could share.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
After trying multiple things I just gave up and reverted back to the functioning VM snapshot.
I thought upgrading might fix the issue I was having with the secure XymonPSClient data not working correctly, but it
didn't, so I'm just going to rebuild the whole OS with latest distro and latest Xymon and see if that changes anything.
Have been planning that for some time anyways. Upgrading the old system caused more trouble that it solved.
-- Kris Springer
-----Original Message----- From: Jeremy Laidman <jeremy at laidman.org> To: Kris Springer <kspringer at innovateteam.com> Cc: Stef Coene <stef.coene at docum.org>, xymon at xymon.com <xymon at xymon.com> Subject: Re: [Xymon] proper upgrade method from 4.3.27 to 4.3.30 Date: Mon, 31 May 2021 22:28:02 +1000
A temporary work-around might be to find (or compile) a copy of the older xymonnet binary and run that version instead of the newer version (eg by tweaking tasks.cfg). I've had to do the reverse in the past, to provide support for newer HTTPS implementations without going through the down-time (and change management bureaucracy) to replace the whole product.
Once you have your tests working again, you have time to troubleshoot the new xymonnet (eg by running from the command- line in debug mode). Or if the tests don't start working again with the old xymonnet, you've at least ruled out one component from being the cause.
J
On Mon, 31 May 2021 at 15:32, Kris Springer <kspringer at innovateteam.com> wrote:
I ran ./configure make make install
All seemed to install ok. I rebooted for good measure. All the http tests are red and the sslcert tests have gone purple. All the other tests seem ok though.
The failing https tests say things like Connected, but got empty response (code: 0) and
Bad Requestxymonnet.log shows this. Unspecified SSL error in SSL_connect to https (47873/tcp) on host REDACTED: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
What's going on? Is there a quick fix?
Kris Springer
On 5/30/21 4:06 AM, Stef Coene wrote:
Hi,
Yes, simply running a 'make install' is enough. The only thing you really need is the content of the etc directory and optionally the tmp directory (for the checkpoint files).
Stef
On 2021-05-28 22:16, Kris Springer wrote:
One of my Xymon servers is running Ubuntu v16.04 and Xymon Server v4.3.27 I was gonna build a brand new VM and install the Xymon v4.3.30 and go through all the config edits, but if I can just upgrade Xymon instead that will save me a lot of time, but I'm unclear on the correct method. I'd like all the configs and paths to stay intact. Is it as simple as unzipping the 4.3.30.tar.gz and running ./configure ?
I will of course be snapshoting my server prior to trying this, but I thought I'd ask if anyone has attempted this and run into any issues they could share.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
participants (3)
-
jeremy＠laidman.org
-
kspringer＠innovateteam.com
-
stef.coene＠docum.org