weixin_39720181
weixin_39720181
2020-12-02 19:42

Not receiving event notifications after upgrading zmeventnotification.pl to 1.2

I have updated zmeventnotification.pl to 1.2 but now I am not getting any notifications. I have tried with different monitor combinations but with the same result. These logs are with one monitor in “modect”, the rest are in Monitor. When an event happens I get the Shared data size conflict error. This happens with all the monitors. I never got this error when I was using 1.1

Thanks for the help,

Here are the logs.

Date/Time Component Server PID Level Message File Line 2018-09-30 08:29:03 zmeventnotification 20350 INF Storing token ...iJOerwXlrS,monlist:1,5,6,7,8,intlist:0,0,0,0,0,pushstate:enabled zmeventnotification.pl
2018-09-30 08:29:03 zmeventnotification 20350 INF SaveTokens called with:monlist=1,5,6,7,8, intlist=0,0,0,0,0, platform=ios, push=enabled zmeventnotification.pl
2018-09-30 08:29:03 zmeventnotification 20350 INF token fdg4ExZ6jl0:APA91bHMvABosdBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHIvDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS matched, previously stored monlist is: 1,5,6,7,8 zmeventnotification.pl
2018-09-30 08:29:03 zmeventnotification 20350 INF overwriting fdg4ExZ6jl0:APA91bHMvABosdBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHIvDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS monlist with:1,5,6,7,8 zmeventnotification.pl
2018-09-30 08:29:02 zmeventnotification 20350 INF got a websocket connection from ::ffff:98.174.63.232 (1) active connections zmeventnotification.pl
2018-09-30 08:29:02 zmeventnotification 20350 INF Websockets: New Connection Handshake requested from ::ffff:98.174.63.232:50537 state=pending auth zmeventnotification.pl
2018-09-30 08:29:02 zmeventnotification 20350 INF Correct authentication provided by ::ffff:98.174.63.232 zmeventnotification.pl
2018-09-30 08:29:02 zmeventnotification 20350 INF Duplicate token found, removing old data point zmeventnotification.pl
2018-09-30 08:26:16 zmeventnotification 20350 INF Total event client connections: 1 zmeventnotification.pl
2018-09-30 08:26:16 zmeventnotification 20350 INF Loading monitors zmeventnotification.pl
2018-09-30 08:26:16 zmeventnotification 20350 INF Reloading Monitors... zmeventnotification.pl
2018-09-30 08:26:11 zmeventnotification 20350 ERR Shared data size conflict in shared_data for monitor 192.168.1.22, expected 608, got 875967096 zmeventnotification.pl
2018-09-30 08:24:06 zmeventnotification 20350 INF Secure WS(WSS) is enabled... zmeventnotification.pl
2018-09-30 08:24:06 zmeventnotification 20350 INF About to start listening to socket zmeventnotification.pl
2018-09-30 08:24:06 zmeventnotification 20350 INF Loading monitors zmeventnotification.pl
2018-09-30 08:24:06 zmeventnotification 20350 INF Reloading Monitors... zmeventnotification.pl
2018-09-30 08:24:06 zmeventnotification 20350 INF Web Socket Event Server listening on port 9000 zmeventnotification.pl
2018-09-30 08:24:05 zmeventnotification 20350 INF using config file: /etc/zmeventnotification.ini zmeventnotification.pl
2018-09-30 08:24:05 zmeventnotification 20350 INF Push enabled via FCM zmeventnotification.pl
2018-09-30 08:24:05 zmeventnotification 20350 INF Event Notification daemon v 1.2 starting zmeventnotification.pl
2018-09-30 08:24:05 zmeventnotification 20350 INF Total event client connections: 1 zmeventnotification.pl

zmNinja version:1.3.017 (ios) ZoneMinder version:1.32.0

