Contivity 1740 [V05_00.303] : Remote host not responding

[François]

Hi everybody,
My contivity has been refused any connection yesterday and I want to know why. The Internet line was up, there was no errors on switch ports but no responses. I looked in logs and I restarted the interface but the only solution who has resolved the problem was a reboot.
I just want to know if events below may cause this dysfunction and if you have already sow this issue.

*01:48:18 tEvtLgMgr 0 : Security [13] c_check_ca_root: user de-select server cert
*01:48:18 tEvtLgMgr 0 : Sys [13] HTTPD: httpOsalTcp.c:  httpsSSLLoadCert: no server cert selected
*01:49:02 tEvtLgMgr 0 : Security [13] c_check_ca_root: user de-select server cert
*01:49:02 tEvtLgMgr 0 : Sys [13] HTTPD: httpOsalTcp.c:  httpsSSLLoadCert: no server cert selected
*16:17:01 tEvtLgMgr 0 : Sys [13] HTTPD: dispatcher got an error from some RPM

Thanks in advance,

[Telair]

It's been a long time since I dabbled in v5 code for the Contivities, but I recall I had some issues with services stopping at times for no good reason.  I didn't use certificates like you, but I had issues with the interface staying up but the service to handle the VPN tunnel would stop working a few times a year.  Once I upgraded to v6.05.xx software all those problems went away for me.  v5 is very very old now, you might want to look to update to at least late v6 code to be supportable. 

[Michael McNamara]

I'm currently running my NVR 1740s at V07_05.531 and all three of them are very stable. I would suggest that you check the expiration of the certificate but if a reboot resolved the problem then that's not the issue.

Good Luck!

[François]

Thanks guys for your advices,

I think that I will upgrade the software. Anyway, I have no different choice because this hardware are not supported anymore  !
But, I agree with you Micheal, in 6 years, my coworker told me It was the first time that it has a bad working.

I try to obtain a new soft by my supplier but I think it is free now, no ?

See you later,

[François]

Hi all,

I updated my software the last week and it's appear that the problem was fixed.
I'm now in V08_05.450.

Thanks for your advices again,

François.