Monitor Exits With Error 134

[kbocek]

I have a camera I am trying to get working with 1.30, a Hikvision DS-2CD2042WD-I. Many posts here and the wiki say this camera should work fine with zm. Starting zm I see:

Code: Select all

zmdc[6782]: INF ['zmc -m 8' crashed, signal 134]

All my other monitors start fine. The camera is up and accessible.

Does anyone have any ideas?

[iconnor]

Turn on debug logging and check the logs.

[kbocek]

No help. I see a few additional message for other cameras. But this one is the same:

Code: Select all

Jan 16 11:11:07 crystal zmdc[22008]: INF ['zmc -m 8' starting at 17/01/16 11:11:07, pid = 22117]
Jan 16 11:11:07 crystal zmdc[22117]: INF ['zmc -m 8' started at 17/01/16 11:11:07]
Jan 16 11:11:07 crystal zmdc[22008]: INF ['zmc -m 8' crashed, signal 134]

Same starting and started message as with info level logging.

Any other thoughts on how to tackle this?

[kbocek]

Figured it out. Searched for Error 134 here and found a posting suggesting that you lower the number of buffers in the camera setup. I lowered buffers from 50 to 30 and the camera showed up!

This is a really hi res camera. I had already lowered the resolution to 1080p. I think I'll lower it further.

[iconnor]

You can alternatively increase the size of /dev/shm... using more ram...

[kbocek]

Yeah I need to build a new recorder. How much memory do you think for a dedicated machine hosting 6-8 hi res cameras? Is 4gb enough?

[iconnor]

depends on res/buffers, etc.. You will have to do the math.

[kbocek]

Well who has the math? I don't know what numbers to use. I can get the bytes per frame. There must be more than that times buffers.

[iconnor]

1920*1080*4 bytes * 50 frames = 3,317,760,000 bytes of ram for that monitor.

Now 8 monitors = 26,542,080,000 bytes.