ZMTrigger , Shared data size conflict in shared_data

Forum for questions and support relating to the 1.30.x releases only.
Locked
Sigge
Posts: 116
Joined: Mon May 02, 2016 8:14 am

ZMTrigger , Shared data size conflict in shared_data

Post by Sigge »

Eh, what does this mean?

I do not know any differences between monitor 8 and 9. 9 works but 8 does not.

/var/log/zm$ tail -f zm_debug.log.8062
04/01/2018 20:00:02.063786 zmtrigger[8062].DBG [Found monitor for id '9']
04/01/2018 20:00:02.063860 zmtrigger[8062].DBG [Handling action 'show']
04/01/2018 20:00:02.063930 zmtrigger[8062].INF [Updated show text to '11.1 C ']
04/01/2018 20:00:02.064985 zmtrigger[8062].DBG [Got input from 1 connections]
04/01/2018 20:00:02.065041 zmtrigger[8062].DBG [Got input from spawned connection Chan1 TCP on port 6802 (14)]
04/01/2018 20:00:02.065086 zmtrigger[8062].DBG [Removed spawned connection (14), 1 spawned connections]
04/01/2018 20:01:18.045461 zmtrigger[8062].DBG [Loading monitors]
04/01/2018 20:02:27.507382 zmtrigger[8062].DBG [Shared data size conflict in shared_data for monitor Monitor-8, expected 336, got 0]
04/01/2018 20:02:27.507760 zmtrigger[8062].DBG [Loading monitors]
04/01/2018 20:02:27.508563 zmtrigger[8062].DBG [Shared data size conflict in shared_data for monitor Monitor-8, expected 336, got 0]
Sigge
Posts: 116
Joined: Mon May 02, 2016 8:14 am

Re: ZMTrigger , Shared data size conflict in shared_data

Post by Sigge »

'zmc -m 8' crashed, signal 8

might be the problem?
Sigge
Posts: 116
Joined: Mon May 02, 2016 8:14 am

SOLVED ZMTrigger , Shared data size conflict in shared_data

Post by Sigge »

Ok, simple restart seems to have rectified this problem...
Locked