gr021857
Members
-
Joined
-
Last visited
Everything posted by gr021857
-
Hi, I've got myself into an issue where I'm getting the files do not exist errors in the VFIO-PCI Log when it is trying to bind my GPU. I upgraded to the RC1 but also made a move to use Nvidia plugin and use the GPU for Tadarr and that was all working fine. I've tried to go back to using the GPU for VMs and it won't passthrough. Looking at the VFIO log it is saying it can't adjust group ownership as the file or directory doesn't exist but looking in terminal I can see the folder and the files (3 files - 28, 29 and vfio). Not sure if this is causing the VM issue but it's the first error I can find. Loading config from /boot/config/vfio-pci.cfg BIND=0000:0a:00.0|10de:1c03 0000:0a:00.1|10de:10f1 --- Processing 0000:0a:00.0 10de:1c03 Vendor:Device 10de:1c03 found at 0000:0a:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:0a:00.0/iommu_group/devices/0000:0a:00.0 Binding... chown: cannot access '/dev/vfio/28': No such file or directory Error: unable to adjust group ownership of /dev/vfio/28 --- Processing 0000:0a:00.1 10de:10f1 Vendor:Device 10de:10f1 found at 0000:0a:00.1 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:0a:00.1/iommu_group/devices/0000:0a:00.1 Binding... chown: cannot access '/dev/vfio/29': No such file or directory Error: unable to adjust group ownership of /dev/vfio/29 --- vfio-pci binding complete Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Nov 3 13:47 0000:0a:00.0 -> ../../../../devices/pci0000:00/0000:00:03.1/0000:0a:00.0 lrwxrwxrwx 1 root root 0 Nov 3 13:47 0000:0a:00.1 -> ../../../../devices/pci0000:00/0000:00:03.1/0000:0a:00.1 ls -l /dev/vfio/ ls: cannot access '/dev/vfio/': No such file or directory Thank you in advance for any help
-
That's it! My ovpn file had "redirect-gateway" as an entry but it needed the "def1" part adding to the end. Added that and the latest version is connected straight away. Thank you for taking the time to figure this out and fix it really appreciated!
-
I can also confirm 100% without changing anything else just rolling back to this version "binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-2-06" the VPN connected instantly and deluge was started (log attached) @southloven I am on a pro subscription, so not core related delugevpn_log_10102020.txt
-
Damn sorry, should have checked that new server I picked from the website locations list was actually working on Windows *rookie mistake!* 😢. I've switched to a working one and confirmed it works on Windows where it connects fine. The docker isn't connecting (TLS message has gone now) it sits at the section below for half an hour then tries again and hangs in the same place, I've attached the new log file for this working server). 2020-10-09 17:36:07,569 DEBG 'start-script' stdout output: [debug] Waiting for valid local and gateway IP addresses from tunnel... 2020-10-09 17:36:07,571 DEBG 'start-script' stdout output: Fri Oct 9 17:36:07 2020 Initialization Sequence Completed 2020-10-09 18:06:46,069 DEBG 'start-script' stdout output: Fri Oct 9 18:06:46 2020 [VPN] Inactivity timeout (--ping-restart), restarting I don't know if it will help but I used the console of the delugevpn docker container whilst it is in this state and I can successfully ping google.com, the ip address of the vpn server it is trying to connect to and a local ip address all with returned pings (cut out repeat responses and left statistics): Slick server sh-5.0# ping 146.185.17.165 PING 146.185.17.165 (146.185.17.165) 56(84) bytes of data. 64 bytes from 146.185.17.165: icmp_seq=1 ttl=54 time=13.5 ms --- 146.185.17.165 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 13.466/13.472/13.479/0.006 ms Google.com sh-5.0# ping google.com PING google.com (142.250.64.78) 56(84) bytes of data. 64 bytes from lga34s30-in-f14.1e100.net (142.250.64.78): icmp_seq=1 ttl=116 time=83.0 ms --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 8154ms rtt min/avg/max/mdev = 82.213/84.800/92.661/3.961 ms Local IP sh-5.0# ping 192.168.0.15 PING 192.168.0.15 (192.168.0.15) 56(84) bytes of data. 64 bytes from 192.168.0.15: icmp_seq=1 ttl=63 time=188 ms --- 192.168.0.15 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4002ms rtt min/avg/max/mdev = 8.746/350.446/991.771/353.807 ms Thanks for your patience with this delugevpn_log_09102020_v3.txt
-
Thanks for getting back to me so quickly, I've attached a screenshot of my setup, config path on the docker, openvpn folder within it on the network drive view and then the 3 files required within it. These files have been there since February when I last changed my vpn provider, the container has been working great until this week. (I was concerned about the dates being today on the ovpn and credentials files but the docker updates those modified dates when I restart it). To be completely sure before posting this reply I've just wiped out the folder, re-downloaded the .crt, downloaded a different location server ovpn file and I'm now getting the TLS error in the newly attached log. Previously I was only seeing it occasionally but now it is repeating frequently. The TLS error refers to checking your network connection but it must have connectivity as it obtains the IP address of the VPN server in the logs? delugevpn_log_09102020_v2.txt
-
I'm having similar issues, I don't use PIA but I've not been able to connect for a few days. I can connect using my Windows PC to the same VPN server so I know their server is working. Attached debug log file, hopefully that helps. I also have the credential file warning but believe that is just a message to advise the attributes aren't set to restricted user access *Edit, this log doesn't show the TLS error message shown above but I did see it this morning before making the setting change to debug and uploading here.
