IVS client prompting the 'Login Timeout due to network exception or server unstarted' error

This post refers to an IVS client prompting the 'Login Timeout due to network exception or server unstarted' error. Please find the way to solve this issue below.

Issue description

In the case of the NVR6128 server, the cmc service is running (as per below). But when logging in via the client, it prompts the 'Login Timeout due to network exception or server unstarted' error. The customer said they had changed the IP address on the NVR management page. After that, the problem still arised.

Alarm information

When logging in via the client, it prompts the 'Login Timeout due to network exception or server unstarted' error.

Handling process

1. Tried to confirm if there is a network problem. Ping the NVR service IP from the client PC. The response is normal.
   

2. Tried to confirm if the service IP is configured correctly. Query the IP information on the NVR manage page; the result is as follows. It means the server IP is configured correctly, however the service IP in the config file is right.

   

3. Checked the SRU log file. There’s the following information, which means the service is still using the old IP address as service IP:

   ErrorNumber is 1. and ErrorMessage is:DoPostSync error!;[exception]org.apache.http.conn.HttpHostConnectException: Connection to http://192.168.1.55:8800 refused

4. Checked nvrmanage.log. We can’t find any proof that the IP address has been changed on the NVR management page. If it has, there should be the information like: 

   doBondIP()result: Begin execute DoBondIP command . bondName->bond0, NICMaster->eth0, NICSlave->eth1, bondIP->192.168.1.55, bondMask255.255.255.0, gateway192.168.1.254 (Logger.java, line 24)

5. Based on the above proof, we can confirm that the IP address has been changed on suse OS, not on the NVR management page. Such operation can only change the server IP, but the service IP in the config file will not be changed. So, the problem arised.

6. Re-config the IP on the NVR management page. The problem is fixed.

Root causes

1. Maybe there is a network problem between the client and the NVR6128 server.

2. The service IP is not configured correctly.