PISTOL_CUPCAKES

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

PISTOL_CUPCAKES's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Is it possible for me to modify this container somehow to install the python requests module (and perhaps others). I'd like to write a python script that qbit calls when a torrent finishes (using the built-in run external program feature) to automate some stuff for my workflow, however I would need the requests module in order to make API calls to qbit. Any suggestions on where to start?
  2. I am also starting to suspect that this is caused by CA Backup doing its thing. I suspect it is shutting down the dockers in the middle of sonarr/radarr performing database tasks and that leaves the sqlite database in a corrupted state. Unfortunately every time I've brought it up or seen someone else bring it up, the devs just say "well corruption shouldn't ever happen in theory and it must be something wrong with your setup." Not sure what to do at this point since backups are necessary. Here's an issue on the radarr github where I requested a notification be sent when the database is corrupted (which apparently isn't possible). https://github.com/Radarr/Radarr/issues/9007
  3. I've just had this happen again on my server after about 180 days uptime so I have no idea what is causing it. Has anyone had any luck? My server became unresponsive May 2 approx 8:59 and I rebooted at 13:33. I did enable mirroring syslog to flash so I have this but it doesn't appear useful to me: May 2 05:31:40 NASsy kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8a7d9f3: link becomes ready May 2 05:31:40 NASsy kernel: docker0: port 7(veth8a7d9f3) entered blocking state May 2 05:31:40 NASsy kernel: docker0: port 7(veth8a7d9f3) entered forwarding state May 2 05:32:00 NASsy CA Backup/Restore: ####################### May 2 05:32:00 NASsy CA Backup/Restore: appData Backup complete May 2 05:32:00 NASsy CA Backup/Restore: ####################### May 2 05:32:00 NASsy CA Backup/Restore: Deleting /mnt/user/backups/AppdataBackup/[email protected] May 2 05:32:00 NASsy CA Backup/Restore: Backup / Restore Completed May 2 05:32:12 NASsy nginx: 2022/05/02 05:32:12 [error] 17190#17190: *14284161 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /admin/api.php?version HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "127.0.0.1" May 2 05:32:12 NASsy nginx: 2022/05/02 05:32:12 [error] 17190#17190: *14284163 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /admin/api.php?version HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost" May 2 07:42:45 NASsy apcupsd[14578]: Power failure. May 2 07:42:45 NASsy apcupsd[14578]: Power is back. UPS running on mains. May 2 07:42:46 NASsy apcupsd[14578]: Power failure. May 2 07:42:46 NASsy apcupsd[14578]: Power is back. UPS running on mains. May 2 07:43:02 NASsy kernel: TCP: request_sock_TCP: Possible SYN flooding on port 32033. Sending cookies. Check SNMP counters. May 2 08:33:01 NASsy kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] May 2 08:33:01 NASsy kernel: caller _nv000712rm+0x1af/0x200 [nvidia] mapping multiple BARs May 2 13:33:33 NASsy kernel: Linux version 5.10.21-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Sun Mar 7 13:39:02 PST 2021 Additionally, I thought maybe it was an out of memory issue so I wrote a script to log memory usage (free -m) every minute to a file. Seems to be plenty of memory available but this has the added benefit of knowing when the server became unresponsive: date time total used free shared buff/cache available 2022-05-02 08:57:52 32095 10222 417 1661 21455 19770 2022-05-02 08:58:52 32095 10235 398 1661 21461 19757 2022-05-02 08:59:52 32095 10245 379 1661 21470 19747
  4. Okay, no that helps. I'll check but I don't think there are any overclock settings enabled on mine. Thanks!
  5. Could you elaborate on what you changed here? I'm having a similar issue and trying to track down the cause. Weird thing is, I've had this system running for a couple years and at one time had 180+ days uptime. This just started happening in the last couple months.
  6. I'm getting a ton of "irq 16: nobody cared found on your server" from the Fix Common Problems addon and I'm not sure what to do. Any advice? nassy-diagnostics-20190702-2029.zip
  7. Hello, I'm having an issue getting Sonarr to communicate with qBittorrentvpn. Here is my qbittorrent docker logs and run command: docker run -d --name='qbittorrentvpn' --net='br0' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_8080'='8180' -e 'TCP_PORT_8999'='8999' -e 'UDP_PORT_8999'='8999' -e 'WEBUI_PORT'='8180' -e 'INCOMING_PORT'='8999' -e 'VPN_ENABLED'='yes' -e 'VPN_USERNAME'=<username> -e 'VPN_PASSWORD'=<password> -e 'LAN_NETWORK'='10.1.20.0/24' -e 'NAME_SERVERS'='8.8.8.8,8.8.4.4' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='002' -v '/mnt/user/appdata/downloads/':'/downloads':'rw' -v '/mnt/user/appdata/qbittorrentvpn':'/config':'rw' 'markusmcnugen/qbittorrentvpn' Both containers are up and running and appear to be working correctly, I just can't get sonarr to talk with qbittorrentvpn. Any ideas? I'm not sure if I'm putting in the wrong address for the Host (in the sonarr -> add client window) or if its because of the custom network for qbittorrent?
  8. I'm having a similar issue as described earlier in this post. I've installed the qbittorrent docker image from linuxserver.io and haven't touched any config settings. At the moment it is the only container I have running. When I try to navigate to the Web UI I get a completely blank page. Refreshing doesn't do anything but show the same blank page, however, clicking into the URL bar and then hitting enter loads the login prompt and from there the Web UI appears to be working as expected. I mainly use Firefox but I'm seeing the same issue in Chrome. I've tried clearing my cache and specifically allowing popups for this site. There are some errors in my container logs. That same error message just repeats endlessly. run command: Any ideas to get this working? I'd rather not have to manually click the url bar and hit enter every time I need to access the Web UI. Thanks!