Seems the problem is gone again with the latest update. Skipping downloadĪpr 23 22:47:16 f700389c1b33 syslog-ng: syslog-ng starting up version='3.5.6'Īnd if i check the log file i get the following which is also looping Downloaded file /config/downloads/xeoma_18.4.5.tgz already exists. Using Xeoma version 18.4.5 (the latest beta version) When i start my container it keeps looping this message: however after i updated to latest Xeoma my docker images from coppit does not work any more it keeps looping and never starts. *** /etc/my_init.d/40_install_xeoma.sh failed with status 2 Tar: Error is not recoverable: exiting now Tar (child): Error is not recoverable: exiting now Tar (child): /config/downloads/xeoma_18.2.2.tgz: Cannot open: No such file or directory Installing Xeoma from /config/downloads/xeoma_18.2.2.tgz Md5sum: /config/downloads/xeoma_18.2.2.tgz: No such file or directory Using Xeoma version 18.2.2 (a user-specified version)ĭeleting /config/downloads/xeoma_17.11.24.tgz Skipping installation because the currently installed version is the correct oneĪpr 7 11:24:26 585d08292200 syslog-ng: syslog-ng starting up version='3.5.6' Downloaded /config/downloads/xeoma_17.11.24.tgz. Using Xeoma version 17.11.24 (a user-specified version) See the log directory in your config directory for server logs.Īpr 7 11:13:26 585d08292200 syslog-ng: syslog-ng starting up version='3.5.6' *** Running /etc/my_init.d/50_configure_xeoma.sh. Installing Xeoma from /config/downloads/xeoma_17.8.31.tgz Downloaded /config/downloads/xeoma_17.8.31.tgz. Deleting files in /config/downloads to reclaim space. Using Xeoma version 17.8.31 (a user-specified version) *** Running /etc/my_init.d/40_install_xeoma.sh. Has anyone been able to succesffully use the latest version of this software with this docker? But once I try to move past this version it failes. I then updated the config file to version '17.11.24' and this installed fine. Based on other responses I've seen, I changed the version to '17.8.31' and it installed fine. I saw other reports of this behavior in this forum.I've installed the docker and was having issues getting it to install and run with 'latest/latest_beta' specified in the config file. Download Buy Cloud Reselling Support New Back to articles Server and client settings: the difference While installing Xeoma video surveillance software requires just a single file, internally it’s divided into 2 parts: server and client. The memory usage also increases noticeably when this occurs. That was 7 days ago and it's still ok, but I'm assuming this will occur again sometime. The only thing that fixed it longer is deleting all the archives and database and then restarting the XeomaCoreService. rtsp-simple-server Process messages appear to show the server is running. cd /path/to/rtsp/ At the prompt, run the rtsp-simple-server server. I restarted the service several times and each time it fixed it for less than a day. At the prompt, type in the cd command to change to the directory of the rtsp-simple-server. I am using the same version of client, however this high CPU usage occurs even when no clients are connected. You can turn off all cameras via Main menu and turn on one by one to check the load.įorum is mainly a platform for our users to communicate and get in touch. I check 'top' periodically and have never seen this issue despite using this particular version and setup for months. >What is a good way to troubleshoot this? Is there a way to know what camera the rogue process is associated with? We do not recommend using different Xeoma Server and Client versions. Please make sure that you're using 19.4.22 version of Xeoma Client.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |