jonathansayeb Posted January 25, 2018 Share Posted January 25, 2018 Just wanted to let you all know especially XEOMA TEAM that i've been running 8 cameras for 5 months already and everything is working great except for the terrible log problem that keeps filling up my docker.img. Please Xeoma do something asap. Cheers. Quote Link to comment
NewDisplayName Posted January 25, 2018 Share Posted January 25, 2018 HERE is no xeoma team. Im currently writing with their support (why im the only one???) Quote Link to comment
djvj Posted January 25, 2018 Share Posted January 25, 2018 (edited) On 1/20/2018 at 12:42 PM, nuhll said: Can anyone check this docker, why is it doin it? It posts me every day about 1000or more errors... Jan 20 18:06:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-16Jan 20 18:06:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-17Jan 20 18:06:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-18Jan 20 18:11:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-16Jan 20 18:11:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-17Jan 20 18:11:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-18Jan 20 18:11:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-16Jan 20 18:11:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-17Jan 20 18:11:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-18Jan 20 18:11:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-16Jan 20 18:11:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-17Jan 20 18:11:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-18Jan 20 18:16:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-16Jan 20 18:16:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-17Jan 20 18:16:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-18Jan 20 18:16:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-16Jan 20 18:16:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-17Jan 20 18:16:34 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/Kinderzimmer/2018-01-18 nuhll, I just started getting these as well!! Jan 25 12:24:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/2018-01-21Jan 25 12:24:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/2018-01-22Jan 25 12:24:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/2018-01-23Jan 25 12:24:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/2018-01-24Jan 25 12:24:04 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/2018-01-25Jan 25 12:24:04 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/2018-01-21Jan 25 12:24:04 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/2018-01-22Jan 25 12:24:04 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/2018-01-23Jan 25 12:24:04 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/2018-01-24Jan 25 12:24:04 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/2018-01-25Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/2018-01-21Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/2018-01-22Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/2018-01-23Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/2018-01-24Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.12/2018-01-25Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/2018-01-21Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/2018-01-22Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/2018-01-23Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/2018-01-24Jan 25 12:29:03 Storinator shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk2/Surveillance/Preview+Archive.18/2018-01-25 Edited January 25, 2018 by djvj Quote Link to comment
ksignorini Posted February 1, 2018 Share Posted February 1, 2018 Thanks for this docker. I've installed the docker, set the password in the config file, restarted the docker and attempted to connect to it via the client on my Mac. The client sees the server (I've tested a few ways; stopping docker for example) but can't connect because it says that the password I'm entering is wrong. I've edited the config, changed the password, and restarted the docker several times. No go. Any idea why it wouldn't be accepting the password that's set? Thanks! Quote Link to comment
ksignorini Posted February 1, 2018 Share Posted February 1, 2018 4 minutes ago, ksignorini said: Any idea why it wouldn't be accepting the password that's set? Ugh. Now it's working. Thanks again for the docker! Quote Link to comment
Microryan Posted February 8, 2018 Share Posted February 8, 2018 I've been running Xeoma without any issues for a few months now. However, I'd like to be able to access it directly from my phone when I'm on the go. Does anyone have Xeoma setup with a reverse proxy? I found this discussion: http://felenasoft.com/forum/viewtopic.php?f=8&t=581 ...but it's quite old. I've never setup a reverse proxy, shouldn't this be easier / different with Unraid 6.4.1 ? Quote Link to comment
Greygoose Posted February 10, 2018 Share Posted February 10, 2018 This is a tempting move for me, running blue iris for years. I like the idea of this in a docker.. Quote Link to comment
ksignorini Posted February 27, 2018 Share Posted February 27, 2018 On 5/7/2017 at 11:27 AM, hendu said: I've been running this licensed for the last week and a half now. Overall I'd say things have been great. I think I lose a few features over blue iris, but not having to run a windows vm that was consuming the amount of CPU necessary for BI is a nice trade off. I am noticing that occasionally the licensing must lose connection to their servers, and since the docker is a vm and requires constant connection, this requires me to re-enter my code. I have to see why that's happening, I've been rebooting my server a bit more lately as I work on things, I'll have to see if that's related. How did you get a license installed? When I connect to the server (container) with my client and try to activate the license I bought I get this: Quote Link to comment
thestickhughes Posted March 20, 2018 Share Posted March 20, 2018 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. Please any help would be greatly appreciated. In a panic i completely removed the Xeoma docker and reinstalled it. but after changing the password in the config file i get this error every time i try to start the docker. Here is my log file from unraid *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...*** Running /etc/my_init.d/30_default_config_file.sh...[Mar 20 06:59:23 AM] Processing config file*** Running /etc/my_init.d/40_install_xeoma.sh...curl: no URL specified!curl: try 'curl --help' or 'curl --manual' for more information[Mar 20 06:59:23 AM] Using Xeoma version (the latest stable version)[Mar 20 06:59:23 AM] Downloaded file /config/downloads/xeoma_from_url.tgz already exists. Skipping download[Mar 20 06:59:23 AM] Installing Xeoma from /config/downloads/xeoma_from_url.tgzgzip: stdin: unexpected end of filetar: Child returned status 1tar: Error is not recoverable: exiting now*** /etc/my_init.d/40_install_xeoma.sh failed with status 2*** Killing all processes... Quote Link to comment
NewDisplayName Posted March 20, 2018 Share Posted March 20, 2018 (edited) Hey, just try to delete first the directory in the appdata (you could also make a copy of it) and then try to install. Did you found out why dockers didnt startet? Maybe something with your disks is wrong? Edited March 20, 2018 by nuhll Quote Link to comment
thestickhughes Posted March 20, 2018 Share Posted March 20, 2018 (edited) after messing with it for another 30 minutes or so i was able to get it working again. After deleting the Xeoma folder in Appdata i stiil could not get it to work. i started trying different options in the versions line in the config file. i kept bouncing between: 'latest', 'latest_beta', and '17.11.24'. still nothing worked. then i tried, '17.8.31' and it worked! the docker started up and stayed up. i then switched to '17.11.24' and it seems to have updated to that and is running...for now. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...*** Running /etc/my_init.d/30_default_config_file.sh...[Mar 20 07:26:41 AM] Processing config file*** Running /etc/my_init.d/40_install_xeoma.sh...[Mar 20 07:26:41 AM] Using Xeoma version 17.11.24 (a user-specified version)[Mar 20 07:26:41 AM] Deleting files in /config/downloads to reclaim space...Deleting /config/downloads/xeoma_17.8.31.tgz[Mar 20 07:26:41 AM] Downloading from http://felenasoft.com/xeoma/downloads/xeoma_previous_versions/?get=xeoma_linux64_17.11.24.tgz into /config/downloads[Mar 20 07:26:44 AM] Downloaded /config/downloads/xeoma_17.11.24.tgz...[Mar 20 07:26:44 AM] Installing Xeoma from /config/downloads/xeoma_17.11.24.tgz[Mar 20 07:26:44 AM] Installation complete*** Running /etc/my_init.d/50_configure_xeoma.sh...[Mar 20 07:26:44 AM] Setting the passwordPassword set successfull*** Running /etc/rc.local...*** Booting runit daemon...*** Runit started as PID 66[Mar 20 07:26:44 AM] Starting the server in 5 seconds. See the log directory in your config directory for server logs.Mar 20 07:26:44 432dabeb8d87 syslog-ng[75]: syslog-ng starting up; version='3.5.6' Edited March 20, 2018 by thestickhughes Quote Link to comment
kahunamike Posted March 21, 2018 Share Posted March 21, 2018 Thanks @thestickhughes! That worked for me too. After upgrading Unraid to 6.5, Xeoma wouldn't start up anymore. Modified the Xeoma.conf file down to 17.8.31 and back up to 17.11.24 seemed to do the trick. Quote Link to comment
evplasmaman Posted March 21, 2018 Share Posted March 21, 2018 Hi everyone, I recently added a cache pool to my Unraid server and have set my security footage shared folder to "Use cache disk" = Yes. Xeoma now writes all the video to the cache drive and at night the Mover script moves it over to my spinning rust array. The issue is that Archive.db and Archive.db-wal are included in the same folder as the rest of the bulk archive video data and are moved over to the array where they are actively kept open. They seem to be accessed every few seconds which mean the array never gets a chance to spin down. Has anyone come up with a solution to this? Is it be possible to add a volume to the docker for the archive dbs? Many Thanks, Jos Quote Link to comment
NewDisplayName Posted March 21, 2018 Share Posted March 21, 2018 (edited) Yea, "easy". Set mover to move at close midnight. Like 23:55. But where is the archive db? I hope u have your appdata on cache also? (if u change cache settings, you have to manually move files) Edited March 21, 2018 by nuhll Quote Link to comment
ksignorini Posted March 22, 2018 Share Posted March 22, 2018 Hi everyone. Xeoma died on me. I shut it down, started it back up, and now it won't work (and it was working great before that!) It looks like it's trying to download some app code on each restart and the file its getting is 0 bytes. I've tried putting back an older version of the appdata/Xeoma folder and each time it starts it erases whats in appdata/Xeoma/downloads, re-downloads some broken file, and dies. Thoughts? Quote Link to comment
Microryan Posted March 22, 2018 Share Posted March 22, 2018 (edited) 1 hour ago, ksignorini said: Hi everyone. Xeoma died on me. I shut it down, started it back up, and now it won't work (and it was working great before that!) It looks like it's trying to download some app code on each restart and the file its getting is 0 bytes. I've tried putting back an older version of the appdata/Xeoma folder and each time it starts it erases whats in appdata/Xeoma/downloads, re-downloads some broken file, and dies. Thoughts? I had the same issue, but managed to fix it by downloading the Linux x64 version and renaming it to "xeoma_from_url.tgz" and putting it in the downloads folder. As a bonus, I did this with the new beta version and it runs better than latest stable version. I'm now able to smoothly watch my footage at 20x playback speed, which didn't work well before. I think you also need to edit the conf file to make it install. Edited March 22, 2018 by Microryan Quote Link to comment
ksignorini Posted March 22, 2018 Share Posted March 22, 2018 1 minute ago, Microryan said: I had the same issue, but managed to fix it by downloading the Linux x64 version and renaming it to "xeoma_from_url.tgz" and putting it in the downloads folder. As a bonus, I did this with the new beta version and it runs better than latest stable version. I'm now able to smoothly watch my footage at 20x playback speed, which didn't work well before. I wonder what's going on there. Do you have the link you downloaded from? Quote Link to comment
Microryan Posted March 22, 2018 Share Posted March 22, 2018 (edited) 1 minute ago, ksignorini said: I wonder what's going on there. Do you have the link you downloaded from? https://felenasoft.com/xeoma/downloads/xeoma_beta_linux64.tgz Edited March 22, 2018 by Microryan 1 Quote Link to comment
ksignorini Posted March 23, 2018 Share Posted March 23, 2018 Worked like a charm. Thanks again! Quote Link to comment
darrenyorston Posted March 27, 2018 Share Posted March 27, 2018 (edited) Hi there. Two days ago I started getting an error with Xeoma. It has been working fine but now the container keeps stopping. I tried downloading the file as mentioend by Microryan however I am unable to copy the file to the downloads folder. It reports that access top target is denied. The log file shows the following error: *** Killing all processes...*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...*** Running /etc/my_init.d/30_default_config_file.sh...[Mar 27 12:07:19 PM] Processing config file*** Running /etc/my_init.d/40_install_xeoma.sh...curl: no URL specified!curl: try 'curl --help' or 'curl --manual' for more information[Mar 27 12:07:21 PM] Using Xeoma version (the latest stable version)[Mar 27 12:07:21 PM] Downloaded file /config/downloads/xeoma_from_url.tgz already exists. Skipping download[Mar 27 12:07:21 PM] Installing Xeoma from /config/downloads/xeoma_from_url.tgzgzip: stdin: unexpected end of filetar: Child returned status 1tar: Error is not recoverable: exiting now*** /etc/my_init.d/40_install_xeoma.sh failed with status 2 Edited March 27, 2018 by darrenyorston update Quote Link to comment
darrenyorston Posted March 28, 2018 Share Posted March 28, 2018 On 24/03/2018 at 12:23 AM, ksignorini said: Worked like a charm. Thanks again! How were you able to copy the file across? I keep receiving a message that the downloads folder is read only. I have tried changing it but it seems to remain read only all the time. Quote Link to comment
ksignorini Posted March 28, 2018 Share Posted March 28, 2018 (edited) I have a share that I copied it to using SMB. Then I went into a terminal and copied it to the Xeoma folder with the cp command. I think I changed ownership on the file with chown as well. Edited March 28, 2018 by ksignorini Quote Link to comment
pcaro Posted March 28, 2018 Share Posted March 28, 2018 On 22/3/2018 at 7:22 PM, Microryan said: https://felenasoft.com/xeoma/downloads/xeoma_beta_linux64.tgz Thanks! Quote Link to comment
darrenyorston Posted March 29, 2018 Share Posted March 29, 2018 On 28/03/2018 at 11:26 AM, ksignorini said: I have a share that I copied it to using SMB. Then I went into a terminal and copied it to the Xeoma folder with the cp command. I think I changed ownership on the file with chown as well. I cant seem to get it to work. The Xeoma folder on appdata remains read only regardless of what I do. It says the permissions have been changed by each time I try to copy the tgz file to my SMB appadata share it says permission denied. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.