dalben

Members
  • Posts

    1409
  • Joined

  • Last visited

Everything posted by dalben

  1. No, never got it working but to be honest I gave up fairly quickly.
  2. Not sure if the title explains my issue well. My server randomly reboots or hard lockups every now and again (something I've been fighting for a while now, but regardless). I've noticed recently (either RC1 or RC2) that on an unsafe reboot I cannot access the server via the primary IP address (10.10.0.10), but I can via the second NIC and IP address(10.10.3.10) which is there for my docker containers. Dockers work, but anyone trying to access the server via it's hostname or primary IP fails. If I restart the server it all comes back correctly. Two diagnostics files attached, one after an unsafe reboot where I can only access the server via the eth1, and a second diagnostics after a safe reboot and the server comes back on eth0. eth0 / 10.10.0.10 is the main NIC for the server. eth1 / 10.10.3.10 is there for the docker network where each container has their own IP tdm-diagnostics-20211124-0653-PriLANup.zip tdm-diagnostics-20211124-0646PriLANdown.zip
  3. I recently swapped over from my trusty but now dead APC 650cs to an APC MODEL Back-UPS BX750MI. NET detects it fine and starts monitoring. After a few hours (twice in 24 hours), it disconnects with the following error: Nov 22 03:41:15 tdm usbhid-ups[18835]: nut_libusb_get_report: Input/Output Error. Nov 22 03:41:17 tdm usbhid-ups[18835]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Nov 22 03:41:17 tdm upsd[18990]: Data for UPS [ups] is stale - check driver Nov 22 03:41:18 tdm upsmon[18994]: Poll UPS [ups@127.0.0.1] failed - Data stale Nov 22 03:41:18 tdm upsmon[18994]: Communications with UPS ups@127.0.0.1 lost Nov 22 03:41:19 tdm usbhid-ups[18835]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Nov 22 03:41:21 tdm usbhid-ups[18835]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Nov 22 03:41:23 tdm usbhid-ups[18835]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Repeating every second or so and spamming the syslog. I pull out the USB cable and replug it in, and all works fine: Nov 22 06:04:04 tdm kernel: usb 1-8: USB disconnect, device number 5 Nov 22 06:04:08 tdm upsmon[18994]: Poll UPS [ups@127.0.0.1] failed - Data stale Nov 22 06:04:13 tdm upsmon[18994]: Poll UPS [ups@127.0.0.1] failed - Data stale Nov 22 06:04:16 tdm kernel: usb 1-8: new full-speed USB device number 6 using xhci_hcd Nov 22 06:04:16 tdm kernel: hid-generic 0003:051D:0002.0006: hiddev98,hidraw3: USB HID v1.10 Device [American Power Conversion Back-UPS BX750MI FW:295201G -302201G ] on usb-0000:00:14.0-8/input0 Nov 22 06:04:17 tdm upsd[18990]: UPS [ups] data is no longer stale Nov 22 06:04:18 tdm upsmon[18994]: Communications with UPS ups@127.0.0.1 established Until it crashes again. I moved over to the Unraid default UPS setting instead of NUT and it's now been solid without any disconnection. While I don't *need* the Network feature, it was handy to have. And I enjoyed the UPS status in the status bar. Any ideas of what could be the issue, or what I can do to resolve it? here's the UPS Details page for the UPS Settings tab
  4. OK, I deleted the lot and started again. It works with latest. Thanks. I did see these warnings come up: fpcalc could not be found. Audio fingerprinting disabled. Please upgrade to the .NET Core version of Lidarr Everything seems to work fine though
  5. I pulled down your Lidarr docker and tried to fire it up but it keeps failing on the first install. here's a copy of the log. FWIW I installed your Sonarr yesterday without any issues. ---Checking if UID: 99 matches user--- ---Checking if GID: 100 matches user--- ---Setting umask to 0000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Version Check--- ---Lidarr not found, downloading and installing v1.0.0.2255...--- ---Successfully downloaded Lidarr v1.0.0.2255--- mkdir: cannot create directory ‘/lidarr/Lidarr’: File exists tar: This does not look like a tar archive gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now ---Preparing Server--- ---Starting Lidarr--- /opt/scripts/start-server.sh: line 116: /lidarr/Lidarr/Lidarr: No such file or directory ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 0000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Version Check--- ---Lidarr not found, downloading and installing v1.0.0.2255...--- ---Successfully downloaded Lidarr v1.0.0.2255--- mkdir: cannot create directory ‘/lidarr/Lidarr’: File exists tar: This does not look like a tar archive gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now ---Preparing Server--- ---Starting Lidarr--- /opt/scripts/start-server.sh: line 116: /lidarr/Lidarr/Lidarr: No such file or directory ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 0000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Version Check--- ---Lidarr not found, downloading and installing v1.0.0.2255...--- ---Successfully downloaded Lidarr v1.0.0.2255--- mkdir: cannot create directory ‘/lidarr/Lidarr’: File exists tar: This does not look like a tar archive gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now ---Preparing Server--- ---Starting Lidarr--- /opt/scripts/start-server.sh: line 116: /lidarr/Lidarr/Lidarr: No such file or directory ---Successfully downloaded Lidarr v1.0.0.2255--- mkdir: cannot create directory ‘/lidarr/Lidarr’: File exists tar: This does not look like a tar archive gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now ---Preparing Server--- ---Starting Lidarr--- /opt/scripts/start-server.sh: line 116: /lidarr/Lidarr/Lidarr: No such file or directory ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 0000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Version Check--- ---Lidarr not found, downloading and installing v1.0.0.2255...--- ---Successfully downloaded Lidarr v1.0.0.2255--- mkdir: cannot create directory ‘/lidarr/Lidarr’: File exists tar: This does not look like a tar archive gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now
  6. I need to refine my "Doesn't work". It's not a geo block or vpn range block scenario. It's latency. I did get to some sites straight out of the box(container) eventually. But most were failing with a timeout. speedtest.net eventually loaded. Ping test of 175ms. That must be why a lot of sites were failing with a timeout. When I changed to a server closer to me (SE Asia), ping were 4ms and all of my sites loaded fine. In summary, using the Amsterdam endpoint when in SE Asia will cause some issues with websites timing out.
  7. No errors but I couldn't reach any website when wet to PIA and Wireguard. Flip it over to OpenVPN and it worked fine. This was after a couple of re-installs. I've edited my post. I wiped the container and config directory then reinstalled everything again. Same thing. All the sites I needed to reach were just timing out. I then compared the new config with the working one I had. Only difference was the wireguard server being used. I replaced the default amsterdam with one closer to me and things started working again. Pings on speedtest.net went from 175ms to 4ms. Websites are reachable.
  8. I've been struggling to get PIA and Wireguard working with this Docker. PIA's lack of an easy Wireguard config file maker has been a pain. I managed to get @binhex's PrivoxyVPN script working with PIA and Wireguard by using @Dor's PIA Wireguard config script found HERE by dumping the script generated config files into the Wireguard folder. When I try that with this container it still doesn't work. Not sure where to go from here. Openvpn works fine.
  9. For anyone struggling to get PIA & Wireguard working together with this container (as I was), Edit: Try changing the default PIA Wireguard server from Amsterdam to something closer. Firing up speedtest.net showed a ping response of 175ms. That caused most of the sites I was trying to reach to timeout and fail. I'm not sure if there is a cleaner way to do it but I ended up editing the wg0.conf file manually and replacing the amsterdam server with one closer to me. Seems to be working a lot better now.
  10. Hi, tried running it and hit an error ./get_region.sh: line 242: ./setup_wireguard_with_token.sh: Permission denied This was after it auto-selected the nearest server for me Edit: Made it executable and all good now.
  11. Thanks. Yes, I've looked at the others but this offers 2 way syncing natively which the others don't seem to do.
  12. There's a bit of talk about 2-way synching for rclone online. There doesn't seem to be much drive from the rclone devs but there are a couple of add-on scripts to rclone that can achieve 2-way. Don't waste too much time on a fix though, my use case is probably an edge case.
  13. My use case is where 3 people share a OneDrive on laptops and mobiles, where as I am fixated on saving to my unraid server. Hence the need for 2 way syncing between unraid and OneDrive. Dropbox and Gmail are just additional backups
  14. OK, not me then. Thanks. I did think of adding another share name so that /data and /media are the same directory. But I since realised rclone only offers 1-way sync to that doesn't address what I need. I might still use it for 1-way synching for Google Drive and Dropbox. https://hub.docker.com/r/driveone/onedrive This looks like it has 2-way synching for OneDrive, but trying to get it working in UnRaid has proven beyond my capabilities.
  15. rclone is great, but offers only 1-way sync, which doesn't meet my requirements. I found a dedicated OneDrive sync tool that offers two-way sync. https://github.com/abraunegg/onedrive/blob/master/docs/Docker.md is the github page. Has anyone ported this container to UnRaid by any chance? I tried configuring using the CA templates and failed. About as badly as when I tried to set it up using portainer.
  16. Thanks for the docker, this is very hendy. One issue I have is around the paths. Container Path: /media is /mnt/user/data RCLONE_MEDIA_SHARES is /media/testrc I am trying to setup rclone so it syncs the the /mnt/user/data/testrc directory to OneDrive:/testrc with the current setup I end up with One:Drive:/media/testrc What should the settings above be to get my desired result?
  17. Is there a way to throttle this app so it doesn't max out a core? I am having random hard lockups and while I have no evidence that it's urbackup, I would like to stop it maxxing out cores to see if that makes a difference
  18. I got the following error from logrotate last night mcelog:6 keyword 'size' not properly separated, found 0x3d Quick Google led me to this page which pointed to logrotate 3.18.1 , which is in Unraid 6.1- RC1, being the culprit.
  19. I get the following error no matter what version I try to use. Has anyone seen it or know how to get around it? Internet bandwidth test started Warning: simplexml_load_file(): /boot/config/plugins/speedtest/speedtest.xml:1: parser error : Document is empty in /usr/local/emhttp/plugins/speedtest/scripts/speedtest-xml on line 59 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/speedtest/scripts/speedtest-xml on line 59 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/speedtest/scripts/speedtest-xml on line 59 Fatal error: Uncaught Error: Call to a member function addChild() on bool in /usr/local/emhttp/plugins/speedtest/scripts/speedtest-xml:60 Stack trace: #0 {main} thrown in /usr/local/emhttp/plugins/speedtest/scripts/speedtest-xml on line 60
  20. 3 hard lockups in 36 hours of 6.10 RC1 If no one is interested in the logs or any potential other checks or tests I'll just roll back to 6.9 Latest diagnostics attached tdm-diagnostics-20210811-1548.zip
  21. I've had two hard lockups in 12 hours since installing this release. Nothing in syslog around time of lockup. Diagnostics attached. I'll stay on this release for a bit longer in case there's a need for more info or a fix, but will need to roll back to 6.9 sooner rather than later. tdm-diagnostics-20210810-0718.zip
  22. After reading most threads here and on the interweb that seemed relevant, I'm still unsure if what I want to achieve is even possible. So hoping someone here knows. My unraid server as 2 NICs, eth0 and eth1. Eth1 is setup on a separate vlan and is bridged (br1) with all dockers having their own IP address on the br1 bridge. Is it possible to route all internet traffic on the vlan/br1/eth1/second NIC through a Wireguard tunnel to my VPN provider? @TechMed would it be possible for you to paste screenshots of your config? You've got going what I failed at last night as part 1 of my testing
  23. Changing the repository to portainer/portainer-ce worked for me. I have 2.6.1 running now.
  24. Look at any plugins you use and see if there was an update to any around the same time as the problems started. My server started experiencing lockups last weekend. I had 3 in 4 days. Nothing at all in the syslog, server just halted. I removed a recently updated plugin and it's been stable for 2 days. I'll let it go a bit longer before claiming I found the issue. As there has been no other reports of random lockups and it's a very widely used plugin, I'm not confident to name it until I am sure. if it's been doing it from day 1 then maybe it is hardware related. My previous build would lock up at odd times. Sometimes nothing for two weeks then a few in succession, very random times and frequency. Nothing in the syslog before the lockup. It had been going on for a year or so. I finally swapped out the motherboard/CPU and RAM and replaced them with components I had in my main PC. Net result my server stopped random lockups and was stable until recently. My PC, with the old server internals, hasn't missed a beat either.