[Xymon 4.3.7] bad imaps check

7 messages in this thread

list David Agbo · Wed, 04 Apr 2012 18:42:07 +0200 ·

Hi,

I have installed Xymon 4.3.7 on Centos 5.8 x64. Before that, I have installed it on a RHEL 5.6, everything worked fine until I tried to check an imaps server. The Xymon on RHEL is OK, and it grab the ssl certificate, but on the Centos, it displays a yellow error, with the message "Service imaps on my_server is not OK : Unexpected service response", and of course don't see the certificate.
The only difference (except the system) is that I've compiled a RPM for the Centos system.

When I test imaps with openssl on both systems (openssl s_client -connect my_server:993 -ssl3) the result is * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready.

Could someone tell me what is the problem?

Best regards,

David AGBO

list Jeremy Laidman · Thu, 5 Apr 2012 09:08:15 +1000 ·

▸ quoted from David Agbo

On Thu, Apr 5, 2012 at 2:42 AM, David AGBO <user-b2c8d499b0a4@xymon.invalid> wrote:

I have installed Xymon 4.3.7 on Centos 5.8 x64. Before that, I have
installed it on a RHEL 5.6, everything worked fine until I tried to check an
imaps server. The Xymon on RHEL is OK, and it grab the ssl certificate, but
on the Centos, it displays a yellow error, with the message "Service imaps
on my_server is not OK : Unexpected service response", and of course don't

Can you try testing an https server and see if that behaves the same?
I suspect it's not IMAP-related and instead to do with linking against
SSL libraries at compile-time.  Perhaps run "ldd
$XYMONHOME/server/xymonnet" and see if there are difference between
the two servers.

Cheers
Jeremy

list David Agbo · Thu, 05 Apr 2012 11:03:52 +0200 ·

Thanks for your answer.
You're right, this is not IMAP-related, plus the test of HTTPS returns 
the following message :

Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Hint: https://my_server

Of course, that's what I'm trying...

So it can be a problem at compile-time, like I said, the only difference 
is this RPM. But everything seems to be OK in the SPEC file.
Here is the result of "ldd" :

On RHEL :

     linux-gate.so.1 =>  (0x00cc1000)
     libldap-2.3.so.0 => /usr/lib/libldap-2.3.so.0 (0x0014b000)
     liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x00110000)
     libssl.so.6 => /lib/libssl.so.6 (0x00185000)
     libcrypto.so.6 => /lib/libcrypto.so.6 (0x003d6000)
     libpcre.so.0 => /lib/libpcre.so.0 (0x00918000)
     librt.so.1 => /lib/librt.so.1 (0x00c51000)
     libc.so.6 => /lib/libc.so.6 (0x00a62000)
     libresolv.so.2 => /lib/libresolv.so.2 (0x00dc9000)
     libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0011e000)
     libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x001cd000)
     libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00247000)
     libcom_err.so.2 => /lib/libcom_err.so.2 (0x00cab000)
     libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x001fb000)
     libdl.so.2 => /lib/libdl.so.2 (0x00bbd000)
     libz.so.1 => /usr/lib/libz.so.1 (0x00341000)
     libpthread.so.0 => /lib/libpthread.so.0 (0x00a22000)
     /lib/ld-linux.so.2 (0x00a43000)
     libcrypt.so.1 => /lib/libcrypt.so.1 (0x00c77000)
     libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00cb5000)
     libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00df1000)
     libselinux.so.1 => /lib/libselinux.so.1 (0x00bc4000)
     libsepol.so.1 => /lib/libsepol.so.1 (0x00bde000)

