Added 3 cameras, same model, one doesn't work

[pigpen]

I've come back to Zoneminder after using several commercially packaged products. I can't stand how bloated they are and proprietary that are in every way. The last time I used ZM was in 2011. Fast forward 7 years....

I installed 1.30.4 on a test ubuntu box. Got it installed and running easily. I have several cameras to mess with. Advida (A34 and A35's), an old Axis and some very high end Panasonic PTZ's. Thus far, I got the Axis running and 3 of the 4 Advidia's running. Oddly enough, one of the Advidia's I cannot get to stream. Same settings, same user, same pass, same model, same firmware. I used ONVIF to setup the local cameras (the Advidia's) and it has worked flawlessly except for the one.
Oddly enough, I get some errors:

2018-03-25 22:31:42.086906 zms 20107 ERR Backtrace 6: /usr/lib/zoneminder/cgi-bin/nph-zms(_start+0x29) [0x5614d6f41f69] zm_signal.cpp 102
2018-03-25 22:31:42.085457 zms 20107 ERR Backtrace 5: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fc8cf723830] zm_signal.cpp 102
2018-03-25 22:31:42.083960 zms 20107 ERR Backtrace 4: /usr/lib/zoneminder/cgi-bin/nph-zms(main+0xb9e) [0x5614d6f4106e] zm_signal.cpp 102
2018-03-25 22:31:42.082678 zms 20107 ERR Backtrace 3: /usr/lib/zoneminder/cgi-bin/nph-zms(_ZN13MonitorStream9runStreamEv+0x48) [0x5614d6f7aa38] zm_signal.cpp 102
2018-03-25 22:31:42.081502 zms 20107 ERR Backtrace 2: /usr/lib/zoneminder/cgi-bin/nph-zms(_ZNK7Monitor6GetFPSEv+0xd) [0x5614d6f6dd9d] zm_signal.cpp 102
2018-03-25 22:31:42.080053 zms 20107 ERR Backtrace 1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7fc8d3031390] zm_signal.cpp 102
2018-03-25 22:31:42.078720 zms 20107 ERR Backtrace 0: /usr/lib/zoneminder/cgi-bin/nph-zms(_Z14zm_die_handleriP9siginfo_tPv+0x78) [0x5614d6fc0fa8] zm_signal.cpp 102
2018-03-25 22:31:42.077213 zms 20107 ERR Signal address is 0x7fc8a4da3004, from 0x5614d6f6dd9d zm_signal.cpp 81
2018-03-25 22:31:42.075522 zms 20107 ERR Got signal 7 (Bus error), crashing zm_signal.cpp 50
2018-03-25 22:31:41.990626 web_js 14417 ERR getStreamCmdResponse stream error: socket_sendto( /var/run/zm/zms-164462s.sock ) failed: Connection refused - checkStreamForErrors() ?view=watch
2018-03-25 22:31:41.961392 web_php 14417 ERR socket_sendto( /var/run/zm/zms-164462s.sock ) failed: Connection refused /usr/share/zoneminder/www/includes/functions.php 2033

Again, all is working perfect with the other cameras. (the Axis and Advidia's). I have not setup the Panasonic PTZ's yet, but I'm sure they will be fun. Thanks for the suggestions. It is refreshing how quickly I can find events and export them vs the same process in VideoInsight or such.

Thanks!

[bbunge]

Did you run out of shared memory? Check the free space in /dev/shm

[pigpen]

Dam. You are spot on.
$df -h /dev/shm
Filesystem Size Used Avail Use% Mounted on
tmpfs 1.9G 1.9G 0 100% /dev/shm

So. I'll google a bit about increasing the shared memory. Thanks for the catch. I'll post how and if this resolves it.

[bbunge]

Be careful. Adding RAM is your best bet or using lower camera resolution. Ubuntu uses half of the RAM for tmpfs and taking more can rob other processes of needed memory. As you increase the number of events MySQL will need more memory (innodb_buffer_pool_size).
I use Webmin to manage my Ubuntu/Debian servers. Webmin can be used to change the amount of RAM /dev/shm uses.
Oh, if you are using a desktop version of Ubuntu go back to a minimal server version to save some RAM.

[pigpen]

After checking the shared memory, I was using 100% of my 2 GB. (4 GB Ram in system). I killed X and dropped a camera and the odd camera out started working. Since this is a "test" I figure I'll just keep it to 2-3 cameras a most so I won't run into issues. In the long run, we will deploy "real" servers with considerably more ram.
I'll have to dig around the forum a bit, looking to do around 100 cameras, all 3 MP with motion detection. Needless to say, this little laptop won't do that, but I'll do some research and some math to see what is needed. We may also host virtually on a VMWare deployment. All of this onsite, nothing in the cloud.