ZoneMinder Forums

Hi,

please do you have a working procedure for ZM install on Ubuntu 18.04 on Odroid XU4 (armhf)?
I tried to install: FFmpeg cameras (working on 1.30.4 and 1.29.0) are not working.

thanks a lot

You can use the install script on the Zoneminder wiki. I have use it on a Pi 3 B+ running Bionic. You may not get support for ffmpeg. I used local and remote cameras successfully.

https://wiki.zoneminder.com/Ubuntu_Serv ... e_easy_way

Thanks, bbunge.

It's exactly, on script, the procedure present on https://zoneminder.readthedocs.io/en/la ... untu-16-04.
That is the procedure I used.
So, it's possible to install and it's possible to get stream from remote cameras, but not possible to get ffmpeg stream (using the same working parameters used for Ubuntu 14.04/ZM1.30.04 on Radxa ARM).
In case of 16.04-18.04/ZM1.32 (and higher ZM versions) on Odroid ARM ffmpeg streams are not captured. For 16.04 I'm using ZM 1.29 since the package available on ubuntu rep.

Probably the ZM 1.32 version (or greater) is not still mature (*) or only for experts.

(*): the ZM package not available in 18.04 ubuntu repository and only 1.29 is available on 16.04 ubuntu repository. You might add ppa:iconnor/zoneminder-1.32 repository, but ffmpeg not working.

Actually the ffmpeg source type does work on my Pi 3B+. The Storage/Video Writer is not compatible with Arm processors and needs to be disabled. Enabling Storage/Save JPEGS/Frames only does jpeg files quite well!

I'm not able to capture and view the ffmpeg stream. In the log I'm receiving the following error messages:
could you help me to understand what is broken?

Note: I'm using the same camera configuration parameters working for 1.30.04 (on 14.04 and radxa arm) and for 1.29.0 (on 16.04 and odroid XU4 arm)
Note: I installed 18.04 on my PC (in a VMware virtual environment), and then ZM 1.32.3. It is working with all cameras (remote and ffmpeg too). So it seems an issue on ARM processor/ZM 1.32 or only with the 18.04 Ubuntu image for Odroid XU4.