On Centos x64 :

     linux-vdso.so.1 =>  (0x00007fff62199000)
     libldap-2.3.so.0 => /usr/lib64/libldap-2.3.so.0 (0x00000031cc400000)
     liblber-2.3.so.0 => /usr/lib64/liblber-2.3.so.0 (0x00000031cbc00000)
     libpcre.so.0 => /lib64/libpcre.so.0 (0x00000031cf800000)
     librt.so.1 => /lib64/librt.so.1 (0x00007f529dd66000)
     libc.so.6 => /lib64/libc.so.6 (0x00000031c9c00000)
     libresolv.so.2 => /lib64/libresolv.so.2 (0x00000031cd400000)
     libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00000031ca400000)
     libssl.so.6 => /lib64/libssl.so.6 (0x00000031cf000000)
     libcrypto.so.6 => /lib64/libcrypto.so.6 (0x00000031cc800000)
     libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f529db49000)
     /lib64/ld-linux-x86-64.so.2 (0x00000031c9800000)
     libdl.so.2 => /lib64/libdl.so.2 (0x00000031ca000000)
     libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00000031cb800000)
     libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 
(0x00000031cd000000)
     libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00000031cdc00000)
     libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00000031cd800000)
     libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00000031ce800000)
     libz.so.1 => /lib64/libz.so.1 (0x00000031cb400000)
     libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 
(0x00000031ce000000)
     libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00000031ce400000)
     libselinux.so.1 => /lib64/libselinux.so.1 (0x00000031cac00000)
     libsepol.so.1 => /lib64/libsepol.so.1 (0x00000031ca800000)

Best regards,
David

▸ quoted from Jeremy Laidman


Le 05/04/2012 01:08, Jeremy Laidman a écrit :

On Thu, Apr 5, 2012 at 2:42 AM, David AGBO<user-b2c8d499b0a4@xymon.invalid>  wrote:

I have installed Xymon 4.3.7 on Centos 5.8 x64. Before that, I have
installed it on a RHEL 5.6, everything worked fine until I tried to check an
imaps server. The Xymon on RHEL is OK, and it grab the ssl certificate, but
on the Centos, it displays a yellow error, with the message "Service imaps
on my_server is not OK : Unexpected service response", and of course don't

Can you try testing an https server and see if that behaves the same?
I suspect it's not IMAP-related and instead to do with linking against
SSL libraries at compile-time.  Perhaps run "ldd
$XYMONHOME/server/xymonnet" and see if there are difference between
the two servers.

Cheers
Jeremy

list David Agbo · Thu, 05 Apr 2012 11:49:12 +0200 ·

OK, it's really weird...
$XYMONHOME/server/xymonnet returns :

On RHEL :

xymonnet version 4.3.5
SSL library : OpenSSL 0.9.8e-rhel5 01 Jul 2008
LDAP library: OpenLDAP 20343

On Centos x64 :

xymonnet version 4.3.7
LDAP library: OpenLDAP 20343

But in the SPEC file I have :

[...]
%setup
     USEXYMONPING=n \
         ENABLESSL=y \
         ENABLELDAP=y \
         ENABLELDAPSSL=y \
         XYMONUSER=xymon \

▸ quoted from David Agbo

[...]

Le 05/04/2012 11:03, David AGBO a écrit :

Thanks for your answer.
You're right, this is not IMAP-related, plus the test of HTTPS returns 
the following message :

Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Hint: https://my_server

Of course, that's what I'm trying...

So it can be a problem at compile-time, like I said, the only 
difference is this RPM. But everything seems to be OK in the SPEC file.
Here is the result of "ldd" :

