Jump to content

frakman1

Members
  • Content Count

    77
  • Joined

  • Last visited

Community Reputation

4 Neutral

About frakman1

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. @Squid Can you please tell me what docker command I could run that returns the values in the table that gets displayed when I click on "Container SIze"? I want to be able to graph the output of this data over time to see which containers are growing. I've already used the "limit-log-files" extra parameter trick but still see the docker.img file growing over time. I've tried using "docker system df -v" among others but nothing has displayed a similar table as the "Container Size" one.
  2. Ahh yes. Sorry I missed that. Thank you for the reminder. That seems to have fixed it. Now I see entries in the log and results when I search. Thank you!
  3. Thanks for the tip. I don't have any restrictive router firewalls. My UnRAID server can talk to anything on the outside. I set that variable to 'true' and re-ran it. This is what my output log file looks like:
  4. I wanted to share my settings that finally got it to work with my brand new APC UPS. I bought this unit from Amazon. It's a 1500VA BX1500M model. The settings in the above posts didn't work for me. Ironically, the most obvious ones did. Just set both cable and type to USB and it will work. I have two servers on it which is probably why the runtime is only 17 minutes. I was hoping for more. Oh well.
  5. I let it run overnight but it still doesn't find anything. I looked at the Github page. Are you able to get it to work? If so, how? How does the docker container get this giant database of torrents? Do I need to provide some run parameter or is it baked in? Do I have to place a file in the appdata fole "/mnt/user/appdata/magnetico" ? I checked and there are already three databases there "database.sqlite3 database.sqlite3-shm database.sqlite3-wal" I keep getting this:
  6. @Nord Looks promising. I installed it and logged into the WebUI but anything I search for returns nothing. I tried searching for "ubuntu" like the screenshot on the github page shows and it returned nothing too. Am I missing something?
  7. Thanks. I didn't know that it was a plugin and not part of the core feature-set
  8. Well that was easy. Thank you for the tip and insight. Much appreciated. I didn't know that clicking on the mount point let me change its name. It's working now.
  9. Remote SMB Share Won't Mount When I add a remote SMB share, the GUI walks me through the steps and lets me search for and select the Samba share on my network by "name" (not IP address). I then select the share I want from the pull down and end up with this: However, when I hit the "MOUNT" button, I get the error below. It can't find the SMB share by the name that it gave me to use: Jul 9 15:50:20 Tower unassigned.devices: Mount SMB share '//VIDEO/ContaCam' using SMB3 protocol. Jul 9 15:50:20 Tower unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_ContaCam' '//VIDEO/ContaCam' '/mnt/disks/VIDEO_ContaCam' Jul 9 15:50:20 Tower unassigned.devices: SMB3 mount failed: mount error: could not resolve address for VIDEO: Unknown error It won't let me modify it afterwards to set the IP address. To make it work, I have to delete the share, add a new SMB share and search by IP address. Except now, the location is this ugly: /mnt/disks/192.168.xxx.xxx_ContaCam Instead of the much nicer: /mnt/disks/VIDEO_ContaCam By the way, I am running version 6.8.3 of Unraid. I just updated to the latest version of this plugin (2020.07.10) and installed the 'plus' version but the error persists: This used to work a while back. I don't know what changed other than the version of Unraid. tower-diagnostics-20200709-1641.zip
  10. When I add a remote SMB share, the GUI walks me through the steps and lets me search for and select the Samba share on my network by "name" (not IP address). I then selec the share I want from the pull down and end up with this: However, when I hit the "MOUNT" button, I get the error below. It can't find the SMB share by the name that it gave me to use Jul 9 15:50:20 Tower unassigned.devices: Mount SMB share '//VIDEO/ContaCam' using SMB3 protocol. Jul 9 15:50:20 Tower unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_ContaCam' '//VIDEO/ContaCam' '/mnt/disks/VIDEO_ContaCam' Jul 9 15:50:20 Tower unassigned.devices: SMB3 mount failed: mount error: could not resolve address for VIDEO: Unknown error . It won't let me change it afterward to tell it the IP address. To make it work, I have to delete it, add a new SMB share and search by IP address. Except now, the location is this ugly: /mnt/disks/192.168.xxx.xxx_ContaCam Instead of the much nicer: /mnt/disks/VIDEO_ContaCam By the way, I am running version 6.8.3 of Unraid. This used to work when I was on the previous build, I think 6.7.2 based on this: tower-diagnostics-20200709-1641.zip
  11. Thank you. I changed it to use: system("/usr/bin/bash /boot/config/xxxx_route.sh") and that worked.
  12. @brunnels I did all that but when I restart the container, I see this error message in the unraid terminal: root@Tower:/boot/config# sh: /boot/config/xxx_route.sh: Permission denied Doing a "chmod +x filename" and even chmod 777 on the file doesn't change it. I even killed the no hup process to make sure it's really stopped but the changes won't stick. The script adds the route to 10.0.0.199 which is the IP address of the Unraid server so how is it adding a route to the container? That script actually runs on the server right? Not the container since it is doing a "docker inspect". Or is the "ip netns exec" command actually run inside the container?
  13. I found a workaround for when the krusader GUI won't start. Try launching it in incognito mode. It worked for me then. It wouldn't work at all ( I mean, ever) in normal mode.