Hi,
I installed version 1.2.7 and setup LDAP synchronization. Approximately one week everything was OK. Now I can't connect to the server as AD user nor admin (nxmc). I restarted the server and I could connect to the server again but only for 30-60 minutes. There was no error in log file netxms.
I setup debug 4. When I connect to the server as AD user, in netxms log is
...
[12-Jun-2015 11:00:07.973] [DEBUG] LDAPConnection::initLDAP(): Connecting to LDAP server
[12-Jun-2015 11:00:07.976] [DEBUG] LDAPConnection::closeLDAPConnection(): Disconnect form ldap.
[12-Jun-2015 11:00:07.978] [DEBUG] [CLSN-0] User <user> authenticated (language=en clientInfo="nxmc/1.2.17 (Windows 7 6.1; libnxcl 1.2.17)")
...
When I couldn't connect to the server, these rows are missing and nxmc writes
Request timed out
server: CentOS 7.1, MariaDB
Thank you very much
Ladislav
Hi,
1.2.17 has few known LDAP bugs that was fixed in 2.0. I'm not sure though if that's one of those known bugs. If you can try 2.0-M4 (or wait for 2.0-M5 which will be available next week) it will be great.
Also, is is possible that LDAP server do not respond to requests from NetXMS server? This can be the reason of timeout on client connect.
Best regards,
Victor
Hi,
LDAP server is OK. I'll wait for version 2.0-M5
Thanks
Ladislav
Hi,
I updated server to version 2.0-M5 (clean installation with new db) but it didn't help.
I setup debug 6 and I tried to login as admin. In the log
[DEBUG] [CLSN-6] Received message CMD_GET_SERVER_INFO
[DEBUG] [CLSN-6] Server time zone: CET+02CEST
[DEBUG] [CLSN-6] Sending message CMD_REQUEST_COMPLETE
[DEBUG] [CLSN-6] Received message CMD_REQUEST_ENCRYPT
[DEBUG] [CLSN-6] Sending message CMD_REQUEST_SESSION_
[DEBUG] [CLSN-6] Received message CMD_SESSION_KEY
[DEBUG] [CLSN-6] Sending message CMD_REQUEST_COMPLETE
[DEBUG] [CLSN-6] Received message CMD_LOGIN
[DEBUG] [CLSN-6] authentication type 0
.
.
[DEBUG] [CLSN-5] readThread: message receiving error
(MSGRECV_COMM_FAILURE)
[DEBUG] [CLSN-6] readThread: message receiving error
(MSGRECV_COMM_FAILURE)
When I restarted the server, I could connect without any problem. It means, the problem is persistent.
Thanks,
Ladislav