On RHEL :

    linux-gate.so.1 =>  (0x00cc1000)
    libldap-2.3.so.0 => /usr/lib/libldap-2.3.so.0 (0x0014b000)
    liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x00110000)
    libssl.so.6 => /lib/libssl.so.6 (0x00185000)
    libcrypto.so.6 => /lib/libcrypto.so.6 (0x003d6000)
    libpcre.so.0 => /lib/libpcre.so.0 (0x00918000)
    librt.so.1 => /lib/librt.so.1 (0x00c51000)
    libc.so.6 => /lib/libc.so.6 (0x00a62000)
    libresolv.so.2 => /lib/libresolv.so.2 (0x00dc9000)
    libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0011e000)
    libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x001cd000)
    libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00247000)
    libcom_err.so.2 => /lib/libcom_err.so.2 (0x00cab000)
    libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x001fb000)
    libdl.so.2 => /lib/libdl.so.2 (0x00bbd000)
    libz.so.1 => /usr/lib/libz.so.1 (0x00341000)
    libpthread.so.0 => /lib/libpthread.so.0 (0x00a22000)
    /lib/ld-linux.so.2 (0x00a43000)
    libcrypt.so.1 => /lib/libcrypt.so.1 (0x00c77000)
    libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00cb5000)
    libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00df1000)
    libselinux.so.1 => /lib/libselinux.so.1 (0x00bc4000)
    libsepol.so.1 => /lib/libsepol.so.1 (0x00bde000)

On Centos x64 :

    linux-vdso.so.1 =>  (0x00007fff62199000)
    libldap-2.3.so.0 => /usr/lib64/libldap-2.3.so.0 (0x00000031cc400000)
    liblber-2.3.so.0 => /usr/lib64/liblber-2.3.so.0 (0x00000031cbc00000)
    libpcre.so.0 => /lib64/libpcre.so.0 (0x00000031cf800000)
    librt.so.1 => /lib64/librt.so.1 (0x00007f529dd66000)
    libc.so.6 => /lib64/libc.so.6 (0x00000031c9c00000)
    libresolv.so.2 => /lib64/libresolv.so.2 (0x00000031cd400000)
    libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00000031ca400000)
    libssl.so.6 => /lib64/libssl.so.6 (0x00000031cf000000)
    libcrypto.so.6 => /lib64/libcrypto.so.6 (0x00000031cc800000)
    libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f529db49000)
    /lib64/ld-linux-x86-64.so.2 (0x00000031c9800000)
    libdl.so.2 => /lib64/libdl.so.2 (0x00000031ca000000)
    libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00000031cb800000)
    libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 
(0x00000031cd000000)
    libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00000031cdc00000)
    libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00000031cd800000)
    libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00000031ce800000)
    libz.so.1 => /lib64/libz.so.1 (0x00000031cb400000)
    libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 
(0x00000031ce000000)
    libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00000031ce400000)
    libselinux.so.1 => /lib64/libselinux.so.1 (0x00000031cac00000)
    libsepol.so.1 => /lib64/libsepol.so.1 (0x00000031ca800000)

Best regards,
David

Le 05/04/2012 01:08, Jeremy Laidman a écrit :

On Thu, Apr 5, 2012 at 2:42 AM, David AGBO<user-b2c8d499b0a4@xymon.invalid>  wrote:

I have installed Xymon 4.3.7 on Centos 5.8 x64. Before that, I have
installed it on a RHEL 5.6, everything worked fine until I tried to check an
imaps server. The Xymon on RHEL is OK, and it grab the ssl certificate, but
on the Centos, it displays a yellow error, with the message "Service imaps
on my_server is not OK : Unexpected service response", and of course don't

Can you try testing an https server and see if that behaves the same?
I suspect it's not IMAP-related and instead to do with linking against
SSL libraries at compile-time.  Perhaps run "ldd
$XYMONHOME/server/xymonnet" and see if there are difference between
the two servers.

Cheers
Jeremy

list Henrik Størner · Thu, 05 Apr 2012 11:53:31 +0200 ·

▸ quoted from David Agbo

On 05-04-2012 11:49, David AGBO wrote:

OK, it's really weird...
$XYMONHOME/server/xymonnet returns :

On RHEL :

xymonnet version 4.3.5
SSL library : OpenSSL 0.9.8e-rhel5 01 Jul 2008
LDAP library: OpenLDAP 20343

On Centos x64 :

xymonnet version 4.3.7
LDAP library: OpenLDAP 20343

But in the SPEC file I have :

[...]
%setup
USEXYMONPING=n \
ENABLESSL=y \
ENABLELDAP=y \
ENABLELDAPSSL=y \
XYMONUSER=xymon \
[...]

