Xeoma disease8/17/2023 ![]() NVME boot SSD and 10TB conventional drive for video storage (which they call the Archive). B450M Motherboard, 8GB RAM (working so well that I thought I had 16GB when first posting this!), Ryzen 5 5600G CPU* (with graphics on chip). I also placed a label on the outside of each camera with its MAC address, so I can easily look them up on the Sonicwall. This way cameras get consistent LAN IP addresses, and this can be changed for all cameras simply in the firewall's UI. To simplify things going forward, I took the extra step of programming each camera for DHCP IP addressing, and then set the LAN IP address via Static DHCP for each camera in my Sonicwall firewall. Xeoma automatically scanned the network and recognized 2 types the third type are Uniden cameras that are a few years old I had to find the rtsp stream link and enter that, but no complaints as they worked instantly when I entered it.Ĭost seems quite reasonable for what you get. *** /etc/my_init.d/40_install_xeoma.Using this now with 6 cameras of 3 different types. It reports that access top target is denied. I tried downloading the file as mentioend by Microryan however I am unable to copy the file to the downloads folder. ![]() It has been working fine but now the container keeps stopping. ![]() Two days ago I started getting an error with Xeoma. Mar 20 07:26:44 432dabeb8d87 syslog-ng: syslog-ng starting up version='3.5.6' Edited Maby thestickhughes See the log directory in your config directory for server logs. ![]() *** Running /etc/my_init.d/50_configure_xeoma.sh. Installing Xeoma from /config/downloads/xeoma_17.11.24.tgz Downloaded /config/downloads/xeoma_17.11.24.tgz. Deleting files in /config/downloads to reclaim space.ĭeleting /config/downloads/xeoma_17.8.31.tgz Using Xeoma version 17.11.24 (a user-specified version) i then switched to '17.11.24' and it seems to have updated to that and is running.for now. then i tried, '17.8.31' and it worked! the docker started up and stayed up. i kept bouncing between: 'latest', 'latest_beta', and '17.11.24'. i started trying different options in the versions line in the config file. After deleting the Xeoma folder in Appdata i stiil could not get it to work. *** /etc/my_init.d/40_install_xeoma.sh failed with status 2Īfter messing with it for another 30 minutes or so i was able to get it working again. Tar: Error is not recoverable: exiting now Installing Xeoma from /config/downloads/xeoma_from_url.tgz Downloaded file /config/downloads/xeoma_from_url.tgz already exists. Using Xeoma version (the latest stable version) *** Running /etc/my_init.d/40_install_xeoma.sh.Ĭurl: try 'curl -help' or 'curl -manual' for more information *** Running /etc/my_init.d/30_default_config_file.sh. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh. but after changing the password in the config file i get this error every time i try to start the docker. In a panic i completely removed the Xeoma docker and reinstalled it. Please any help would be greatly appreciated. Hi All, I have been running my Xeoma docker successfully for the last week untill around 3am this morning when the docker shutdown and refused to start back up. Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/ Edited Januby djvj Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/ Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/ Jan 25 12:24:04 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/ Jan 25 12:24:04 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/ Jan 25 12:24:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/ Jan 20 18:16:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/ Jan 20 18:11:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/ Jan 20 18:06:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/ It posts me every day about 1000or more errors. Can anyone check this docker, why is it doin it?
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |