<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body>
OK, it's really weird...<br>
$XYMONHOME/server/xymonnet returns :<br>
<br>
On RHEL :<br>
<br>
xymonnet version 4.3.5<br>
SSL library : OpenSSL 0.9.8e-rhel5 01 Jul 2008<br>
LDAP library: OpenLDAP 20343<br>
<br>
On Centos x64 :<br>
<br>
xymonnet version 4.3.7<br>
LDAP library: OpenLDAP 20343<br>
<br>
But in the SPEC file I have :<br>
<br>
[...]<br>
%setup<br>
USEXYMONPING=n \<br>
ENABLESSL=y \<br>
ENABLELDAP=y \<br>
ENABLELDAPSSL=y \<br>
XYMONUSER=xymon \<br>
[...]<br>
<br>
Le 05/04/2012 11:03, David AGBO a écrit :
<blockquote class=" cite" id="mid_4F7D5FF8_50103_kernix_com"
cite="mid:4F7D5FF8.50103@kernix.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Thanks for your answer.<br>
You're right, this is not IMAP-related, plus the test of HTTPS
returns the following message :<br>
<br>
Bad Request<br>
<br>
Your browser sent a request that this server could not understand.<br>
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br>
Instead use the HTTPS scheme to access this URL, please.<br>
<br>
Hint: <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://my_server">https://my_server</a><br>
<br>
Of course, that's what I'm trying...<br>
<br>
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.<br>
Here is the result of "ldd" :<br>
<br>
On RHEL :<br>
<br>
linux-gate.so.1 => (0x00cc1000)<br>
libldap-2.3.so.0 => /usr/lib/libldap-2.3.so.0 (0x0014b000)<br>
liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x00110000)<br>
libssl.so.6 => /lib/libssl.so.6 (0x00185000)<br>
libcrypto.so.6 => /lib/libcrypto.so.6 (0x003d6000)<br>
libpcre.so.0 => /lib/libpcre.so.0 (0x00918000)<br>
librt.so.1 => /lib/librt.so.1 (0x00c51000)<br>
libc.so.6 => /lib/libc.so.6 (0x00a62000)<br>
libresolv.so.2 => /lib/libresolv.so.2 (0x00dc9000)<br>
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0011e000)<br>
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2
(0x001cd000)<br>
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00247000)<br>
libcom_err.so.2 => /lib/libcom_err.so.2 (0x00cab000)<br>
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x001fb000)<br>
libdl.so.2 => /lib/libdl.so.2 (0x00bbd000)<br>
libz.so.1 => /usr/lib/libz.so.1 (0x00341000)<br>
libpthread.so.0 => /lib/libpthread.so.0 (0x00a22000)<br>
/lib/ld-linux.so.2 (0x00a43000)<br>
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00c77000)<br>
libkrb5support.so.0 => /usr/lib/libkrb5support.so.0
(0x00cb5000)<br>
libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00df1000)<br>
libselinux.so.1 => /lib/libselinux.so.1 (0x00bc4000)<br>
libsepol.so.1 => /lib/libsepol.so.1 (0x00bde000)<br>
<br>
On Centos x64 :<br>
<br>
linux-vdso.so.1 => (0x00007fff62199000)<br>
libldap-2.3.so.0 => /usr/lib64/libldap-2.3.so.0
(0x00000031cc400000)<br>
liblber-2.3.so.0 => /usr/lib64/liblber-2.3.so.0
(0x00000031cbc00000)<br>
libpcre.so.0 => /lib64/libpcre.so.0 (0x00000031cf800000)<br>
librt.so.1 => /lib64/librt.so.1 (0x00007f529dd66000)<br>
libc.so.6 => /lib64/libc.so.6 (0x00000031c9c00000)<br>
libresolv.so.2 => /lib64/libresolv.so.2
(0x00000031cd400000)<br>
libsasl2.so.2 => /usr/lib64/libsasl2.so.2
(0x00000031ca400000)<br>
libssl.so.6 => /lib64/libssl.so.6 (0x00000031cf000000)<br>
libcrypto.so.6 => /lib64/libcrypto.so.6
(0x00000031cc800000)<br>
libpthread.so.0 => /lib64/libpthread.so.0
(0x00007f529db49000)<br>
/lib64/ld-linux-x86-64.so.2 (0x00000031c9800000)<br>
libdl.so.2 => /lib64/libdl.so.2 (0x00000031ca000000)<br>
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00000031cb800000)<br>
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2
(0x00000031cd000000)<br>
libkrb5.so.3 => /usr/lib64/libkrb5.so.3
(0x00000031cdc00000)<br>
libcom_err.so.2 => /lib64/libcom_err.so.2
(0x00000031cd800000)<br>
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3
(0x00000031ce800000)<br>
libz.so.1 => /lib64/libz.so.1 (0x00000031cb400000)<br>
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0
(0x00000031ce000000)<br>
libkeyutils.so.1 => /lib64/libkeyutils.so.1
(0x00000031ce400000)<br>
libselinux.so.1 => /lib64/libselinux.so.1
(0x00000031cac00000)<br>
libsepol.so.1 => /lib64/libsepol.so.1 (0x00000031ca800000)<br>
<br>
Best regards,<br>
David<br>
<br>
Le 05/04/2012 01:08, Jeremy Laidman a écrit :
<blockquote class=" cite"
id="mid_CAAnki7CFn1qUGuSrJ7Mda6J7_BHuqUeec2nJJ8hqkrSgZW0cxQ_mail_gmail_com"
cite="mid:CAAnki7CFn1qUGuSrJ7Mda6J7_BHuqUeec2nJJ8hqkrSgZW0cxQ@mail.gmail.com"
type="cite">
<pre wrap="">On Thu, Apr 5, 2012 at 2:42 AM, David AGBO <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:dagbo@kernix.com"><dagbo@kernix.com></a> wrote:
</pre>
<blockquote class=" cite" id="Cite_0" type="cite">
<pre wrap="">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
</pre>
</blockquote>
<pre wrap="">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
</pre>
</blockquote>
</blockquote>
</body>
</html>