Regardless of your spec-file, if you don't have the openssl development 
package installed, the configure script will disable SSL support.

You should see a warning in the xymonnet logfile that SSL tests will not 
work: "SSL test, but xymonnet was built without SSL support"


Regards,
Henrik

list Paul Root · Thu, 5 Apr 2012 07:03:59 -0500 ·

You'll need openssl-devel installed on CentOS.

Paul Root    - Senior Engineer
Managed Services Systems - CenturyLink

▸ quoted from David Agbo



From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of David AGBO
Sent: Thursday, April 05, 2012 4:49 AM
To: Jeremy Laidman
Cc: xymon at xymon.com
Subject: Re: [Xymon] [Xymon 4.3.7] bad imaps check

OK, it's really weird...
$XYMONHOME/server/xymonnet returns :

On RHEL :

xymonnet version 4.3.5
SSL library : OpenSSL 0.9.8e-rhel5 01 Jul 2008
LDAP library: OpenLDAP 20343

On Centos x64 :

xymonnet version 4.3.7
LDAP library: OpenLDAP 20343

But in the SPEC file I have :

[...]
%setup
    USEXYMONPING=n \
        ENABLESSL=y \
        ENABLELDAP=y \
        ENABLELDAPSSL=y \
        XYMONUSER=xymon \
[...]

Le 05/04/2012 11:03, David AGBO a écrit :
Thanks for your answer.
You're right, this is not IMAP-related, plus the test of HTTPS returns the following message :

Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Hint: https://my_server

Of course, that's what I'm trying...

So it can be a problem at compile-time, like I said, the only difference is this RPM. But everything seems to be OK in the SPEC file.
Here is the result of "ldd" :

On RHEL :

    linux-gate.so.1 =>  (0x00cc1000)
    libldap-2.3.so.0 => /usr/lib/libldap-2.3.so.0 (0x0014b000)
    liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x00110000)
    libssl.so.6 => /lib/libssl.so.6 (0x00185000)
    libcrypto.so.6 => /lib/libcrypto.so.6 (0x003d6000)
    libpcre.so.0 => /lib/libpcre.so.0 (0x00918000)
    librt.so.1 => /lib/librt.so.1 (0x00c51000)
    libc.so.6 => /lib/libc.so.6 (0x00a62000)
    libresolv.so.2 => /lib/libresolv.so.2 (0x00dc9000)
    libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0011e000)
    libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x001cd000)
    libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00247000)
    libcom_err.so.2 => /lib/libcom_err.so.2 (0x00cab000)
    libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x001fb000)
    libdl.so.2 => /lib/libdl.so.2 (0x00bbd000)
    libz.so.1 => /usr/lib/libz.so.1 (0x00341000)
    libpthread.so.0 => /lib/libpthread.so.0 (0x00a22000)
    /lib/ld-linux.so.2 (0x00a43000)
    libcrypt.so.1 => /lib/libcrypt.so.1 (0x00c77000)
    libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00cb5000)
    libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00df1000)
    libselinux.so.1 => /lib/libselinux.so.1 (0x00bc4000)
    libsepol.so.1 => /lib/libsepol.so.1 (0x00bde000)