Sep 30, 2018 08:29:03 AM DEBUG EventCtrl:loading one more page just in case we don't have enough to display Sep 30, 2018 08:29:03 AM DEBUG EventCtrl: success, got 31 events Sep 30, 2018 08:29:03 AM DEBUG removing settings-temp-data worked Sep 30, 2018 08:29:03 AM DEBUG removing settings-temp-data worked Sep 30, 2018 08:29:03 AM DEBUG removing settings-temp-data worked Sep 30, 2018 08:29:03 AM DEBUG EventCtrl: grabbing events for: id=0 Date/Time:- Sep 30, 2018 08:29:03 AM DEBUG EventCtrl: found 10 pages of events Sep 30, 2018 08:29:03 AM DEBUG {"results":{"1":"9","5":"1","6":"4","7":"1","8":"15"}} Sep 30, 2018 08:29:03 AM DEBUG {"results":{"1":"618","2":"86","3":"22","5":"28","6":"29","7":"101","8":"47"}} Sep 30, 2018 08:29:03 AM DEBUG {"results":{"6":"2"}} Sep 30, 2018 08:29:03 AM DEBUG {"results":{"1":"149","5":"22","6":"28","7":"71","8":"45"}} Sep 30, 2018 08:29:03 AM DEBUG saving defaultServerName worked Sep 30, 2018 08:29:03 AM DEBUG Real-time event: {"type":"","version":"1.2","reason":"","status":"Success","event":"auth"} Sep 30, 2018 08:29:03 AM DEBUG saving defaultServerName worked Sep 30, 2018 08:29:03 AM DEBUG openHandShake: state of push is enabled Sep 30, 2018 08:29:03 AM INFO openHandshake: Websocket open, sending Auth Sep 30, 2018 08:29:03 AM INFO Inside openHandshake Sep 30, 2018 08:29:03 AM DEBUG saving defaultServerName worked Sep 30, 2018 08:29:03 AM DEBUG consoleEvents API:https:///api/events/consoleEvents/1%20month/AlarmFrames >=:1.json Sep 30, 2018 08:29:03 AM DEBUG consoleEvents API:https:///api/events/consoleEvents/1%20week/AlarmFrames >=:1.json Sep 30, 2018 08:29:03 AM DEBUG consoleEvents API:https:///api/events/consoleEvents/1%20day/AlarmFrames >=:1.json Sep 30, 2018 08:29:03 AM DEBUG consoleEvents API:https:///api/events/consoleEvents/1%20hour/AlarmFrames >=:1.json Sep 30, 2018 08:29:03 AM DEBUG Setting up carousel watchers Sep 30, 2018 08:29:03 AM DEBUG EventCtrl: grabbing # of event pages Sep 30, 2018 08:29:03 AM DEBUG getInitialEvents called Sep 30, 2018 08:29:03 AM DEBUG saving serverGroupList worked Sep 30, 2018 08:29:02 AM DEBUG saving serverGroupList worked Sep 30, 2018 08:29:02 AM DEBUG enabling options swipe Sep 30, 2018 08:29:02 AM DEBUG text zoom factor is 1 Sep 30, 2018 08:29:02 AM INFO ZM_EVENT_IMAGE_DIGITS is 5 Sep 30, 2018 08:29:02 AM INFO Image padding digits reported as 5 Sep 30, 2018 08:29:02 AM DEBUG Portal: Deregistering broadcast handles Sep 30, 2018 08:29:02 AM INFO ZM_EVENT_IMAGE_DIGITS is already configured for 5 Sep 30, 2018 08:29:02 AM DEBUG >>>height of list/scrub set to 330 and 370 Sep 30, 2018 08:29:02 AM DEBUG --> thumbnail means increasing row size Sep 30, 2018 08:29:02 AM INFO EventCtrl called with: E/MID=0 playEvent = false Sep 30, 2018 08:29:02 AM INFO Returning pre-loaded list of 5 monitors Sep 30, 2018 08:29:02 AM DEBUG saving serverGroupList worked Sep 30, 2018 08:29:02 AM DEBUG Transitioning state to: app.events with param {"id":"0","playEvent":"false"} Sep 30, 2018 08:29:02 AM DEBUG Setting up websocket error handler Sep 30, 2018 08:29:02 AM DEBUG Removing error handlers for websocket Sep 30, 2018 08:29:02 AM INFO Initializing Websocket with URL wss:// Sep 30, 2018 08:29:02 AM DEBUG Config URL for digits is:https:///api/configs/viewByName/ZM_EVENT_IMAGE_DIGITS.json Sep 30, 2018 08:29:02 AM INFO Got API version: 1.32.0 Sep 30, 2018 08:29:02 AM DEBUG Setting server version to:1.32.0 Sep 30, 2018 08:29:02 AM DEBUG getAPIversion called Sep 30, 2018 08:29:02 AM DEBUG PortalLogin: auth success Sep 30, 2018 08:29:02 AM DEBUG Storing login time as Sun Sep 30 2018 08:29:02 GMT-0500 Sep 30, 2018 08:29:02 AM DEBUG auth-success broadcast:Successful Sep 30, 2018 08:29:02 AM INFO zmAutologin successfully logged into Zoneminder via API Sep 30, 2018 08:29:02 AM INFO Stream authentication construction: &auth=9562524ffc69444cfc818867da6c4042 Sep 30, 2018 08:29:02 AM DEBUG Setting server version to:1.32.0 Sep 30, 2018 08:29:02 AM DEBUG API based login returned... Sep 30, 2018 08:29:02 AM INFO zmAutologin called Sep 30, 2018 08:29:02 AM DEBUG Resetting zmCookie... Sep 30, 2018 08:29:02 AM DEBUG Logout returned... Sep 30, 2018 08:29:02 AM DEBUG Logging out using API method Sep 30, 2018 08:29:02 AM INFO https://=>Logging out of any existing ZM sessions... Sep 30, 2018 08:29:02 AM INFO Cancelling zmAutologin timer Sep 30, 2018 08:29:02 AM DEBUG PIN code entered is correct, or there is no PIN set Sep 30, 2018 08:29:02 AM DEBUG unlock called with check PIN=true Sep 30, 2018 08:29:02 AM INFO not checking for touchID Sep 30, 2018 08:29:02 AM INFO User credentials are provided Sep 30, 2018 08:29:02 AM DEBUG Inside Portal login Enter handler Sep 30, 2018 08:29:01 AM DEBUG EventCtrl: Deregistering broadcast handles Sep 30, 2018 08:29:01 AM DEBUG EventCtrl: Deregistering resize listener Sep 30, 2018 08:29:01 AM INFO Entering Portal Main Sep 30, 2018 08:29:01 AM DEBUG going to portal login Sep 30, 2018 08:29:01 AM DEBUG Last State recorded:{"viewId":"ion17","index":0,"historyId":"ion6","backViewId":null,"forwardViewId":null,"stateId":"app.events_id=0_playEvent=false","stateName":"app.events","stateParams":{"id":"0","playEvent":"false"},"url":"/app/events/0/false","canSwipeBack":true} Sep 30, 2018 08:29:01 AM INFO App is resuming from background Sep 30, 2018 08:13:45 AM DEBUG EventCtrl Pause:Deregistering broadcast handles Sep 30, 2018 08:13:45 AM DEBUG EventCtrl:onpause called Sep 30, 2018 08:13:45 AM DEBUG Montage View Cleanup was already done, skipping Sep 30, 2018 08:13:45 AM DEBUG MontageCtrl: onpause called Sep 30, 2018 08:13:45 AM INFO Cancelling zmAutologin timer Sep 30, 2018 08:13:45 AM INFO Clearing error/close cbk, disconnecting and deleting Event Server socket... Sep 30, 2018 08:13:45 AM INFO ROOT APP:App is going into background Sep 30, 2018 08:13:41 AM DEBUG EventCtrl:loading one more page just in case we don't have enough to display Sep 30, 2018 08:13:41 AM DEBUG EventCtrl: success, got 29 events Sep 30, 2018 08:13:41 AM DEBUG EventCtrl: grabbing events for: id=0 Date/Time:- Sep 30, 2018 08:13:41 AM DEBUG EventCtrl: found 10 pages of events Sep 30, 2018 08:13:41 AM DEBUG {"results":{"1":"149","5":"22","6":"26","7":"71","8":"45"}} Sep 30, 2018 08:13:41 AM DEBUG {"results":[]} Sep 30, 2018 08:13:41 AM DEBUG {"results":{"1":"618","2":"86","3":"22","5":"28","6":"27","7":"101","8":"47"}} Sep 30, 2018 08:13:41 AM DEBUG {"results":{"1":"9","5":"1","6":"2","7":"1","8":"15"}} Sep 30, 2018 08:13:41 AM DEBUG consoleEvents API:https:///api/events/consoleEvents/1%20month/AlarmFrames >=:1.json Sep 30, 2018 08:13:41 AM DEBUG consoleEvents API:https:///api/events/consoleEvents/1%20week/AlarmFrames >=:1.json Sep 30, 2018 08:13:41 AM DEBUG consoleEvents API:https:///api/events/consoleEvents/1%20day/AlarmFrames >=:1.json Sep 30, 2018 08:13:41 AM DEBUG consoleEvents API:https:///api/events/consoleEvents/1%20hour/AlarmFrames >=:1.json Sep 30, 2018 08:13:41 AM DEBUG Setting up carousel watchers Sep 30, 2018 08:13:41 AM DEBUG EventCtrl: grabbing # of event pages Sep 30, 2018 08:13:41 AM DEBUG getInitialEvents called Sep 30, 2018 08:13:41 AM DEBUG enabling options swipe Sep 30, 2018 08:13:40 AM DEBUG text zoom factor is 1 Sep 30, 2018 08:13:40 AM INFO Image padding digits reported as 5 Sep 30, 2018 08:13:40 AM INFO ZM_EVENT_IMAGE_DIGITS is already configured for 5 Sep 30, 2018 08:13:40 AM DEBUG >>>height of list/scrub set to 330 and 370 Sep 30, 2018 08:13:40 AM DEBUG --> thumbnail means increasing row size Sep 30, 2018 08:13:40 AM INFO EventCtrl called with: E/MID=0 playEvent = false Sep 30, 2018 08:13:40 AM INFO Returning pre-loaded list of 5 monitors Sep 30, 2018 08:13:40 AM INFO Returning pre-loaded list of 5 monitors Sep 30, 2018 08:12:27 AM DEBUG doing the jiggle and dance... Sep 30, 2018 08:12:27 AM DEBUG All images loaded, doing image layout Sep 30, 2018 08:12:27 AM INFO Arranging as per packery grid Sep 30, 2018 08:12:27 AM DEBUG All images loaded, switching to snapshot... Sep 30, 2018 08:12:27 AM INFO Monitors that are active and not DOM hidden: 5 while grid has 5 Sep 30, 2018 08:12:27 AM INFO found a packery layout Sep 30, 2018 08:12:27 AM DEBUG removing settings-temp-data worked Sep 30, 2018 08:12:27 AM DEBUG removing settings-temp-data worked Sep 30, 2018 08:12:27 AM DEBUG removing settings-temp-data worked Sep 30, 2018 08:12:26 AM DEBUG saving defaultServerName worked Sep 30, 2018 08:12:26 AM DEBUG saving defaultServerName worked Sep 30, 2018 08:12:26 AM DEBUG saving defaultServerName worked Sep 30, 2018 08:12:26 AM DEBUG Real-time event: {"type":"","status":"Success","event":"auth","reason":"","version":"1.2"} Sep 30, 2018 08:12:26 AM DEBUG saving serverGroupList worked Sep 30, 2018 08:12:26 AM INFO Inside Montage Ctrl:We found 5 monitors Sep 30, 2018 08:12:26 AM DEBUG skipping image refresh, packery is still loading Sep 30, 2018 08:12:26 AM DEBUG Setting up cycle interval of:10000 Sep 30, 2018 08:12:26 AM DEBUG bandwidth: highbw montage refresh set to: 2 Sep 30, 2018 08:12:26 AM DEBUG openHandShake: state of push is enabled Sep 30, 2018 08:12:26 AM INFO openHandshake: Websocket open, sending Auth Sep 30, 2018 08:12:26 AM INFO Inside openHandshake Sep 30, 2018 08:12:26 AM DEBUG Forcing simulStreams off as you have disabled it Sep 30, 2018 08:12:26 AM DEBUG Multiport=0 Sep 30, 2018 08:12:26 AM DEBUG Portal: Deregistering broadcast handles Sep 30, 2018 08:12:26 AM INFO sending Cached ZM_MIN_STREAMING_PORT 0 Sep 30, 2018 08:12:26 AM DEBUG Loading hidden/unhidden status for profile: Sep 30, 2018 08:12:26 AM INFO multi server list loaded{"servers":[]} Sep 30, 2018 08:12:26 AM DEBUG loading saved monitor list and interval of 1,5,6,7,8>>0,0,0,0,0 Sep 30, 2018 08:12:26 AM DEBUG Loading hidden/unhidden status for profile: Sep 30, 2018 08:12:26 AM INFO multi server list loaded{"servers":[]} Sep 30, 2018 08:12:26 AM INFO Monitor load was successful, loaded 5 monitors Sep 30, 2018 08:12:26 AM DEBUG Now trying to get multi-server data, if present Sep 30, 2018 08:12:26 AM DEBUG Inside getMonitors, will also regen connkeys Sep 30, 2018 08:12:26 AM DEBUG Loading hidden/unhidden status for profile: Sep 30, 2018 08:12:26 AM INFO Monitor load was successful, loaded 5 monitors Sep 30, 2018 08:12:26 AM DEBUG Now trying to get multi-server data, if present Sep 30, 2018 08:12:26 AM DEBUG Inside getMonitors, will also regen connkeys Sep 30, 2018 08:12:26 AM DEBUG Loading hidden/unhidden status for profile: Sep 30, 2018 08:12:25 AM DEBUG saving serverGroupList worked Sep 30, 2018 08:12:25 AM DEBUG Monitor URL to fetch is:https:///api/monitors/index/Type !=:WebSite.json Sep 30, 2018 08:12:25 AM DEBUG ZMS Multiport reported: 0 Sep 30, 2018 08:12:25 AM INFO ZM_MIN_STREAMING_PORT not configure, disabling Sep 30, 2018 08:12:25 AM DEBUG Setting multi-port to:false Sep 30, 2018 08:12:25 AM DEBUG Monitor URL to fetch is:https:///api/monitors/index/Type !=:WebSite.json Sep 30, 2018 08:12:25 AM DEBUG ZMS Multiport reported: 0 Sep 30, 2018 08:12:25 AM INFO ZM_MIN_STREAMING_PORT not configure, disabling Sep 30, 2018 08:12:25 AM DEBUG Setting multi-port to:false Sep 30, 2018 08:12:25 AM DEBUG Timezone API response is:America/Chicago Sep 30, 2018 08:12:25 AM INFO ZM_EVENT_IMAGE_DIGITS is 5 Sep 30, 2018 08:12:25 AM INFO Checking value of ZM_MIN_STREAMING_PORT for the first time Sep 30, 2018 08:12:25 AM INFO getMonitors:Loading all monitors Sep 30, 2018 08:12:25 AM DEBUG Push Notification registration ID received: {"registrationId":"fdg4ExZ6jl0:APA91bHMvABosdBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHIvDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS","registrationType":"FCM"} Sep 30, 2018 08:12:25 AM DEBUG saving serverGroupList worked Sep 30, 2018 08:12:25 AM INFO Checking value of ZM_MIN_STREAMING_PORT for the first time Sep 30, 2018 08:12:25 AM INFO getMonitors:Loading all monitors Sep 30, 2018 08:12:25 AM DEBUG DataModel: Regenerating connkeys... Sep 30, 2018 08:12:25 AM DEBUG Transitioning state to: app.montage with param undefined Sep 30, 2018 08:12:25 AM DEBUG Setting up websocket error handler Sep 30, 2018 08:12:25 AM DEBUG Removing error handlers for websocket Sep 30, 2018 08:12:25 AM INFO Initializing Websocket with URL wss:// Sep 30, 2018 08:12:25 AM INFO >>>Setting up push registration Sep 30, 2018 08:12:25 AM INFO First invocation of TimeZone, asking server Sep 30, 2018 08:12:25 AM DEBUG Config URL for digits is:https:///api/configs/viewByName/ZM_EVENT_IMAGE_DIGITS.json Sep 30, 2018 08:12:25 AM INFO Got API version: 1.32.0 Sep 30, 2018 08:12:25 AM DEBUG Setting server version to:1.32.0 Sep 30, 2018 08:12:25 AM DEBUG getAPIversion called Sep 30, 2018 08:12:25 AM DEBUG PortalLogin: auth success Sep 30, 2018 08:12:25 AM DEBUG Storing login time as Sun Sep 30 2018 08:12:25 GMT-0500 Sep 30, 2018 08:12:25 AM DEBUG auth-success broadcast:Successful Sep 30, 2018 08:12:25 AM INFO zmAutologin successfully logged into Zoneminder via API Sep 30, 2018 08:12:25 AM INFO Stream authentication construction: &auth=9562524ffc69444cfc818867da6c4042 Sep 30, 2018 08:12:25 AM DEBUG Setting server version to:1.32.0 Sep 30, 2018 08:12:25 AM DEBUG API based login returned... Sep 30, 2018 08:12:25 AM INFO zmAutologin called Sep 30, 2018 08:12:25 AM DEBUG Resetting zmCookie... Sep 30, 2018 08:12:25 AM DEBUG Logout returned... Sep 30, 2018 08:12:24 AM DEBUG Logging out using API method Sep 30, 2018 08:12:24 AM INFO https://=>Logging out of any existing ZM sessions... Sep 30, 2018 08:12:24 AM INFO Cancelling zmAutologin timer Sep 30, 2018 08:12:24 AM DEBUG PIN code entered is correct, or there is no PIN set Sep 30, 2018 08:12:24 AM DEBUG unlock called with check PIN=true Sep 30, 2018 08:12:24 AM INFO not checking for touchID Sep 30, 2018 08:12:24 AM INFO User credentials are provided Sep 30, 2018 08:12:24 AM DEBUG Inside Portal login Enter handler Sep 30, 2018 08:12:24 AM DEBUG Latest post dated 2018-09-25 15:25:13 but you read 2018-09-25 15:25:13 Sep 30, 2018 08:12:24 AM DEBUG current version: 1.3.017 & available version 1.3.018 Sep 30, 2018 08:12:24 AM INFO Entering Portal Main Sep 30, 2018 08:12:23 AM INFO Inside init-complete in app.js: All init over, going to portal login Sep 30, 2018 08:12:23 AM INFO >>>> Disabling strict SSL checking (turn off in Dev Options if you can't connect) Sep 30, 2018 08:12:23 AM INFO DataModel init retrieved store loginData Sep 30, 2018 08:12:23 AM INFO SlowDelay is: false Sep 30, 2018 08:12:23 AM INFO Setting DataModel init bandwidth to: highbw Sep 30, 2018 08:12:23 AM DEBUG timeline graph type not set. Setting to all Sep 30, 2018 08:12:23 AM INFO user profile encrypted, decoding... Sep 30, 2018 08:12:23 AM INFO Setting up pause and resume handler AFTER language is loaded... Sep 30, 2018 08:12:23 AM INFO Setting up POST LOGIN timer Sep 30, 2018 08:12:23 AM INFO Checking for news updates Sep 30, 2018 08:12:23 AM INFO Checking for new version updates... Sep 30, 2018 08:12:23 AM INFO ZMData init: checking for stored variables & setting up log file Sep 30, 2018 08:12:23 AM INFO Language file loaded, continuing with rest Sep 30, 2018 08:12:23 AM DEBUG isFirstUse returned: false Sep 30, 2018 08:12:23 AM INFO >>>>Language to be used:en Sep 30, 2018 08:12:23 AM INFO Device Language is:en Sep 30, 2018 08:12:23 AM INFO No language set, switching to en Sep 30, 2018 08:12:23 AM INFO App Version: 1.3.017 Sep 30, 2018 08:12:23 AM INFO Retrieving language before init is called... Sep 30, 2018 08:12:23 AM INFO Enabling native transitions... Sep 30, 2018 08:12:23 AM INFO Updating statusbar Sep 30, 2018 08:12:23 AM INFO >>>>No data to import.... Sep 30, 2018 08:12:23 AM INFO localforage driver for storage:cordovaSQLiteDriver Sep 30, 2018 08:12:23 AM DEBUG configureStorageDB:test get/set worked, this driver is ok... Sep 30, 2018 08:12:23 AM DEBUG text zoom factor is 1 Sep 30, 2018 08:12:23 AM DEBUG configureStorageDB:Making sure this storage driver works... Sep 30, 2018 08:12:23 AM INFO configureStorageDB:localforage driver for storage:cordovaSQLiteDriver Sep 30, 2018 08:12:23 AM DEBUG configureStorageDB: trying order:["cordovaSQLiteDriver","asyncStorage","localStorageWrapper"] Sep 30, 2018 08:12:23 AM DEBUG Inside configureStorageDB Sep 30, 2018 08:12:23 AM INFO You are running on ios Sep 30, 2018 08:12:23 AM INFO Device is ready Sep 29, 2018 07:51:43 PM DEBUG State results: {"data":{"states":[{"State":{"Id":"1","Name":"default","Definition":"","IsActive":"0"}},{"State":{"Id":"8","Name":"Monitor","Definition":"1:Monitor:1,5:Monitor:1,6:Monitor:1,7:Monitor:1,8:Monitor:1","IsActive":"1"}},{"State":{"Id":"9","Name":"Mocord","Definition":"1:Mocord:1,5:Mocord:1,6:Mocord:1,7:Mocord:1,8:Mocord:1","IsActive":"0"}},{"State":{"Id":"10","Name":"Nighttime","Definition":"1:Modect:1,5:Modect:1,6:Modect:1,7:Modect:1,8:Modect:1","IsActive":"0"}},{"State":{"Id":"12","Name":"Away","Definition":"1:Modect:1,5:Modect:1,6:Modect:1,7:Modect:1,8:Modect:1","IsActive":"0"}}]},"status":200,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"url":"https:///api/States.json","headers":{"Accept":"application/json, text/plain, /"}},"statusText":"OK"} Sep 29, 2018 07:51:43 PM DEBUG StateCtrl: getting state using https:///api/States.json Sep 29, 2018 07:51:42 PM DEBUG StateCtrl/controlZM: returned success Sep 29, 2018 07:51:30 PM INFO Websocket closed Sep 29, 2018 07:51:27 PM DEBUG StateCtrl/controlZM: POST Control command is https:///api/states/change/Monitor.json Sep 29, 2018 07:51:27 PM DEBUG inside performZMoperation with Monitor Sep 29, 2018 07:51:20 PM INFO List of custom states: ["default","Monitor","Mocord","Nighttime","Away"] Sep 29, 2018 07:51:13 PM DEBUG State results: {"data":{"states":[{"State":{"Id":"1","Name":"default","Definition":"","IsActive":"0"}},{"State":{"Id":"8","Name":"Monitor","Definition":"1:Monitor:1,5:Monitor:1,6:Monitor:1,7:Monitor:1,8:Monitor:1","IsActive":"0"}},{"State":{"Id":"9","Name":"Mocord","Definition":"1:Mocord:1,5:Mocord:1,6:Mocord:1,7:Mocord:1,8:Mocord:1","IsActive":"0"}},{"State":{"Id":"10","Name":"Nighttime","Definition":"1:Modect:1,5:Modect:1,6:Modect:1,7:Modect:1,8:Modect:1","IsActive":"0"}},{"State":{"Id":"12","Name":"Away","Definition":"1:Modect:1,5:Modect:1,6:Modect:1,7:Modect:1,8:Modect:1","IsActive":"1"}}]},"status":200,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"url":"https:///api/States.json","headers":{"Accept":"application/json, text/plain, /"}},"statusText":"OK"} Sep 29, 2018 07:51:13 PM DEBUG StateCtrl: getting state using https:///api/States.json Sep 29, 2018 07:51:13 PM DEBUG invoking CurrentState... Sep 29, 2018 07:51:11 PM DEBUG StateCtrl/getLoadStatus: success Sep 29, 2018 07:51:11 PM DEBUG Load results: {"data":{"load":[0.63,0.61,0.57]},"status":200,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"url":"https:///api/host/getLoad.json","headers":{"Accept":"application/json, text/plain, /"},"timeout":30000},"statusText":"OK"} Sep 29, 2018 07:51:11 PM DEBUG StateCtrl/getLoadStatus: https:///api/host/getLoad.json Sep 29, 2018 07:51:11 PM DEBUG invoking LoadStatus... Sep 29, 2018 07:51:10 PM DEBUG Run results: {"data":{"result":1},"status":200,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"url":"https:///api/host/daemonCheck.json","headers":{"Accept":"application/json, text/plain, /"},"timeout":30000},"statusText":

