zm working but after changeing any mon. settings -> resta

[taskforce]

Hello everybody,

i have the following problem i couldn't resolv with the README, FAQ:

My System: SuSE 9.0 no XFree, 2.4.21-144-athlon, bt848 haupauge card
shmall, shmmax 268435456

Problem:
Everything works fine until i want to change any settings in the monitor view (specially in the Source options width/heigth or in the buffer settings)

as well as restarting the server (zmpkg.pl stop and start or restart) brings me to errors. when i restart the whole server everything works with the new settings.

I always get the following errors
--------------
working fine
---------------
Nov 26 17:06:43 fwrouter zma_m5[5506]: INF [New: 23415 - Left alarm state (137) - 49(9) images]
Nov 26 17:07:27 fwrouter zma_m5[5506]: INF [New: 24523 - Gone into alarm state]
--------------
restart
-------------
Nov 26 17:07:29 fwrouter zmc_dvideo0[3514]: INF [Got TERM signal, exiting]
Nov 26 17:07:29 fwrouter zmc_dvideo0[3514]: ERR [Sync failure for frame 2 buffer 3(1): Interrupted system call]
Nov 26 17:07:29 fwrouter zmc_dvideo0[6946]: INF [Debug Level = 0, Debug Log = <none>]

---------------
error
---------------
Nov 26 17:07:29 fwrouter zmc_dvideo0[6946]: ERR [Failed to set window attributes: Invalid argument]
Nov 26 17:07:29 fwrouter zmc_dvideo0[6948]: INF [Debug Level = 0, Debug Log = <none>]
Nov 26 17:07:29 fwrouter zmc_dvideo0[6948]: ERR [Failed to set window attributes: Invalid argument]
Nov 26 17:07:29 fwrouter zma_m5[5506]: INF [Got signal (Terminated), exiting]
Nov 26 17:07:29 fwrouter zma_m5[6956]: INF [Debug Level = 0, Debug Log = <none>]
Nov 26 17:07:29 fwrouter zma_m5[6956]: INF [Warming up]
Nov 26 17:07:34 fwrouter zmc_dvideo0[6970]: INF [Debug Level = 0, Debug Log = <none>]
Nov 26 17:07:34 fwrouter zmc_dvideo0[6970]: ERR [Failed to set window attributes: Invalid argument]
-----------------------
...
-----------------------
then i get ~ 1min later
----------------------
Nov 26 17:13:12 fwrouter zma_m5[6956]: INF [Got signal (Terminated), exiting]

Nov 26 17:13:28 fwrouter zmu[7531]: ERR [Shared memory not initialised by capture daemon]
Nov 26 17:13:33 fwrouter zmu[7537]: ERR [Shared memory not initialised by capture daemon]
------------------------

I want to metion that i get shared memory in repeat which means:

after stopping the server with zmpkg.pl stop

ipcs -m gives me the following
---------------------------------------
fwrouter:/vdb/events/5 # ipcs -m

------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x7a6d2005 491520 wwwrun 700 4608508 0
0x0052e2c1 131073 postgres 600 1466368 1
0x50494f4e 393218 nobody 660 2016 1

-----------------------------------------

if i want to delete the shared memory with
ipcrm -m 49152

new shared memory is reserved with a new shmid

but i think the shared memory is not the real problem. the problem is the resize window errors before.

when i unhook the mentioned "...forced..." stuff explained in the faq my logs get messed up.

Is there anybody who could help? Are there infos i havent mentioned which could help?

thanks in advance

Matt

[zoneminder]

If you are making the image size bigger it's always worth doing a full restart if you aren't already. What size are you changing to? It's also possible that the dimensions (or other attributes) that you are choosing are not actually supported by your capture card, e.g. an image size of 357x291 will never work no matter what else you do.

Phil

[taskforce]

Hi Phil,

yes i know.
But the problem also exists if I dont change anything at all and only want to restart zm. (zmpkg.pl restart)

I red the stuff you wrote about supported sizes. So that is not the Problem.
For example:
I change the window size from anything working to anything else I Know that works. -> video device broken (errors like i posted before)
If I change it back and push save -> errors as before

Same changes need a restart of the pkg like jpeg quality,... so restarting doesnt work because video device broken with the errors in the log file.

I found good working settings for me now so I hope i dont have to restart anymore.

Maybe you want to write this Problem to the FAQ that it is possible that restarting the whole package will in some circumstances bring "errors with the window sizes" and restarting the whole computer can help

Thanks for this great program!!!!!