Open JanSimek opened 6 years ago
Though your configuration looks ok, which browser are you using to open the stream. It might be that the machinery 'online' check fails. Which OS are you using?
Kerberos runs on Arch linux. I tried with Edge on Windows 10 and Google Chrome on Android and it does work on Android, so it must be an issue with the browser. Thanks.
@JanSimek well that's what I'm trying to explain. The check happens in the web, and apparently that's not working on your arch linux install. https://github.com/kerberos-io/web/blob/master/app/Http/Repositories/System/OSSystem.php#L183-L198
@cedricve just wondering, wouldn't it be better to use systemctl is-active kerberosio
. That should work the same on Raspberry Pi (Raspbian), shouldn't it?
@JanSimek thanks for the share, hmm yeah I think so. Let me check.
I'll add a fix so it gives better cross-platform support. Thanks for noticing @JanSimek, will be in next release.
@cedricve, I also want to note that this method of detecting the machinery is not compatible with any kind of docker orchestration tools like rancher. For this to work i believe the machinery service needs to have its own api running on top to be accessible from, or maybe merge it into 1 docker container :)
I run this in rancher, so no issue in docker orchestration.
version: '2'
volumes:
kerberosio-service-conf-files:
external: true
driver: rancher-nfs
kerberosio-machinery-conf-files:
external: true
driver: rancher-nfs
kerberosio-machinery-capture-files:
external: true
driver: rancher-nfs
kerberosio-machinery-capture-h264-files:
external: true
driver: rancher-nfs
kerberosio-machinery-log-files:
external: true
driver: rancher-nfs
services:
service:
image: kerberos/web:v2.4.0
stdin_open: true
volumes:
- kerberosio-service-conf-files:/var/www/web/config
tty: true
volumes_from:
- machinery
ports:
- 8180:80/tcp
labels:
io.rancher.container.pull_image: always
io.rancher.scheduler.affinity:host_label: host.name=microesxi
io.rancher.sidekicks: machinery
machinery:
image: kerberos/machinery:v2.4.0
stdin_open: true
volumes:
- kerberosio-machinery-conf-files:/etc/opt/kerberosio/config
- kerberosio-machinery-log-files:/etc/opt/kerberosio/logs
- kerberosio-machinery-capture-files:/etc/opt/kerberosio/capture
- kerberosio-machinery-capture-h264-files:/etc/opt/kerberosio/h264
tty: true
labels:
io.rancher.container.pull_image: always
Amazing, thanks for sharing @shacal! we should include this in the documentation. Would you be interesting to share a tutorial with us?
Hi, I'm having the same issue using docker with raspberry pi2
I created the container with
sudo docker run --name kerberos_salotto -p 80:9020 -p 8889:9021 -d kerberos/kerberos
And I see in the log
08/02/2019 16:07:05.300 INFO [trivial] Reading configuration file: /etc/opt/kerberosio/config/config.xml 08/02/2019 16:07:05.301 ERROR [trivial] TinyXML : could not open the xml file, maybe the file doesn't exist?
I checked in the container volume and no config.xml file is present
In docker environment i receive error TinyXML : could not open the xml file, maybe the file doesn't exist? But the file exist and have 777 permission
I followed the Generic installation path and installed latest Kerberos.io from git. When I go to Web -> Systém panel, it says that machinery is not running but according to
systemctl status kerberosio
, it is running (I assume kerberosio = machinery). Also, ip camera view on the dashboard is stuck at "Almost there, hold on"