On Centos x64 :

    linux-vdso.so.1 =>  (0x00007fff62199000)
    libldap-2.3.so.0 => /usr/lib64/libldap-2.3.so.0 (0x00000031cc400000)
    liblber-2.3.so.0 => /usr/lib64/liblber-2.3.so.0 (0x00000031cbc00000)
    libpcre.so.0 => /lib64/libpcre.so.0 (0x00000031cf800000)
    librt.so.1 => /lib64/librt.so.1 (0x00007f529dd66000)
    libc.so.6 => /lib64/libc.so.6 (0x00000031c9c00000)
    libresolv.so.2 => /lib64/libresolv.so.2 (0x00000031cd400000)
    libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00000031ca400000)
    libssl.so.6 => /lib64/libssl.so.6 (0x00000031cf000000)
    libcrypto.so.6 => /lib64/libcrypto.so.6 (0x00000031cc800000)
    libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f529db49000)
    /lib64/ld-linux-x86-64.so.2 (0x00000031c9800000)
    libdl.so.2 => /lib64/libdl.so.2 (0x00000031ca000000)
    libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00000031cb800000)
    libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00000031cd000000)
    libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00000031cdc00000)
    libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00000031cd800000)
    libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00000031ce800000)
    libz.so.1 => /lib64/libz.so.1 (0x00000031cb400000)
    libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00000031ce000000)
    libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00000031ce400000)
    libselinux.so.1 => /lib64/libselinux.so.1 (0x00000031cac00000)
    libsepol.so.1 => /lib64/libsepol.so.1 (0x00000031ca800000)

Best regards,
David

Le 05/04/2012 01:08, Jeremy Laidman a écrit :

On Thu, Apr 5, 2012 at 2:42 AM, David AGBO <user-b2c8d499b0a4@xymon.invalid><mailto:user-b2c8d499b0a4@xymon.invalid> wrote:


I have installed Xymon 4.3.7 on Centos 5.8 x64. Before that, I have

installed it on a RHEL 5.6, everything worked fine until I tried to check an

imaps server. The Xymon on RHEL is OK, and it grab the ssl certificate, but

on the Centos, it displays a yellow error, with the message "Service imaps

on my_server is not OK : Unexpected service response", and of course don't

Can you try testing an https server and see if that behaves the same?

I suspect it's not IMAP-related and instead to do with linking against

SSL libraries at compile-time.  Perhaps run "ldd

$XYMONHOME/server/xymonnet" and see if there are difference between

the two servers.


Cheers

Jeremy


This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.

list David Agbo · Thu, 05 Apr 2012 14:48:20 +0200 ·

Exactly, that's what it comes to, Jeremy helped me to get the picture. I 
thought that I had installed it...
I will re-compile my RPM.
Thanks to both of you.

Best regards,
David

▸ quoted from Paul Root


Le 05/04/2012 14:03, Root, Paul a écrit :

You'll need openssl-devel installed on CentOS.

Paul Root    - Senior Engineer

Managed Services Systems - CenturyLink


*From:*xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] *On

▸ quoted from Paul Root

Behalf Of *David AGBO
*Sent:* Thursday, April 05, 2012 4:49 AM
*To:* Jeremy Laidman
*Cc:* xymon at xymon.com
*Subject:* Re: [Xymon] [Xymon 4.3.7] bad imaps check

OK, it's really weird...


$XYMONHOME/server/xymonnet --version returns :

▸ quoted from Paul Root


On RHEL :

xymonnet version 4.3.5
SSL library : OpenSSL 0.9.8e-rhel5 01 Jul 2008
LDAP library: OpenLDAP 20343

On Centos x64 :

xymonnet version 4.3.7
LDAP library: OpenLDAP 20343

But in the SPEC file I have :

[...]
%setup
    USEXYMONPING=n \
        ENABLESSL=y \
        ENABLELDAP=y \
        ENABLELDAPSSL=y \
        XYMONUSER=xymon \
[...]

Le 05/04/2012 11:03, David AGBO a écrit :

Thanks for your answer.
You're right, this is not IMAP-related, plus the test of HTTPS returns 
the following message :

Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Hint: https://my_server

Of course, that's what I'm trying...

So it can be a problem at compile-time, like I said, the only 
difference is this RPM. But everything seems to be OK in the SPEC file.
Here is the result of "ldd" :

