app gets into weird state that prevents timeline from populating and syslog goes nuts from montage #26
Comments
|
The problem description: Right now I don't have an easy way to solve this, but solve we must..... will think..... |
|
Okay , note to self: I think I can fix it but I need to use ZM's auth token and not user=&pass= |
|
@alager actually this issue does not seem to be the issue I thought it was. According to your log report, mysqld is throwing warnings --> it also shows failed zms. Are your montage view feeds working? |
|
It appears that they stop after some event on the app. Like maybe the phone going to sleep? |
|
It's in that mode again...The montage on the phone isn't loading any images. Also, while it's doing that, the web console has difficulty displaying the monitors and the montage there doesn't work at the same time. If I go over to the logs panel (to get it to stop pulling data) then the web console starts working again. |
|
restarting the app returns the syslog messaging to normal and I can run montage on both the web console and the app at the same time. |
|
So I just updated my version of ZM to the latest version. I am just not seeing mysqld warnings or errors. I somehow feel for some reason you have an issue with mysql's configuration. I'll dig more, but I've checked on my DB and I've asked some other testers on Android and they don't seem to be seeing this. What they are however seeing is while in montage view or monitor live view mode, a log entry INF [Authenticated user 'admin'] every second - I am aware of that part and am going to fix it (eventually) |
|
try this: don't go to montage view. Go to some other view and wait for your logs to stabilize. Then go to "Monitor" view and click on "Live View" - do you see your mysqld complaining? |
|
After the app has been sitting a while, with the phone idle(screen shuts down), then starting it up: I have constant motion events happening and one camera recording, so the DB should have plenty of "traffic" to keep it awake. I don't see these types of messages now that it's up. I can go to any of the other live views and no messages. I can also go to the live view on the web console, no error messages. |
|
my db setting for wait_timeout was set to 600. I put it back to the default of 28800, we'll see if that makes things better. |
|
With montage working, my syslogs look like this: |
|
Thanks. These logs are related to ZM capturing rtsp frames. They should On Thursday, August 27, 2015, alager [email protected] wrote:
|
|
No I still get them. I'm trying to narrow it down. I know that if I start the app and go to the montage, there are no errors. But if I lock the phone (without exiting the app) and then try it some time later, then I get the errors. I won't be able to try any more until Monday. |
…d Monitor view does not hit the ZM DB and generate a million records. Solves the log pings of https://github.com/pliablepixels/zmNinja/issues/26
|
I've released version 0.73 - may take a few hours for you to see it. Once your app upgrades, please let me know if it resolves your issues. |
|
syslog behaves much better with 0.73. The issue I was seeing with the Here is a cpu chart from nmon. The CPU is at 100% is when zmNinja is in montage (getting syslog errors too). When it is below 100% zmN is on the monitor panel, and ZM is both on the console and in montage view. An interesting test, I exited zmN, then restarted it, and went to montage view, and things are well behaved; both CPU and syslog! For a good 10+ minutes I let zmN sit in montage mode, and there were no issues. I locked my phone screen, then turned it back on, still no issue. I locked it and waited about 3-4 minutes, turned it back on and blamo! High CPU and syslog errors. |
|
Thanks - some questions: a) Are you saying your CPU runs at 80% even without viewing montage views of Zomeminder? |
|
a) yes. I just modified path_swap to use a ram disk (/var/run) things seem to be better, now at 65% typical. running zmN montage( the step up): left zmN in montage and locked phone. waited 3 minutes, unlocked it, and bad behavior: |
|
Unfortunately I am just not able to replicate your sleep-wait 3-4 mins-awake-syslog/CPU issue I just ran the latest client version on Android - Samsung S3 On an average, my CPU load is 18%. When you add a montage view of zmNinja, the CPU load goes to 36% when all cameras are enabled. When I use ZM's own Montage view the CPU goes to 22% (zmNinja takes more CPU because it uses a single snapshot mode - this ensures that zmNinja can show more than 6 monitors - default chrome limit or 15 monitors - default FF limit). I tried powering off the screen 3 times, waited for 3-4 minutes each time and monitored top as well as syslog - both of them were normal - each time I turned back on, CPU went up to 33-36% and syslog said "user admin successfully logged in" -- thats it. |
|
how are the cameras configured? motion detect, monitor, record? On Mon, Aug 31, 2015 at 3:59 PM, Pliable Pixels [email protected]
|
|
All modect. It is very important to lower FPS though on a low end machine - I've changed in-camera FPS of all of them to 3 (not in ZM - you need to do it in camera) |
|
closing. I assume this is resolved. |
Here is a 1 second sample of syslog when this is happening:
The text was updated successfully, but these errors were encountered: