darrenyorston

I have tried adding cameras to Zoneminder but they remain red in the console. My cameras are Dlink DCS-4602EC. I utilised the settings per https://wiki.zoneminder.com/D-Link#DCS-4602EV The log file is attached. I know the cameras work zm-log.txt

Hello all. I have some concerns about my Docker setup. I think I have my containers setup correctly. I followed Spaceinvader One's guides for setting up containers such as Deluge, Radarr, Sonarr. The size of the container folders in my appdata directory is quite large and I don't know if it should be the case. I am concerned that I have set something up incorrectly and I have duplicate files on my server. My binhex-plex container folder for example is 225GB. (Size on disk reported by Windows file explorer) My /media path is set to /mnt/user/Video/ My CrashPlan Pro container folder is 12.1GB. (Size on disk reported by Windows file explorer) I have my backup set to preserve my appdata folder, USB Backup, and libvirt.img. The produced CA_backup archive is 65GB. This seems way excessive. What folder size should one expect to see for container folders in appdata?

So the hardware doesnt matter? Ill be changing MB, CPUs, memory, NICs. Only thing Ill be porting will be my HDDs and cache SSDs

Could someone point me to a thread or guide about moving my licence to a new system? I have an existing system which runs fine. However, I am about to start building a new server. I want to make sure everything actually works with the new hardware before I move over my key and drives.

I tried to install the container but wont keep operating. The log reports: Port 8080 not available2018-05-27 19:54:06,299 INFO exited: unifi (exit status 255; not expected)2018-05-27 19:54:07,301 INFO spawned: 'unifi' with pid 892018-05-27 19:54:08,302 INFO success: unifi entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2018-05-27 19:54:16,147 WARN received SIGTERM indicating exit request2018-05-27 19:54:16,147 INFO waiting for unifi to die2018-05-27 19:54:16,152 INFO stopped: unifi (exit status 143) I tried altering the port from 8080 but it wont accept anything else.

Trouble is unless you keep watvching the docker containers who dont know that it is no longer working. I dont run the client unless I want to view the camera feeds. Most of the time I just record to a file server. With the docker container crashing its only when I check on the footage that I notice it has not been recording. This can be days.

I have tried to set the version in xeoma.conf to 17.11.24, the same as my client application however the container will still not remain active. The log is reporting: *** Killing all processes...*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...*** Running /etc/my_init.d/30_default_config_file.sh...[May 14 03:03:27 PM] Processing config file*** Running /etc/my_init.d/40_install_xeoma.py...Traceback (most recent call last):File "/etc/my_init.d/40_install_xeoma.py", line 198, in <module>version_number, download_url, alternate_download_url = resolve_download_info()File "/etc/my_init.d/40_install_xeoma.py", line 100, in resolve_download_infoversion_number, download_url = version, VERSION_DOWNLOAD_URL.format(version_number)UnboundLocalError: local variable 'version_number' referenced before assignment*** /etc/my_init.d/40_install_xeoma.py failed with status 1

My Xeoma container has started crashing again and won't remain online. It had been doign this however with recent updates it began working fine. I am presuming that something has changed again causing the container to fail.

I didnt get a container update. Also what would I edit in the xeoma.conf? The version? To make it the same as the client? I tried that and it the container keeps stopping with seconds of starting.

Yes. I was using 17.11.24. I only went to the 18.4.5 beta because of this message that I needed the 18.2.2 client.

Hello. I have started having a problem with Xeoma again. Previous I had the issue with the container stopping all the time due to the failed download as reported by ksignorini on March 23. I was able to resolve the issue however now every time the Xeoma client starts it says the server is the wrong version. At the moment Xeoma keeps asking for version 18.2.2. I have updated to the 18.4.5 beta however it keeps saying that to connect to the server I need version 18.2.2 I cant seem to find the 18.2.2 client version on Xeoma's website.

That worked. Much appreciated.

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.

32GB. Currently building a 256GB unit as 32GB isnt enough to run my system.

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.

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

E5-2680s are $2500 a piece for me. 14 core/28 threads. Xeon Silver 4114s are $1000 a piece. 10 cores/28 threads. E5s x 2 28 cores ($5000/pair) vs 3647s x 2 20cores ($2000). Not sure whether the additional 8 core is worth the $3000 increase. I am always cautious of eBay ex-server chips. I bought an E3 awhilst back and it was DOA. Im cautious of using the latest MB and CPUs as well. Dont want to spend a bucketload an it not work. Considering I want my setup to run quite a few things at once.

Has anyone done a build with the new Intel LGA3647 chips? I was intending to do an X99 2011-3 E5 build however the buy prices per items are roughly equivalent between the 2011-3/3647 platforms. I am currently looking at a dual CPU ASUS WS C621E Sage Motherboard and a pair of Intel Xeon Silver 4114 chips.

Ahh. Thanks. Worked a charm!

I have the port on which to listen for connections set to 8081 in the Docker container. I have the content server connection on the Android client set to 10.1.2.40:8081. It reports "Cannot find Content Server". If I set the port to 8080 it reports "Cannot connect" advising a conflict with another Docker container. My container port mappings are: 8080/tcp - 10.1.2.40:9080 8081/tcp - 10.1.2.40:9081 I cant set the Docker container to 8080, I already have a container utilising 8080 and it reports the conflict.

I changed the connection settings in Calibre Companion to: 10.1.2.40:9081 That does not work. Calibre companion reports "Cannot find Content Server". The calibre error log, on the docker application, is reporting: Failed to bind to 10.1.2.40 with error: No socket could be created -- (('10.1.2.40', 9080): [Errno 99] Cannot assign requested address). Trying to bind to the default interface: 172.17.0.9 instead calibre server listening on 172.17.0.9 port 9080 OPDS feeds advertised via Bonjour at: 172.17.0.9 port: 9080 calibre server listening on 0.0.0.0:9080 I am able to connect Calibre Companion to Calibre running on a Windows 10 PC but not to the Docker application.

Thank you for your response. Calibre is displaying the content server on 172.17.0.9 port 9080. My Docker port mappings are: 8080/tcp 10.1.2.40:9080 8081/tcp 10.1.2.40:9081 In Calibre Companion (Android) I have configured the Content server connection as: Content Server IP Address IP 10.1.2.40 Port 9080 When I select Connect - to Content Server, from the Companion menu I receive the message displayed in the image.

I cant seem to work out how to make Calibre available on my network. The content server is listed as 172.17.0.9:9080 My network though is in the 10.1.2.X range. How do I make it accessible to Calibre Companion from my tablet? Emailing books via cops is not very effective.

Yes. I am/was utilising jlesage/crashplan. It works fine.

I followed the instructions at the start of the thread to copy my app data folder to the Pro. I also upgraded my CrashPlan account to Pro and confirmed I can log in via the webpage. I installed the Pro container but am unable to log in. I am inserting the correct password however I keep receiving the message "Unable to sign in". I have confirmed via the Code42 webpage my account is correct. Even if I change pwd I still receive the same message.