Problem with distributed system: Unexpected state, could not set msg version

[frankySie]

hello,
a distributed system was setup. the system 13 and 14 are located within a test network which is connected with openvpn.
What is the problem with "Unexpected state, could not set msg version" ?

The system-overview-panel shows a yellow state for system 13 and 14. What does the yellow color mean?



(...copy/paste from log file...)

WCCILdist (1), 2013.01.14 08:44:59.507, SYS, INFO, 4, Connected to, (SYS: 13 Dist -num 1 CONN: 1) @ 172.24.17.13 (172.24.17.13)
WCCILdist (1), 2013.01.14 08:44:59.523, SYS, INFO, 4, Connected to, (SYS: 14 Dist -num 1 CONN: 1) @ 172.24.17.14 (172.24.17.14)
WCCILdist (1), 2013.01.14 08:45:01.913, IMPL, SEVERE, 54, Unexpected state, could not set msg version for the connection to "(SYS: 2 Dist -num 1 CONN: 1)". peer not found! at:3395 file:MsgItcDispatcher.cxx
WCCILdist (1), 2013.01.14 08:45:04.195, REDU, INFO, 3/dist, Closing connection to passiv peer MAN: (SYS: 13 Dist -num 1 CONN: 1)
WCCILdist (1), 2013.01.14 08:45:04.195, SYS, INFO, 181, Closing connection to (SYS: 13 Dist -num 1 CONN: 1)
WCCILdist (1), 2013.01.14 08:45:06.492, IMPL, SEVERE, 54, Unexpected state, could not set msg version for the connection to "(SYS: 2 Dist -num 1 CONN: 1)". peer not found! at:3395 file:MsgItcDispatcher.cxx
WCCILdist (1), 2013.01.14 08:45:08.773, REDU, INFO, 3/dist, Closing connection to passiv peer MAN: (SYS: 14 Dist -num 1 CONN: 1)
WCCILdist (1), 2013.01.14 08:45:08.773, SYS, INFO, 181, Closing connection to (SYS: 14 Dist -num 1 CONN: 1)
WCCILdist (1), 2013.01.14 08:45:08.773, SYS, WARNING, 39, Connection lost, MAN: (SYS: 13 Dist -num 1 CONN: 1), Connection reset by peer (10054)
WCCILdist (1), 2013.01.14 08:45:08.789, SYS, WARNING, 39, Connection lost, MAN: (SYS: 14 Dist -num 1 CONN: 1), Connection reset by peer (10054)


It might be a configuration problem, because the systems 23 and 24 are connected successfull. As well system 23 and 24 are located behind the openvpn link.

[leoknipp]

Hello,

the "yellow" color indicates that the system is trying to establish/initialize the connection to the distributed system.

To be able to find the cause for the problem we need additional information.
Maybe the configuration of the distributed system is not correct (different language settings, wrong dist-settings at the config-file, ...) and therefore the error occurs.

If the problem still occurs please refer to the official support and open a new service request.
How to open a service request is described at the following links:

portal.etm.at/index.php?view=items&c...ickfaq&Itemid=54

portal.etm.at/index.php?view=items&c...ickfaq&Itemid=54


Please notice that the ETM Portal does not substitute the common WinCC OA support.

Best Regards
Leopold Knipp
Senior Support Specialist

[frankySie]

well, after some investigation in that problem
a solution was found.
But it could be a workaround more than a solution.

At (my) linux PC when WinCC-OA is stopped then a lock manager still is running in the background.

>>ps -ef|grep lm_ip
>>root 11337 1 0 09:26 ? 00:00:00 /opt/WinCC_OA/3.11/bin/lm_ip -a lockmgr -f 600


This lock manager has to be killed (manually) first.
Then I configure the WinCC-OA project which was copied to this Linux PC:

>>./WCCOAtoolSyncTypes -system -proj

The project is started and now it connects successfull to the other system.
The connection status becomes green.

Feel free to correct my answer if you think it is improper.

[leoknipp]

Hello,

the lock-manager lm_ip is a tool for the RAIMA-database (WinCC OA database) and is not related to a specific project.
This process is also not related to any distributed system functionality of WinCC OA.

Restarting the lm_ip-process should not be the solution for a problem with a distributed system.

Best Regards
Leopold Knipp
Senior Support Specialist