I do my development on the exact same setup you are running, ODroid XU4 (technically it's an HC1 which has the brains of an XU4) on Armbian (Ubuntu 18.04). I am not experiencing any streaming issues, and I've tested this on several cameras.

Verify your operating system is stock. By that I mean, verify you have not installed any packages from third party repositories, especially ffmpeg.

Verify the video writer mode is NOT set to x264 Encode. You should not be able to select this mode in the dropdown because it is not compatible on arm, but double check anyway.

Verify you are not trying to stream to something else at the exact same time you are conducting your zoneminder tests. This includes the cameras built in web page.

Verify the resolution in zoneminder exactly matches that of the incoming stream. Use vlc player to tell you what the resolution should be.

Once you have verified all those steps, try building a zoneminder package yourself, using the do_debian script, like I described to you in our private message.

Instructions are here:
https://zoneminder.readthedocs.io/en/la ... rom-source

For experimentation, try to build the latest master. It has additional ffmpeg output and might provide additional information.

If the master branch does work, use the same do_debain script to build the latest release, and repeat the experiment.

thanks, Knight.
I'm running the Ubuntu 18.04 image provided by Odroid in their wiki site. I tried different 18.04 versions they provided till the last of Dec 2018. I tried with 16.04 too.

No third part pakage installed. LAMP installed through ubuntu repos. To be sure I reinstalled ffmpeg using Ubuntu repos. The only third part repo I added is ppa:iconnor/zoneminder-1.32
Writer mode set to "disabled". I tried "H264 camera passthrough" too. You are right: "x264 Encode" is disabled.

I was trying to stream at the same time from Radxa and from Odroid XU4 1 (i have 2 Odroid XU4 boardS). I turned off both, leaving only 1 Odroid XU4 working. Verified resolution through VLC: H264 - MPEG4- AVC (part10)(h264), 640x480 (the same used in ZM), 10 fps, colors managed by ITU-R BT.709.

No way. Unfortunately it continues to do not capture the ffmpeg streams.
So, it should be something related to the ubuntu images provided by Odroid.

I wil try, as you suggested, with Armbian building the zm package by myself. That's my first build with ZM! I'm not an expert.It MUST work since you have the same setup. I will try too with the latest master too.

So, knight, thanks a lot. I will report about my next steps. I will do during week end.

Thanks best regards

great and many many thanks, Andrew!

I started with Armbian (since you told me working) and I built the 1.33.1 package from source according to your recommendation. Then installed ZM. Then installed an ffmpeg camera. And it works!

It's possible to capture the ffmpeg stream and it's possible to see recorded images selecting "H264 Camera Passthrough" as Video Writer.
I want to try the same with the 18.04 Ubuntu image provided by Odroid wiki as you suggested. For my curiosity. Even if Armbian seems a good distro too: I have a jessie debian distribution on my Radxa (my second ARM board) and I like it..

Definitively 1.33.1 can work on ARM and ffmpeg. I will try with with the 18.04 provided by Hardkernel building the ZM package from source.
For now many many thanks. I will tell you about further experiments.

Moreover I learnt about how to build a ZM package. Again thanks a lot.
Michele

Hi Andrew, I tried too with the 18.04 and 16.04 images provided by Hardkernel.

I was succesful to build ZM from source and install the last 1.33.1 (and 1.32.3 too), but in this case, differently from Armbian image, ffmpeg streams are not captured (the error messages are those I reported in previous post).

So, since 1.33.1 is working on ARMbian, the issue is related to images provided by Odroid. Probably you would be able to understand what to be adjusted on the Ubuntu images provided by Hardkernel, I'm not.

For experiment, I built from souce a lower ZM versions 1.30.4 on xenial (16.04) image provided by Hardkernel. Same issue: ffmpeg not working and in ZM log same error messages as I posted previously.
So it seems an issue related to the Ubuntu images provided by Hardkernel:

https://wiki.odroid.com/odroid-xu4/os_i ... 4/20181203 (for 18.04)
https://wiki.odroid.com/odroid-xu4/os_i ... 4/20171213 (for 16.04)

The strange is ZM 1.29.0 is working fine with the 16.04 image provided by Hardkernel! So, something changed between 1.29 and 1.30 in the way ffmpeg streams are not working on ubuntu Hardkernel images.

Definitively I will use the Armbian 18.04 image that is working.
Andrew, please, since you have Odroid XU4, if you will have time, install ZM 1.33 package on 18.04 (or 16.04) provided by Hardkernel + LAMP and pls let me know what hell could be the issue (i.e.: why ffmpeg stream is not working).

Anyway, thanks, since I solved with the Armbian distro and I learnt how to build from source.
thanks

EDIT 2019 Feb 10: unfortunately also Armbian has little issues, but for me important. On 1.33.1 and 1.32.3 both I'm not able to:

- view recorded MJPEG streams (i have a still image whatever selection for Save JPEGs in storage)
- save New (PTZ) Control (after pushing save button, the activity doesn't complete).

Probably the issues are simple to solve adiusting anything on ZM or Apache config file, or chowing anything or whatever hell needed (i passed all week end trying to adjust, no way). I tried but I'm not an expert.
I'm coming back to Ubuntu 16.04 image provided by Hardkernel and ZM 1.29 and Odroid XU4. All is working fine with such setup.
Probably due to different linux distros to be managed and the specific not so diffused ARM technology, the ZM tool is not still mature for newbie like me and good only for experts/developers. I understand the tool is not commercial and based on the good will of volunteers. 1.29 on Odroid XU4 and 1.30.4 on the older Radxa Pro are fully working and enough.

Hi Andrew,

I have an interesting update.
With support of Odroid community the issue related to unavailability to capture FFMPEG streams is solved.
Rebuilding FFMPEG, forcing it to do not use h264_v4l2m2m, now it's possible to capture FFMPEG streams also using the 18.04 Hardkernel Odroid distro.
With the Armbian distro I didn't have the issue.

The remaning issue (still on Hardkernel distro, still on Armbian distro, still on ARM, still on my laptop) is when I try to see recorded images of MJPEG cameras (camera is configured as remote and in Storage: Save JPEGs= Frames only, Video writer= disabled).
I'm able to view the MJPEG stream, but not able to view a recorded MJPEG stream.

In the logs I'm getting the following message:

"Socket /var/run/zm/zms-251032s.sock does not exist. This file is created by zms, and since it does not exist, either zms did not run, or zms exited early. Please check your zms logs and ensure that CGI is enabled in apache and check that the PATH_ZMS is set correctly. Make sure that ZM is actually recording. If you are trying to view a live stream and the capture process (zmc) is not running then zms will exit. Please go to http://zoneminder.readthedocs.io/en/lat ... window-etc for more information."


Note: for the laptop i have a workaround: in Storage: Save JPEGs= Disabled, Video writer= X264 Encode. For ARM (= Odroid, Raspberry,...) no workaround.

Is it a bug on higher ZM versions? I found the regression on my ARM board and on my laptop. I don't have such issue on 1.30.4: ZM is able to reproduce a video from recorded JPEGs.

thanks

Hi pat2, have you news ?

I compiled zoneminder to version v 1.33.12

my system is Armbian:
Linux Odroid-HC1 4.14.111-odroidxu4 # 2 SMP PREEMPT Wed May 8 17:30:01 CEST 2019 armv7l armv7l armv7l GNU / Linux
Hardware: Odroid HC-1

zoneminder_1.33.12~20190713064922-bionic_armhf.deb
https://www59.zippyshare.com/v/CPpHEdBN/file.html

zoneminder-dbg_1.33.12~20190713064922-bionic_armhf.deb
https://www62.zippyshare.com/v/Fcj0Kmkl/file.html

zoneminder-doc_1.33.12~20190713064922-bionic_all.deb
https://www58.zippyshare.com/v/zlpG0h8v/file.html
https://www.dropbox.com/sh/sqjwnrh5dsvz ... VF-0a?dl=0

detxm80 wrote: ↑Mon Apr 15, 2019 10:52 pm Hi pat2, have you news ?

Hi @detxm80,

on the new version 1.36.7 the issue disappeared.
We had to wait 2 years, but finallly solved.
Please try, I'm sure it's working now.