1.27.99 Build Path Problem Can't bind: No such file

[snerfu]

I'm not sure why the shared memory area is linked to the path I built the source from. Anyone know how to fix this? If I run strings on the binaries in /usr/local/bin I can see that path in the binaries:

2014-10-14 15:46:03.168987 zms 32767 FAT Can't bind: No such file or directory /home/snerfu/builds/ZoneMinder/src/zm_stream.cpp 302
2014-10-14 15:46:03.162793 zms 32767 WAR Shared data not initialised by capture daemon, some query functions may not be available or produce invalid results /home/snerfu/builds/ZoneMinder/src/zm_monitor.cpp 424
2014-10-14 15:46:03.120550 zms 32767 FAT Can't bind: No such file or directory /home/snerfu/builds/ZoneMinder/src/zm_stream.cpp

In my zoneminder config in the interface ZM_MAP points to /dev/shm


Here is my cmake command, I'm on CentOS 7 if that matters:

cmake -DZM_DB_HOST="localhost" -DZM_DB_NAME="zm" -DZM_DB_USER="zm" -DZM_DB_PASS="zmpass" -DZM_WEBDIR="/usr/local/share/zoneminder/www" -DZM_CGIDIR="/usr/local/libexec/zoneminder/cgi-bin" -DZM_EXTRA_LIBS="ssl" -DCMAKE_VERBOSE_MAKEFILE="ON" -DCMAKE_CXX_FLAGS_RELEASE="-D__STDC_CONSTANT_MACROS" -DZM_RUNDIR="/var/run/zm" .


But zoneminder refuses to start via CLI or or web interface.

[snerfu]

Update: I built it under the /tmp directory and now the error points to those directories as not existing. I assume they are directories. I tried them as directories first and then regular files. Neither worked. I did change owner all the way through from /tmp/ZoneMinder to the webserver user/group

014-10-15 11:05:33.999873 zms 3158 FAT Can't bind: No such file or directory /tmp/ZoneMinder/src/zm_stream.cpp 302
2014-10-15 11:05:33.985908 zms 3158 WAR Shared data not initialised by capture daemon, some query functions may not be available or produce invalid results /tmp/ZoneMinder/src/zm_monitor.cpp

[snerfu]

Another update, it's specifically a problem with 1.27.99, I built 1.27.0 just fine and it works.

[knight-of-ni]

Log entries are always going to show the path from which you built the source from. This is normal.

What you are probably experiencing is a change in some of the default variables for the folders zoneminder uses.

See this pull request for the new defaults:
https://github.com/ZoneMinder/ZoneMinder/pull/524

This was necessary because many new distros seem to be migrating towards private /tmp directories that reside in RAM, which cause issues when zoneminder tries to save certain files there. CentOS 6 does not have this issue (CentOS 7 does) so if you want to use the old values then just set them at build time.

Had you built the latest version of zoneminder and created a new dB from scratch, you would not have noticed the difference. However, for upgrades, zoneminder will not change the values of an existing database. You need to manually update the tmpdir, scokdir, rundir values under options or start over with a new database which will have the new values.