• Content Count

  • Joined

  • Last visited

Everything posted by MammothJerk

  1. i emailed the unraid support as well but they said they dont support docker lol.
  2. read other issues in this subforum and found my solution && docker exec containername sh -c 'rm /storage/file.txt' So apparently this script only runs when the container is rebuilt, and not on start/restart So i'm still looking for a solution
  3. I'm trying to get a specific container to remove a file before the container is started. but i can't quite seem to get it to work running "rm /mnt/user/storage/file.txt" from outside the container in the unraid temrinal works fine, and running "rm /storage/file.txt" (where /mnt/user/storage:/storage) from inside the container console both work fine. but i cant seem to get the logic in the docker container settings. i've tried both commands in the post arguments box but neither seems to run so i'm not sure what i'm supposed to do here. Thanks!
  4. It's likely you need to change "data_units_written" to "total_LBAs_written" and add *512 to your math function. not all SSDs have the same names. you should be able to click in the data_units_written field and in the dropdown you should find a synonym
  5. i seem to have commented out the "attributes=true" flag under diskio while comparing the telegraf config of my two servers. this appears to have been the issue. i still have some issues with my SSDs though sdl and sdk are both missing some info, and sdj still has a duplicate for some reason. sdl, sdk, and sdj are all SSD's, where sdl is a mounted unassigned device whilst sdk and sdj are both part of different cache pools. I cannot find anything specifically about SSD's in the telegraf config or in the first post so im stumped. also did you get a chance to
  6. i have an issue with my smart health overview where every drive shows up twice (and my SSD cache shows up thrice) as you can see the duplicate row only has the "health ok?" info which the other row is missing, and they both have the same device id.
  7. awesome job on 1.6! 👍👍 Couple of comments i have: the installing of dalvany-image-panel seemed kinda strange, i had to install about 3 times before it actually started working even with restarts in-between. Not sure what was up with that The "array status" field $.['servers']['']['serverDetails'].arrayStatus needs to be edited to match your own server ip. Or i think the entire field can safely be changed to just $.['serverDetails'].arrayStatus i did not have to login again when i changed the vm/docker base ur
  8. If i am force rechecking hundreds of torrents some of them will sometimes start downloading for a split second EVEN THOUGH theyre PAUSED. This sometimes overwrites the already correct download with a new file and i'll have to download the entire thing again any way to fix this? when force rechecking it should NEVER start downloading if the initial state is paused.
  9. 1. I'm only using the delugevpn privoxy for sonarr. 2. and my server address is 3. sonarr and delugevpn are both running bridged. delugevpn settings: Sonarr settings With the latest delugevpn container sonarr can only connect to deluge download client if the host is set to localhost or does NOT work. Same story with the proxy under general > proxy. downgrading to the previous container i have no issues.
  10. Wait so to clarify: for dockers to make use of the delugevpn privoxy (and even the download client for radarr/sonarr/lidarr) they must have "--net=container:Binhex-DelugeVPN" in their extra parameters?
  11. I had to install the grafana-worldmap-panel and the grafana-piechart-panel for those specific panels to show up under my plex section. Just paste these 2 commands in the Grafana docker console and then restart the container 😁 grafana-cli plugins install grafana-worldmap-panel grafana-cli plugins install grafana-piechart-panel Great progress in 1.5!
  12. This seems to be it. I unplugged the Commander Pro from its USB header and started the server again and it instantly connected to the APC UPS daemon with no problem. Now the only issue i have left is not getting the relevant realtime UPS load, but as you say it's a hardware limitation so i would have to upgrade my UPS in the future 😁 Thanks a lot for your help!
  13. Whats throwing me is that other than the UPS load information not updating in realtime - NUT works without any problems. It would seem that the issue is on the software side edit: quick response 😁, ill try disconnecting iCue and get back to you
  14. im using the same cable that came in the box with the UPS so i would assume its official. Yes it is RJ45/USB
  15. root@tower:~# cat /var/log/syslog | grep "apcupsd" Oct 30 21:18:51 tower root: Starting apcupsd power management: /sbin/apcupsd Oct 30 21:18:51 tower apcupsd[12378]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded Oct 30 21:18:51 tower apcupsd[12378]: NIS server startup succeeded Oct 30 21:20:54 tower apcupsd[12378]: apcupsd exiting, signal 15 Oct 30 21:20:54 tower apcupsd[12378]: apcupsd shutdown succeeded Oct 30 21:20:56 tower apcupsd[24185]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded Oct 30 21:20:56 tower apcupsd[24185]: NIS server startup succeeded Oct 30 21:25:33
  16. Searching for "APC" in the output only shows me this line and its surrounding [ 12.676866] sda: sda1 [ 12.678857] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 12.831161] usb 3-7.1: new low-speed USB device number 8 using xhci_hcd [ 12.943735] input: HID 0557:2419 as /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7.1/3-7.1:1.0/0003:0557:2419.0003/input/input1 [ 12.946475] hid-generic 0003:051D:0002.0004: hiddev98,hidraw2: USB HID v1.10 Device [APC Back-UPS ES 700G FW:871.O3 .I USB FW:O3 ] on usb-0000:00:14.0-9/input0 [ 12.996334] hid-generic 0003:0557:2419.0003: input,h
  17. I had this issue before installing NUT, and I assumed stopping the NUT UPS tools service would be sufficient to not cause a conflict, but ive removed the NUT plugin anyway. I still have the issue even after a complete server reboot and restarting the APC UPS daemon.
  18. I'm tunneled into my network from accross the country and i'm having a weird issue trying to connect. I have 2 unraid servers on this local network both setup with a separate tunnel connection because of this specific issue. When i'm connected to server1tunnel i cannot access the deluge thinclient connection on server1, but i CAN access the deluge thinclient connection on server2. Same thing when connected to server2tunnel i cannot access the deluge thinclient connection on server2, but i CAN access it for server1. What is weird is that i can access the webUI from
  19. I have an APC Back-UPS ES 700VA connected via RJ45/USB cable to my unraid server and i am having an issue seeing its stats. When using the built in "UPS Settings" the "UPS STATUS" is stuck showing "Refreshing..." and will never show any other information. I'm not sure if there is something broken or if the firmware is corrupted or something. The weird thing is that the NUT v2 UPS plugin works as intended and show all relevant information except for the UPS load only showing when on battery power. Any ideas?
  20. aha i see. Seems like very strange behaviour to only report UPS load when disconnected, but atleast i know my UPS is not broken, thanks!
  21. Disconnecting the mains from my ups for about a minute did indeed change the shown UPS load to now 182 watts while the charge decreased to 93% any steps where to go from here? sorry for the long delay, i haven't had physical access for some time edit: When the server is on UPS power the UPS load will update in realtime together with the battery percentage this is how my grafana graph looks like to show how useless it is when i dont get the updated correct information lol, the last fluctiations are after disconnecting the mains
  22. I'm having an issue where UPS load is not updating at all. It starts out at 162W and sits there stuck even with load changes and parity checking etc. it never changes. Any idea why i'm having this problem? I would use the built-in unraid APC UPS plugin but that doesnt give me any info whatsoever, its just stuck when starting for some reason.