该提问来源于开源项目:pliablepixels/zmeventnotification

  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 复制链接分享
  • 邀请回答

17条回答

  • weixin_39893205 weixin_39893205 5月前

    Yes the Video Writer is set to X264 encode.

    Yeah, so it looks like you are experiencing this issue, which has been fixed: https://github.com/ZoneMinder/zoneminder/issues/2184

    点赞 评论 复制链接分享
  • weixin_39720181 weixin_39720181 5月前

    That was it. Notifications working great now. Thanks!

    点赞 评论 复制链接分享
  • weixin_39639643 weixin_39639643 5月前

    Great. Thanks for the help Andy.

    点赞 评论 复制链接分享
  • weixin_39639643 weixin_39639643 5月前

    Hi, please do this

    1. Stop event server by doing sudo zmdc.pl stop zmeventnotification.pl
    2. Download version 1.3 (just updated it)
    3. Restart ZoneMinder
    4. Edit your zmeventserver.ini file and change verbose to 1
    5. Run the notification server manually by doing sudo -u www-data ./zmeventnotification.pl (or -u apache depending on which distro you are running on)

    If you did everything right, you'll see logs on the screen directly

    Generate alarms and please post the logs. I only need zmeventnotification logs. Thx

    点赞 评论 复制链接分享
  • weixin_39720181 weixin_39720181 5月前

    Here you go. Thanks

    sudo -u www-data ./zmeventnotification.pl 09/30/2018 10:06:14.080782 zmeventnotification[23413].INF [main:241] [using conf ig file: /etc/zmeventnotification.ini]

    Configuration (read /etc/zmeventnotification.ini):

    Port .......................... 9000 Address ....................... [::] Event check interval .......... 5 Monitor reload interval ....... 300

    Auth enabled .................. true Auth timeout .................. 20

    Use FCM ....................... true FCM API key ................... (defined) Token file .................... /etc/private/tokens.txt

    Use MQTT .......................false MQTT Server ....................127.0.0.1 MQTT Username ..................(undefined) MQTT Password ..................(undefined)

    SSL enabled ................... true SSL cert file ................. /etc/apache2/ssl/zoneminder.crt SSL key file .................. /etc/apache2/ssl/zoneminder.key

    Verbose ....................... true Read alarm cause .............. false Tag alarm event id ............ false Use custom notification sound . false

    09/30/2018 10:06:14.211349 zmeventnotification[23413].INF [main:375] [Push enabl ed via FCM] 2018-09-30,10:06:14 **You are running version: 1.3 09/30/2018 10:06:14.261099 zmeventnotification[23413].INF [main:455] [Event Noti fication daemon v 1.3 starting] 2018-09-30,10:06:14 Calling uniq from loadTokens 09/30/2018 10:06:14.308875 zmeventnotification[23413].INF [main:491] [Total even t client connections: 1] 2018-09-30,10:06:14 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 10:06:14.407803 zmeventnotification[23413].INF [main:505] [Reloading Monitors...] 09/30/2018 10:06:14.457844 zmeventnotification[23413].INF [main:589] [Loading mo nitors] 09/30/2018 10:06:14.510767 zmeventnotification[23413].INF [main:1450] [About to start listening to socket] 09/30/2018 10:06:14.591421 zmeventnotification[23413].INF [main:1468] [Secure WS (WSS) is enabled...] 09/30/2018 10:06:14.658819 zmeventnotification[23413].INF [main:1474] [Web Socke t Event Server listening on port 9000] 2018-09-30,10:06:19 Active connects after INVALID_AUTH purge=1 2018-09-30,10:06:19 Active connects after INVALID_APNS purge=1 2018-09-30,10:06:24 Active connects after INVALID_AUTH purge=1 2018-09-30,10:06:24 Active connects after INVALID_APNS purge=1 2018-09-30,10:06:29 Active connects after INVALID_AUTH purge=1 2018-09-30,10:06:29 Active connects after INVALID_APNS purge=1 2018-09-30,10:06:34 Active connects after INVALID_AUTH purge=1 2018-09-30,10:06:34 Active connects after INVALID_APNS purge=1 2018-09-30,10:06:39 Active connects after INVALID_AUTH purge=1 2018-09-30,10:06:39 Active connects after INVALID_APNS purge=1 09/30/2018 10:06:39.713146 zmeventnotification[23413].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.22, expected 608, got 875967096] 09/30/2018 10:06:39.762077 zmeventnotification[23413].INF [main:525] [ Memory verify failed for 192.168.1.22(id:6) so forcing reload] 2018-09-30,10:06:44 Active connects after INVALID_AUTH purge=1 2018-09-30,10:06:44 Active connects after INVALID_APNS purge=1 09/30/2018 10:06:44.714325 zmeventnotification[23413].INF [main:491] [Total even t client connections: 1] 2018-09-30,10:06:44 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 10:06:44.758412 zmeventnotification[23413].INF [main:505] [Reloading Monitors...] 09/30/2018 10:06:44.804317 zmeventnotification[23413].INF [main:589] [Loading mo nitors] 09/30/2018 10:06:44.843741 zmeventnotification[23413].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096] 2018-09-30,10:06:49 Active connects after INVALID_AUTH purge=1 2018-09-30,10:06:49 Active connects after INVALID_APNS purge=1 09/30/2018 10:06:49.713157 zmeventnotification[23413].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096] 09/30/2018 10:06:49.823726 zmeventnotification[23413].INF [main:525] [ Memory verify failed for Kitchen(id:1) so forcing reload] 2018-09-30,10:06:54 Active connects after INVALID_AUTH purge=1 2018-09-30,10:06:54 Active connects after INVALID_APNS purge=1 09/30/2018 10:06:54.714217 zmeventnotification[23413].INF [main:491] [Total even t client connections: 1] 2018-09-30,10:06:54 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 10:06:54.892771 zmeventnotification[23413].INF [main:505] [Reloading Monitors...] 09/30/2018 10:06:54.946256 zmeventnotification[23413].INF [main:589] [Loading mo nitors] 09/30/2018 10:06:54.994321 zmeventnotification[23413].ERR [ZoneMinder::Memory::M apped:95] [Memory map file '/dev/shm/zm.mmap.7' should have been 1168 but was in stead 0] no memkey in zmMemInvalidate 2018-09-30,10:06:59 Active connects after INVALID_AUTH purge=1 2018-09-30,10:06:59 Active connects after INVALID_APNS purge=1 2018-09-30,10:07:04 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:04 Active connects after INVALID_APNS purge=1 09/30/2018 10:07:04.714703 zmeventnotification[23413].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096] 09/30/2018 10:07:04.812545 zmeventnotification[23413].INF [main:525] [ Memory verify failed for Kitchen(id:1) so forcing reload] 2018-09-30,10:07:09 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:09 Active connects after INVALID_APNS purge=1 09/30/2018 10:07:09.714043 zmeventnotification[23413].INF [main:491] [Total even t client connections: 1] 2018-09-30,10:07:09 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 10:07:09.820362 zmeventnotification[23413].INF [main:505] [Reloading Monitors...] 09/30/2018 10:07:09.910766 zmeventnotification[23413].INF [main:589] [Loading mo nitors] 09/30/2018 10:07:09.958321 zmeventnotification[23413].ERR [ZoneMinder::Memory::M apped:95] [Memory map file '/dev/shm/zm.mmap.1' should have been 1168 but was in stead 0] no memkey in zmMemInvalidate 2018-09-30,10:07:14 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:14 Active connects after INVALID_APNS purge=1 2018-09-30,10:07:19 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:19 Active connects after INVALID_APNS purge=1 2018-09-30,10:07:24 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:24 Active connects after INVALID_APNS purge=1 2018-09-30,10:07:29 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:29 Active connects after INVALID_APNS purge=1 2018-09-30,10:07:34 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:34 Active connects after INVALID_APNS purge=1 09/30/2018 10:07:34.714545 zmeventnotification[23413].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096] 09/30/2018 10:07:34.831756 zmeventnotification[23413].INF [main:525] [** Memory verify failed for 192.168.1.21(id:7) so forcing reload] 2018-09-30,10:07:39 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:39 Active connects after INVALID_APNS purge=1 09/30/2018 10:07:39.714128 zmeventnotification[23413].INF [main:491] [Total even t client connections: 1] 2018-09-30,10:07:39 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 10:07:39.896068 zmeventnotification[23413].INF [main:505] [Reloading Monitors...] 09/30/2018 10:07:40.039981 zmeventnotification[23413].INF [main:589] [Loading mo nitors] 09/30/2018 10:07:40.198779 zmeventnotification[23413].ERR [ZoneMinder::Memory::M apped:95] [Memory map file '/dev/shm/zm.mmap.7' should have been 1168 but was in stead 0] no memkey in zmMemInvalidate 2018-09-30,10:07:44 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:44 Active connects after INVALID_APNS purge=1 2018-09-30,10:07:49 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:49 Active connects after INVALID_APNS purge=1 2018-09-30,10:07:54 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:54 Active connects after INVALID_APNS purge=1 2018-09-30,10:07:59 Active connects after INVALID_AUTH purge=1 2018-09-30,10:07:59 Active connects after INVALID_APNS purge=1 2018-09-30,10:08:04 Active connects after INVALID_AUTH purge=1 2018-09-30,10:08:04 Active connects after INVALID_APNS purge=1 2018-09-30,10:08:09 Active connects after INVALID_AUTH purge=1 2018-09-30,10:08:09 Active connects after INVALID_APNS purge=1 2018-09-30,10:08:14 Active connects after INVALID_AUTH purge=1 2018-09-30,10:08:14 Active connects after INVALID_APNS purge=1 2018-09-30,10:08:19 Active connects after INVALID_AUTH purge=1 2018-09-30,10:08:19 Active connects after INVALID_APNS purge=1 2018-09-30,10:08:24 Active connects after INVALID_AUTH purge=1 2018-09-30,10:08:24 Active connects after INVALID_APNS purge=1 2018-09-30,10:08:29 Active connects after INVALID_AUTH purge=1 2018-09-30,10:08:29 Active connects after INVALID_APNS purge=1 2018-09-30,10:08:34 Active connects after INVALID_AUTH purge=1 2018-09-30,10:08:34 Active connects after INVALID_APNS purge=1 2018-09-30,10:08:39 Active connects after INVALID_AUTH purge=1

    点赞 评论 复制链接分享
  • weixin_39639643 weixin_39639643 5月前

    Okay, so the core issue is that for some reason your ZM 1.32 seems to be have shared memory issues for some monitors. This doesn't seem to be an issue with the script but an issue with ZM.

    The difference between the old version and the new version is that in the new version, I am doing a zmMemVerify before I do a zmMemRead like this recent ZM PR does. If memory verification fails, I skip to the next monitor. In your situation, it seems the old version without this PR was sending out alarms for monitors where zmMemVerify failed, but zmMemRead succeeded, which is odd.

    -of-ni, is facing shared memory issues with 1.32. The patch doesn't resolve the shared memory issue by reloading monitors, so I suspect the problem is deeper in ZM. Do you agree? is there any reduced test case you'd like to see?

    The core logs:

    
    09/30/2018 10:06:39.713146 zmeventnotification[23413].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.22, expected 608, got 875967096]
    09/30/2018 10:06:39.762077 zmeventnotification[23413].INF [main:525] [ Memory verify failed for 192.168.1.22(id:6) so forcing reload]
    
    
    09/30/2018 10:06:44.758412 zmeventnotification[23413].INF [main:505] [Reloading Monitors...]
    09/30/2018 10:06:44.804317 zmeventnotification[23413].INF [main:589] [Loading mo nitors]
    09/30/2018 10:06:44.843741 zmeventnotification[23413].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096]
    2018-09-30,10:06:49 Active connects after INVALID_AUTH purge=1
    2018-09-30,10:06:49 Active connects after INVALID_APNS purge=1
    09/30/2018 10:06:49.713157 zmeventnotification[23413].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096]
    09/30/2018 10:06:49.823726 zmeventnotification[23413].INF [main:525] [ Memory verify failed for Kitchen(id:1) so forcing reload]
    
    09/30/2018 10:06:54.892771 zmeventnotification[23413].INF [main:505] [Reloading Monitors...]
    09/30/2018 10:06:54.946256 zmeventnotification[23413].INF [main:589] [Loading mo nitors]
    09/30/2018 10:06:54.994321 zmeventnotification[23413].ERR [ZoneMinder::Memory::M apped:95] [Memory map file '/dev/shm/zm.mmap.7' should have been 1168 but was in stead 0]
    no memkey in zmMemInvalidate
    
    09/30/2018 10:07:04.714703 zmeventnotification[23413].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096]
    09/30/2018 10:07:04.812545 zmeventnotification[23413].INF [main:525] [ Memory verify failed for Kitchen(id:1) so forcing reload]
    
    09/30/2018 10:07:09.820362 zmeventnotification[23413].INF [main:505] [Reloading Monitors...]
    09/30/2018 10:07:09.910766 zmeventnotification[23413].INF [main:589] [Loading mo nitors]
    09/30/2018 10:07:09.958321 zmeventnotification[23413].ERR [ZoneMinder::Memory::M apped:95] [Memory map file '/dev/shm/zm.mmap.1' should have been 1168 but was in stead 0]
    no memkey in zmMemInvalidate
    
    点赞 评论 复制链接分享
  • weixin_39893205 weixin_39893205 5月前

    Those errors look exactly like the ones we just fixed in zmtrigger. Suggest modeling zmeventnotification's mmap'ing routine against zmtrigger in the latest zm master branch.

    点赞 评论 复制链接分享
  • weixin_39639643 weixin_39639643 5月前

    Ah, indeed, I missed changing loadMonitors(). can you repeat the test with 1.4?

    点赞 评论 复制链接分享
  • weixin_39720181 weixin_39720181 5月前

    Configuration (read /etc/zmeventnotification.ini):

    Port .......................... 9000 Address ....................... [::] Event check interval .......... 5 Monitor reload interval ....... 300

    Auth enabled .................. true Auth timeout .................. 20

    Use FCM ....................... true FCM API key ................... (defined) Token file .................... /etc/private/tokens.txt

    Use MQTT .......................false MQTT Server ....................127.0.0.1 MQTT Username ..................(undefined) MQTT Password ..................(undefined)

    SSL enabled ................... true SSL cert file ................. /etc/apache2/ssl/zoneminder.crt SSL key file .................. /etc/apache2/ssl/zoneminder.key

    Verbose ....................... true Read alarm cause .............. false Tag alarm event id ............ false Use custom notification sound . false

    09/30/2018 12:14:15.142038 zmeventnotification[26791].INF [main:375] [Push enabl ed via FCM] 2018-09-30,12:14:15 **You are running version: 1.4 09/30/2018 12:14:15.190515 zmeventnotification[26791].INF [main:455] [Event Noti fication daemon v 1.4 starting] 2018-09-30,12:14:15 Calling uniq from loadTokens 09/30/2018 12:14:15.240826 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:14:15 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:14:15.344059 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] 09/30/2018 12:14:15.419092 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 09/30/2018 12:14:15.474791 zmeventnotification[26791].INF [main:1431] [About to start listening to socket] 09/30/2018 12:14:15.535500 zmeventnotification[26791].INF [main:1449] [Secure WS (WSS) is enabled...] 09/30/2018 12:14:15.592740 zmeventnotification[26791].INF [main:1455] [Web Socke t Event Server listening on port 9000] 2018-09-30,12:14:20 Active connects after INVALID_AUTH purge=1 2018-09-30,12:14:20 Active connects after INVALID_APNS purge=1 2018-09-30,12:14:25 Active connects after INVALID_AUTH purge=1 2018-09-30,12:14:25 Active connects after INVALID_APNS purge=1 09/30/2018 12:14:25.649274 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096] 09/30/2018 12:14:25.715310 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.23(id:5) so forcing reload] 2018-09-30,12:14:30 Active connects after INVALID_AUTH purge=1 2018-09-30,12:14:30 Active connects after INVALID_APNS purge=1 09/30/2018 12:14:30.649852 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:14:30 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:14:30.719341 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] 09/30/2018 12:14:30.764105 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 2018-09-30,12:14:35 Active connects after INVALID_AUTH purge=1 2018-09-30,12:14:35 Active connects after INVALID_APNS purge=1 2018-09-30,12:14:40 Active connects after INVALID_AUTH purge=1 2018-09-30,12:14:40 Active connects after INVALID_APNS purge=1 2018-09-30,12:14:45 Active connects after INVALID_AUTH purge=1 2018-09-30,12:14:45 Active connects after INVALID_APNS purge=1 2018-09-30,12:14:50 Active connects after INVALID_AUTH purge=1 2018-09-30,12:14:50 Active connects after INVALID_APNS purge=1 2018-09-30,12:14:55 Active connects after INVALID_AUTH purge=1 2018-09-30,12:14:55 Active connects after INVALID_APNS purge=1 09/30/2018 12:14:55.650511 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096] 09/30/2018 12:14:55.769861 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.23(id:5) so forcing reload] 2018-09-30,12:15:00 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:00 Active connects after INVALID_APNS purge=1 09/30/2018 12:15:00.649927 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:15:00 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:15:00.686373 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] 09/30/2018 12:15:00.744973 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 09/30/2018 12:15:00.829781 zmeventnotification[26791].ERR [ZoneMinder::Memory::M apped:95] [Memory map file '/dev/shm/zm.mmap.5' should have been 1168 but was in stead 0] 09/30/2018 12:15:00.879670 zmeventnotification[26791].ERR [ZoneMinder::Memory::M apped:95] [Memory map file '/dev/shm/zm.mmap.5' should have been 1168 but was in stead 0] 09/30/2018 12:15:00.928569 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.23(id:5) so forcing reload] 2018-09-30,12:15:05 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:05 Active connects after INVALID_APNS purge=1 09/30/2018 12:15:05.648923 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:15:05 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:15:05.701724 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] no memkey in zmMemInvalidate 09/30/2018 12:15:05.776940 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 09/30/2018 12:15:05.893024 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096] 09/30/2018 12:15:05.982640 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096] 09/30/2018 12:15:06.072754 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.21(id:7) so forcing reload] 2018-09-30,12:15:10 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:10 Active connects after INVALID_APNS purge=1 09/30/2018 12:15:10.649632 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:15:10 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:15:10.692915 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] 09/30/2018 12:15:10.852140 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 09/30/2018 12:15:10.953002 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096] 09/30/2018 12:15:11.052076 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096] 09/30/2018 12:15:11.153167 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096] 09/30/2018 12:15:11.244475 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.23(id:5) so forcing reload] 09/30/2018 12:15:11.383728 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096] 09/30/2018 12:15:11.483861 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for Kitchen(id:1) so forcing reload] 2018-09-30,12:15:15 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:15 Active connects after INVALID_APNS purge=1 09/30/2018 12:15:15.646584 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:15:15 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:15:15.721182 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] 09/30/2018 12:15:15.854969 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 09/30/2018 12:15:15.905821 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096] 09/30/2018 12:15:15.955137 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096] 09/30/2018 12:15:16.006027 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096] 09/30/2018 12:15:16.055130 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for Kitchen(id:1) so forcing reload] 09/30/2018 12:15:16.116250 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096] 09/30/2018 12:15:16.166346 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.23(id:5) so forcing reload] 2018-09-30,12:15:20 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:20 Active connects after INVALID_APNS purge=1 09/30/2018 12:15:20.648883 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:15:20 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:15:20.714068 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] 09/30/2018 12:15:20.998146 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 09/30/2018 12:15:21.107085 zmeventnotification[26791].ERR [ZoneMinder::Memory::M apped:86] [Memory map file '/dev/shm/zm.mmap.5' does not exist. zmc might not b e running.] 09/30/2018 12:15:21.162922 zmeventnotification[26791].ERR [ZoneMinder::Memory::M apped:86] [Memory map file '/dev/shm/zm.mmap.5' does not exist. zmc might not b e running.] 09/30/2018 12:15:21.212634 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.23(id:5) so forcing reload] 2018-09-30,12:15:25 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:25 Active connects after INVALID_APNS purge=1 09/30/2018 12:15:25.649434 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:15:25 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:15:25.724678 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] no memkey in zmMemInvalidate 09/30/2018 12:15:25.871140 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 09/30/2018 12:15:25.967134 zmeventnotification[26791].ERR [ZoneMinder::Memory::M apped:95] [Memory map file '/dev/shm/zm.mmap.5' should have been 1168 but was in stead 0] 09/30/2018 12:15:26.058763 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096] 09/30/2018 12:15:26.147239 zmeventnotification[26791].ERR [ZoneMinder::Memory::M apped:95] [Memory map file '/dev/shm/zm.mmap.5' should have been 1168 but was in stead 0] 09/30/2018 12:15:26.263413 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.23(id:5) so forcing reload] 09/30/2018 12:15:26.355286 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096] 09/30/2018 12:15:26.447099 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.21(id:7) so forcing reload] 2018-09-30,12:15:30 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:30 Active connects after INVALID_APNS purge=1 09/30/2018 12:15:30.646350 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:15:30 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:15:30.746552 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] no memkey in zmMemInvalidate 09/30/2018 12:15:30.820074 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 09/30/2018 12:15:30.932696 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096] 09/30/2018 12:15:31.032325 zmeventnotification[26791].ERR [ZoneMinder::Memory:26 1] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096] 09/30/2018 12:15:31.138409 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.21(id:7) so forcing reload] 2018-09-30,12:15:35 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:35 Active connects after INVALID_APNS purge=1 09/30/2018 12:15:35.649530 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:15:35 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:15:35.759824 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] 09/30/2018 12:15:35.908439 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 09/30/2018 12:15:35.967143 zmeventnotification[26791].ERR [ZoneMinder::Memory::M apped:86] [Memory map file '/dev/shm/zm.mmap.7' does not exist. zmc might not b e running.] 09/30/2018 12:15:36.016620 zmeventnotification[26791].ERR [ZoneMinder::Memory::M apped:86] [Memory map file '/dev/shm/zm.mmap.7' does not exist. zmc might not b e running.] 09/30/2018 12:15:36.066247 zmeventnotification[26791].ERR [main:525] [ Memory verify failed for 192.168.1.21(id:7) so forcing reload] 2018-09-30,12:15:40 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:40 Active connects after INVALID_APNS purge=1 09/30/2018 12:15:40.649225 zmeventnotification[26791].INF [main:491] [Total even t client connections: 1] 2018-09-30,12:15:40 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 12:15:40.712381 zmeventnotification[26791].INF [main:505] [Reloading Monitors...] no memkey in zmMemInvalidate 09/30/2018 12:15:40.762495 zmeventnotification[26791].INF [main:589] [Loading mo nitors] 2018-09-30,12:15:45 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:45 Active connects after INVALID_APNS purge=1 2018-09-30,12:15:50 Active connects after INVALID_AUTH purge=1 2018-09-30,12:15:50 Active connects after INVALID_APNS purge=1

    点赞 评论 复制链接分享
  • weixin_39639643 weixin_39639643 5月前

    Hmm darn. Looks like that did not do anything. -of-ni my code now models zmtrigger as far as I can see.

    点赞 评论 复制链接分享
  • weixin_39639643 weixin_39639643 5月前

    Filtering/formatting logs reported above to relevant ones:

    
    09/30/2018 12:14:15.142038 zmeventnotification[26791].INF [main:375] [Push enabled via FCM]
    2018-09-30,12:14:15 ******You are running version: 1.4
    09/30/2018 12:14:15.190515 zmeventnotification[26791].INF [main:455] [Event Notification daemon v 1.4 starting]
    09/30/2018 12:14:15.344059 zmeventnotification[26791].INF [main:505] [Reloading Monitors...]
    09/30/2018 12:14:15.419092 zmeventnotification[26791].INF [main:589] [Loading monitors]
    09/30/2018 12:14:25.649274 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096]
    09/30/2018 12:14:25.715310 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for 192.168.1.23(id:5) so forcing reload]
    09/30/2018 12:14:30.719341 zmeventnotification[26791].INF [main:505] [Reloading Monitors...]
    09/30/2018 12:14:30.764105 zmeventnotification[26791].INF [main:589] [Loading monitors]
    09/30/2018 12:14:55.650511 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096]
    09/30/2018 12:14:55.769861 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for 192.168.1.23(id:5) so forcing reload]
    09/30/2018 12:15:00.686373 zmeventnotification[26791].INF [main:505] [Reloading 
    09/30/2018 12:15:00.744973 zmeventnotification[26791].INF [main:589] [Loading monitors]
    09/30/2018 12:15:00.829781 zmeventnotification[26791].ERR [ZoneMinder::Memory::Mapped:95] [Memory map file '/dev/shm/zm.mmap.5' should have been 1168 but was instead 0]
    09/30/2018 12:15:00.879670 zmeventnotification[26791].ERR [ZoneMinder::Memory::Mapped:95] [Memory map file '/dev/shm/zm.mmap.5' should have been 1168 but was instead 0]
    09/30/2018 12:15:00.928569 zmeventnotification[26791].ERR [main:525] [** Memoryverify failed for 192.168.1.23(id:5) so forcing reload]
    09/30/2018 12:15:05.701724 zmeventnotification[26791].INF [main:505] [Reloading Monitors...]
    no memkey in zmMemInvalidate
    09/30/2018 12:15:05.776940 zmeventnotification[26791].INF [main:589] [Loading monitors]
    09/30/2018 12:15:05.893024 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096]
    09/30/2018 12:15:05.982640 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096]
    09/30/2018 12:15:06.072754 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for 192.168.1.21(id:7) so forcing reload]
    09/30/2018 12:15:10.692915 zmeventnotification[26791].INF [main:505] [Reloading Monitors...]
    09/30/2018 12:15:10.852140 zmeventnotification[26791].INF [main:589] [Loading monitors]
    09/30/2018 12:15:10.953002 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096]
    09/30/2018 12:15:11.052076 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096]
    09/30/2018 12:15:11.153167 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096]
    09/30/2018 12:15:11.244475 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for 192.168.1.23(id:5) so forcing reload]
    09/30/2018 12:15:11.383728 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096]
    09/30/2018 12:15:11.483861 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for Kitchen(id:1) so forcing reload]
    09/30/2018 12:15:15.721182 zmeventnotification[26791].INF [main:505] [Reloading Monitors...]
    09/30/2018 12:15:15.854969 zmeventnotification[26791].INF [main:589] [Loading monitors]
    09/30/2018 12:15:15.905821 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096]
    09/30/2018 12:15:15.955137 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096]
    09/30/2018 12:15:16.006027 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor Kitchen, expected 608, got 875967096]
    09/30/2018 12:15:16.055130 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for Kitchen(id:1) so forcing reload]
    09/30/2018 12:15:16.116250 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.23, expected 608, got 875967096]
    09/30/2018 12:15:16.166346 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for 192.168.1.23(id:5) so forcing reload]
    09/30/2018 12:15:20.648883 zmeventnotification[26791].INF [main:491] [Total event client connections: 1]
    09/30/2018 12:15:20.714068 zmeventnotification[26791].INF [main:505] [ReloadingMonitors...]
    09/30/2018 12:15:20.998146 zmeventnotification[26791].INF [main:589] [Loading monitors]
    09/30/2018 12:15:21.107085 zmeventnotification[26791].ERR [ZoneMinder::Memory::Mapped:86] [Memory map file '/dev/shm/zm.mmap.5' does not exist.  zmc might not be running.]
    09/30/2018 12:15:21.162922 zmeventnotification[26791].ERR [ZoneMinder::Memory::Mapped:86] [Memory map file '/dev/shm/zm.mmap.5' does not exist.  zmc might not be running.]
    09/30/2018 12:15:21.212634 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for 192.168.1.23(id:5) so forcing reload]
    09/30/2018 12:15:25.724678 zmeventnotification[26791].INF [main:505] [Reloading Monitors...]
    no memkey in zmMemInvalidate
    09/30/2018 12:15:25.871140 zmeventnotification[26791].INF [main:589] [Loading monitors]
    09/30/2018 12:15:25.967134 zmeventnotification[26791].ERR [ZoneMinder::Memory::Mapped:95] [Memory map file '/dev/shm/zm.mmap.5' should have been 1168 but was instead 0]
    09/30/2018 12:15:26.058763 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096]
    09/30/2018 12:15:26.147239 zmeventnotification[26791].ERR [ZoneMinder::Memory::Mapped:95] [Memory map file '/dev/shm/zm.mmap.5' should have been 1168 but was instead 0]
    09/30/2018 12:15:26.263413 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for 192.168.1.23(id:5) so forcing reload]
    09/30/2018 12:15:26.355286 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096]
    09/30/2018 12:15:26.447099 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for 192.168.1.21(id:7) so forcing reload]
    09/30/2018 12:15:30.746552 zmeventnotification[26791].INF [main:505] [Reloading Monitors...]
    no memkey in zmMemInvalidate
    09/30/2018 12:15:30.820074 zmeventnotification[26791].INF [main:589] [Loading monitors]
    09/30/2018 12:15:30.932696 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096]
    09/30/2018 12:15:31.032325 zmeventnotification[26791].ERR [ZoneMinder::Memory:261] [Shared data size conflict in shared_data for monitor 192.168.1.21, expected 608, got 875967096]
    09/30/2018 12:15:31.138409 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for 192.168.1.21(id:7) so forcing reload]
    09/30/2018 12:15:35.649530 zmeventnotification[26791].INF [main:491] [Total event client connections: 1]
    09/30/2018 12:15:35.759824 zmeventnotification[26791].INF [main:505] [ReloadingMonitors...]
    09/30/2018 12:15:35.908439 zmeventnotification[26791].INF [main:589] [Loading monitors]
    09/30/2018 12:15:35.967143 zmeventnotification[26791].ERR [ZoneMinder::Memory::Mapped:86] [Memory map file '/dev/shm/zm.mmap.7' does not exist.  zmc might not be running.]
    09/30/2018 12:15:36.016620 zmeventnotification[26791].ERR [ZoneMinder::Memory::Mapped:86] [Memory map file '/dev/shm/zm.mmap.7' does not exist.  zmc might not be running.]
    09/30/2018 12:15:36.066247 zmeventnotification[26791].ERR [main:525] [** Memory verify failed for 192.168.1.21(id:7) so forcing reload]
    09/30/2018 12:15:40.712381 zmeventnotification[26791].INF [main:505] [Reloading Monitors...]
    no memkey in zmMemInvalidate
    09/30/2018 12:15:40.762495 zmeventnotification[26791].INF [main:589] [Loading monitors]
    
    点赞 评论 复制链接分享
  • weixin_39639643 weixin_39639643 5月前

    looking at your latest logs, your monitors named 192.168.1.21 , 192.168.1.23, and kitchen seem to be erroring out every time the script is trying to call zmMemVerify. There is no alarm here.

    At this stage, I really doubt it is a problem with this script. The problem either seems to be in ZM or your installation (this is a guess, BTW).

    Some questions/clarifications:

    1. How did you install ZM 1.32.0 and which OS?

    2. Do your monitors keep crashing in normal operation (look at logs, see if zmc processes keep restarting)

    3. You mentioned a previous version of this script was actually sending out alarms (albeit missing several). That would mean zmMemVerify was failing but because the old script never checked for it first, it would move directly to the next step -> zmMemRead was succeeding in reading shared memory at the same time. I don't know enough of ZM internals to understand if this was just luck.

    4. How many monitors do you have? Do you think you can remove all monitors and just configure one?

    点赞 评论 复制链接分享
  • weixin_39720181 weixin_39720181 5月前

    I did a fresh install of ZM 1.32.0 on Ubuntu 18.04 LTS. I checked the zmc logs and I did not find any errors or restarts. Everything else seems to be working fine. On the previous version that was sending out alarms. I would receive the first couple of events but then they would stop, even though events were still occurring. After a pause in events (hour or so did not test) I would again receive a couple new event notifications.

    I have 5 monitors. I have removed them all and added just one. Started zmeventnotification.pl again but same thing appears to be happening. Also the shared data errors starts when an event occurs. I get no errors if no event occurs.

    Configuration (read /etc/zmeventnotification.ini):

    Port .......................... 9000 Address ....................... [::] Event check interval .......... 5 Monitor reload interval ....... 300

    Auth enabled .................. true Auth timeout .................. 20

    Use FCM ....................... true FCM API key ................... (defined) Token file .................... /etc/private/tokens.txt

    Use MQTT .......................false MQTT Server ....................127.0.0.1 MQTT Username ..................(undefined) MQTT Password ..................(undefined)

    SSL enabled ................... true SSL cert file ................. /etc/apache2/ssl/zoneminder.crt SSL key file .................. /etc/apache2/ssl/zoneminder.key

    Verbose ....................... true Read alarm cause .............. false Tag alarm event id ............ false Use custom notification sound . false

    09/30/2018 17:20:52.679509 zmeventnotification[2295].INF [main:375] [Push enable d via FCM] 2018-09-30,17:20:52 **You are running version: 1.4 09/30/2018 17:20:52.769750 zmeventnotification[2295].INF [main:455] [Event Notif ication daemon v 1.4 starting] 2018-09-30,17:20:52 Calling uniq from loadTokens 09/30/2018 17:20:52.840137 zmeventnotification[2295].INF [main:491] [Total event client connections: 1] 2018-09-30,17:20:52 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 17:20:52.934257 zmeventnotification[2295].INF [main:505] [Reloading M onitors...] 09/30/2018 17:20:53.022227 zmeventnotification[2295].INF [main:589] [Loading mon itors] 09/30/2018 17:20:53.067087 zmeventnotification[2295].INF [main:1431] [About to s tart listening to socket] 09/30/2018 17:20:53.108688 zmeventnotification[2295].INF [main:1449] [Secure WS( WSS) is enabled...] 09/30/2018 17:20:53.147593 zmeventnotification[2295].INF [main:1455] [Web Socket Event Server listening on port 9000] 2018-09-30,17:20:58 Active connects after INVALID_AUTH purge=1 2018-09-30,17:20:58 Active connects after INVALID_APNS purge=1 2018-09-30,17:21:03 Active connects after INVALID_AUTH purge=1 2018-09-30,17:21:03 Active connects after INVALID_APNS purge=1 2018-09-30,17:21:08 Active connects after INVALID_AUTH purge=1 2018-09-30,17:21:08 Active connects after INVALID_APNS purge=1 2018-09-30,17:21:13 Active connects after INVALID_AUTH purge=1 2018-09-30,17:21:13 Active connects after INVALID_APNS purge=1 09/30/2018 17:21:13.193442 zmeventnotification[2295].ERR [ZoneMinder::Memory:261 ] [Shared data size conflict in shared_data for monitor 192.168.1.22, expected 6 08, got 875967096] 09/30/2018 17:21:13.244842 zmeventnotification[2295].ERR [main:525] [ Memory v erify failed for 192.168.1.22(id:9) so forcing reload] 2018-09-30,17:21:18 Active connects after INVALID_AUTH purge=1 2018-09-30,17:21:18 Active connects after INVALID_APNS purge=1 09/30/2018 17:21:18.194703 zmeventnotification[2295].INF [main:491] [Total event client connections: 1] 2018-09-30,17:21:18 -->Connection 1: IP->(none) Token->fdg4ExZ6jl0:APA91bHMvABos dBpawQGkCKnqEelyMuOy2tInf2rZy0MyUOfBx6EsLn-SybxCpemPcEd80JFvSRHc4DVMGdHzpXx3uvHI vDp0dBIsS1d1AhGXe4fWJVgE2L99Pufn-JmsTiJOerwXlrS Plat:ios Push:enabled 09/30/2018 17:21:18.290729 zmeventnotification[2295].INF [main:505] [Reloading M onitors...] 09/30/2018 17:21:18.458149 zmeventnotification[2295].INF [main:589] [Loading mon itors] 2018-09-30,17:21:23 Active connects after INVALID_AUTH purge=1 2018-09-30,17:21:23 Active connects after INVALID_APNS purge=1 2018-09-30,17:21:28 Active connects after INVALID_AUTH purge=1 2018-09-30,17:21:28 Active connects after INVALID_APNS purge=1 2018-09-30,17:21:33 Active connects after INVALID_AUTH purge=1 2018-09-30,17:21:33 Active connects after INVALID_APNS purge=1

    点赞 评论 复制链接分享
  • weixin_39639643 weixin_39639643 5月前

    Also the shared data errors starts when an event occurs. I get no errors if no event occurs.

    So this really looks like a core ZM issue. I really don't know what/why though. If simple zmMemVerifys are failing for all your monitors, it seems to be a memory corruption issue.

    I run 1.32 on Ubuntu 16 and don't have this issue at all (I have 8 cameras). Given that you have only 1 camera active takes out the memory issue.

    -of-ni - any sage advice? I'm sorta clueless.

    点赞 评论 复制链接分享
  • weixin_39893205 weixin_39893205 5月前

    Couple things.

    https://github.com/pliablepixels/zmeventserver/blob/master/zmeventnotification.pl#L525 Not sure if you meant to do this on purpose, but the following line above is not necessarily an error. zmMemVerify will return false any time the shared memory changes, which happens any time a monitor is restarted for example.

    We recently discovered that cameras using x264 encode were corrupting shared memory. This was fixed just a couple days ago, so make sure you are running the latest master branch.

    点赞 评论 复制链接分享
  • weixin_39639643 weixin_39639643 5月前

    Ah ok. I'll convert that to INF. that being said the core issue of it reloading on every poll is the key unresolved issue. Does the situation above apply to you - are you using x264 encode?

    点赞 评论 复制链接分享
  • weixin_39720181 weixin_39720181 5月前

    Yes the Video Writer is set to X264 encode.

    点赞 评论 复制链接分享

相关推荐