On RHEL :

    linux-gate.so.1 =>  (0x00cc1000)
    libldap-2.3.so.0 => /usr/lib/libldap-2.3.so.0 (0x0014b000)
    liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x00110000)
    libssl.so.6 => /lib/libssl.so.6 (0x00185000)
    libcrypto.so.6 => /lib/libcrypto.so.6 (0x003d6000)
    libpcre.so.0 => /lib/libpcre.so.0 (0x00918000)
    librt.so.1 => /lib/librt.so.1 (0x00c51000)
    libc.so.6 => /lib/libc.so.6 (0x00a62000)
    libresolv.so.2 => /lib/libresolv.so.2 (0x00dc9000)
    libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0011e000)
    libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x001cd000)
    libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00247000)
    libcom_err.so.2 => /lib/libcom_err.so.2 (0x00cab000)
    libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x001fb000)
    libdl.so.2 => /lib/libdl.so.2 (0x00bbd000)
    libz.so.1 => /usr/lib/libz.so.1 (0x00341000)
    libpthread.so.0 => /lib/libpthread.so.0 (0x00a22000)
    /lib/ld-linux.so.2 (0x00a43000)
    libcrypt.so.1 => /lib/libcrypt.so.1 (0x00c77000)
    libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00cb5000)
    libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00df1000)
    libselinux.so.1 => /lib/libselinux.so.1 (0x00bc4000)
    libsepol.so.1 => /lib/libsepol.so.1 (0x00bde000)

On Centos x64 :

    linux-vdso.so.1 =>  (0x00007fff62199000)
    libldap-2.3.so.0 => /usr/lib64/libldap-2.3.so.0 (0x00000031cc400000)
    liblber-2.3.so.0 => /usr/lib64/liblber-2.3.so.0 (0x00000031cbc00000)
    libpcre.so.0 => /lib64/libpcre.so.0 (0x00000031cf800000)
    librt.so.1 => /lib64/librt.so.1 (0x00007f529dd66000)
    libc.so.6 => /lib64/libc.so.6 (0x00000031c9c00000)
    libresolv.so.2 => /lib64/libresolv.so.2 (0x00000031cd400000)
    libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00000031ca400000)
    libssl.so.6 => /lib64/libssl.so.6 (0x00000031cf000000)
    libcrypto.so.6 => /lib64/libcrypto.so.6 (0x00000031cc800000)
    libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f529db49000)
    /lib64/ld-linux-x86-64.so.2 (0x00000031c9800000)
    libdl.so.2 => /lib64/libdl.so.2 (0x00000031ca000000)
    libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00000031cb800000)
    libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 
(0x00000031cd000000)
    libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00000031cdc00000)
    libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00000031cd800000)
    libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00000031ce800000)
    libz.so.1 => /lib64/libz.so.1 (0x00000031cb400000)
    libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 
(0x00000031ce000000)
    libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00000031ce400000)
    libselinux.so.1 => /lib64/libselinux.so.1 (0x00000031cac00000)
    libsepol.so.1 => /lib64/libsepol.so.1 (0x00000031ca800000)

Best regards,
David

Le 05/04/2012 01:08, Jeremy Laidman a écrit :

On Thu, Apr 5, 2012 at 2:42 AM, David AGBO<user-b2c8d499b0a4@xymon.invalid>  <mailto:user-b2c8d499b0a4@xymon.invalid>  wrote:
  

    I have installed Xymon 4.3.7 on Centos 5.8 x64. Before that, I have

    installed it on a RHEL 5.6, everything worked fine until I tried to check an

    imaps server. The Xymon on RHEL is OK, and it grab the ssl certificate, but

    on the Centos, it displays a yellow error, with the message "Service imaps

    on my_server is not OK : Unexpected service response", and of course don't

Can you try testing an https server and see if that behaves the same?
I suspect it's not IMAP-related and instead to do with linking against
SSL libraries at compile-time.  Perhaps run "ldd
$XYMONHOME/server/xymonnet" and see if there are difference between
the two servers.
  
Cheers
Jeremy

This communication is the property of CenturyLink and may contain 
confidential or privileged information. Unauthorized use of this 
communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.

[Xymon 4.3.7] bad imaps check 🔗 link

[Xymon 4.3.7] bad imaps check