RAINMAN

Members
  • Posts

    170
  • Joined

  • Last visited

Everything posted by RAINMAN

  1. Anyone else noticing a memory leak? Pretty sure its to do with irssi but I am not sure how to fix it. Basically just need to restart the docker and it goes back down but this isnt really sustainable.
  2. Edit, close this. I created a root account to see what was being sent and it was a plex export script output. The cronjob was redirecting the output to mail instead of /dev/null
  3. Update: I managed to see the process that runs: root 16380 0.0 0.0 8936 5220 ? S 08:01 0:00 /usr/sbin/sendmail -t -oem -i But still meaningless to me.
  4. Basically in my system log every 10 mins on the 1 (11, 21, 31 etc) I get this log entry that its trying to send an email. I setup the SMTP server in notifications and tested it works fine. I changed it from one domain to another and it changes the sender address domain it tries to use but its not changing the user its using. Its setup to send from fileserver at scne but for some reason its trying to send as root. Sep 22 07:21:25 FILESERVER sSMTP[16472]: Creating SSL connection to host Sep 22 07:21:25 FILESERVER sSMTP[16472]: SSL connection using TLS_AES_256_GCM_SHA384 Sep 22 07:21:27 FILESERVER sSMTP[16472]: RCPT TO:<fileserver (AT) scne xyz> (553 5.7.1 <root at scne xyz>: Sender address rejected: not owned by user fileserver (AT) scne xyz) I removed the @'s to prevent spam bots scraping the email address. I guess I tracked it down to notifications as the place its getting some of the email details but I have no idea what would be trying to send every 10 mins and since its trying to send from an invalid email I dont know what its trying to send. Any way I can track down whats causing this?
  5. Does anyone know how to make use of autotools inside the docker? I have it creating a symbolic link to the file when its done which works fine. The issue is, that symbolic link doesnt work outside the docker since it points to a location inside the docker. ie. /data/complete Is there a way I can make the symbolic link use a different path like: /mnt/disks/unassigned/torrent/complete so that I can run my scripts outside of the docker to sort out where to permanently store the files? It seems like I can do it in the rtorrent.rc file but the scripting is not clear to me on how it works. There is a line that is kind of what I need but I wanted to change it to a symbolic link and hardcode the path /mnt/disks/unassigned/torrent/complete instead of /data/completed/ but then it isnt able to save the link since /mnt/disks/unassigned/torrent/complete doesnt exist in the docker. system.method.set_key = event.download.finished,move_complete,"execute=mv,-u,$d.get_base_path=,/data/completed/;d.set_directory=/data/completed/" Any ideas or help? Edit: I just made a bash script to do it instead of fighting with rtorrent cryptic syntax. The download finished event simply triggers a bash script to create the symlink.
  6. Having the same issue. Did you find a resolution to this?
  7. Had the same issue just recently too. Not sure what caused it as i just updated it a couple weeks back and it was fine.
  8. bingo, i had to edit the xml instead of using the form view. The port was set to -1, I assume that means auto but I changed the websocket to 5703 and then it started. Thanks.
  9. Well, the nginx error is gone but the VM still wont start. Now the error is: internal error: Failed to reserve port 5702
  10. I'm also getting all sorts of nginx errors. This is v 6.8.0. Think I'm just going to update to 6.8.1 and reboot. Jan 20 17:32:38 FILESERVER nginx: 2020/01/20 17:32:38 [alert] 5105#5105: worker process 2605 exited on signal 6 Jan 20 17:32:40 FILESERVER nginx: 2020/01/20 17:32:40 [alert] 5105#5105: worker process 2790 exited on signal 6 Jan 20 17:32:42 FILESERVER nginx: 2020/01/20 17:32:42 [alert] 5105#5105: worker process 3175 exited on signal 6 Jan 20 17:32:44 FILESERVER nginx: 2020/01/20 17:32:44 [alert] 5105#5105: worker process 3417 exited on signal 6 Jan 20 17:32:46 FILESERVER nginx: 2020/01/20 17:32:46 [alert] 5105#5105: worker process 3641 exited on signal 6 Jan 20 17:32:48 FILESERVER nginx: 2020/01/20 17:32:48 [alert] 5105#5105: worker process 3924 exited on signal 6 Jan 20 17:32:50 FILESERVER nginx: 2020/01/20 17:32:50 [alert] 5105#5105: worker process 4093 exited on signal 6
  11. I have 3 VMs running, the 4th wont start with this error. Other VMs start and stop normally. Not sure what to look at to correct this. Any ideas?
  12. So basically if I have a VPN on unraid I can't use any Dockers from outside my network? Any way to correct the routing? But then why do some remote ips work still but others not?
  13. There are no remote peers accessing unraid or dockers via vpn. Remote peers are accessing Dockers directly via external IP/port.
  14. Yes. My desktop is always connected and my phone also is mostly connected.
  15. It is a private VPN. I have 4 different VPS servers that I use for VPN. All have the same issue if I use a different one. Then again, they are all setup more or less the same but no other clients connecting to them have issues.
  16. unraid is the peer as I mentioned before. The remote VPN server has: ens3: 10.0.0.5 lo: 127.0.0.1 tun0: 10.8.0.1 wg0: 10.9.0.1 Local unraid uses: br0: 192.168.254.3 docker0: 172.17.0.1 eth0: some ipv6 address? lo: 127.0.0.1 bunch of vethxxxx: ipv6 wg0 10.9.0.6 No overlaps except the wg interfaces on both which is proper. Note, I am not using wireguard to connect from outside in. I am using it to route unraid traffic out over vpn.
  17. Those IPs are not connecting to wireguard. They are only connecting to the nginx docker via my external IP. The one is a 192.168.0.x network the other i dont know since its not mine but i doubt their internal network address would be relevant when they connect via my external public IP. The only reference to wireguard in this is that when its enabled they cant hit my dockers, when its disabled they can hit them fine. Its like a routing issue where the reply to the request is going out over the VPN instead of directly back, if that makes sense.
  18. The wireguard subnet is 10.9.0.x Local Lan is 192.168.254.x Remote IP example that doesn't work is 69.17.172.210 Remote IP example that does work is 140.238.153.159 Docker subnet 172.17.0.1?
  19. I'm still getting weirdness connecting to my dockers. From certain external IPs they can't connect at all to any of my docker services unless i disable the vpn connection. Other external Ips are working fine so i am not sure how this would get messed up?
  20. If I put by MQTT docker on a custom: br0 network and assign it an IP and port forward to that IP, then I can get my outside connection to work but all my internal connections are dead because I have to go through and re-program them all. (many are arduinos so its a PITA if I need to change the IP) Edit: it gets weirder, from a different webserver it does seem to connect fine. I'm not sure where it would be blocking traffic from that server only, and only when the VPN is enabled. Any suggestions where to look or what to look at?
  21. Ok, maybe I had some field wrong, when I go through it again from scratch it works. There is no way to set DNS though. Perhaps there can be a field for additional custom options. My VPN will try and push 10.9.0.1 as its DNS for my external devices but when I am internal to my network I want to force DNS = 192.168.254.50, 192.168.254.30. I have VPN tunneled access, yes. I am not trying to send to the VPN though. Remote server -- 1883 --> Home IP (Router) Forward to -- 1883 --> 192.168.254.3 --> MQTT Docker. I wouldn't expect the VPN to have any impact on this route? If I disable the VPN it works so somehow the VPN is blocking the connection to the local IP of my unraid box. If I use MQTT internal to my network its fine VPN on or off.
  22. I'm using wireguard to have all unraid outgoing connections go though a VPN. Pain to setup as some of the options needed wont allow. I had to export the config it generated, make the changes and import it back, and if I make any change though the UI it fails again. Either way, that's setup now but it seems like any outside data I forward through my router to a docker doesn't work. Example, I am using a MQTT docker with bridge networking. I setup port forward on my router for 1883 to unraid. It was working fine/is working fine. If I have the VPN connected I cant connect to the MQTT server from outside my network. If I turn off the VPN it works fine again. Is there something i need to do to make this work?
  23. How do you set WSD options? Also having the same issue with 100% CPU due to WSD.
  24. Ok so in my cron just add bash? * * * * * /boot/custom/influxdb/influxStats_1m_Disk.sh > /dev/null 2>&1 change to * * * * * bash /boot/custom/influxdb/influxStats_1m_Disk.sh > /dev/null 2>&1