chesh Posted March 25, 2017 Share Posted March 25, 2017 (edited) I upgraded my unRAID from 6.3.0 to 6.3.1 a couple of weeks ago, but never rebooted. Fast forward to me going on vacation this week and then having a power outage back home while I'm away. Anyway, the person watching my house turned back on my server after getting home from work last night. Server boots and I can ssh into it, but the web UI, dockers, and no VMs are starting up. Anything I can do remotely, and if not, what should my next steps be when I get home? Thanks to anyone that can provide some help. Edited March 25, 2017 by chesh Fixing misspellings and version numbers Quote Link to comment
Squid Posted March 25, 2017 Share Posted March 25, 2017 post up the diagnostics Log in to a SSH session, and enter in diagnostics and upload the resulting file place on the flash drive and then we can go from there. Quote Link to comment
chesh Posted March 25, 2017 Author Share Posted March 25, 2017 See attached. Doing this all from mobile, so excuse any misspellings. tower-diagnostics-20170325-1131.zip Quote Link to comment
Squid Posted March 25, 2017 Share Posted March 25, 2017 It looks like everything is running. But I find this curious: Mar 24 21:19:37 Tower root: Fix Common Problems Version 2017.03.17 Mar 24 21:20:48 Tower root: Fix Common Problems: Error: Unable to communicate with GitHub.com Mar 24 21:20:49 Tower root: Fix Common Problems: Other Warning: Could not check for blacklisted plugins Mar 24 21:20:49 Tower root: Fix Common Problems: Other Warning: Could not perform unknown plugins installed checks can you ping -c 3 github.com Quote Link to comment
chesh Posted March 25, 2017 Author Share Posted March 25, 2017 (edited) It's almost like a route/GW doesn't exist. Considering I can use VPN to connect to my router and then SSH into the box. See below: Last login: Sat Mar 25 11:30:53 2017 from 192.168.10.2 Linux 4.9.8-unRAID. root@Tower:~# ping -c3 github.com PING github.com (10.0.0.1) 56(84) bytes of data. ^C --- github.com ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2084ms root@Tower:~# ping -c 3 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. --- 8.8.8.8 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2067ms root@Tower:~# Here's my routes, though. And, they look fine. Last login: Sat Mar 25 12:34:42 2017 from 192.168.10.2 Linux 4.9.8-unRAID. root@Tower:~# ip route |grep default default via 192.168.1.1 dev br0 root@Tower:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.1.1 0.0.0.0 UG 0 0 0 br0 loopback * 255.0.0.0 U 0 0 0 lo 172.17.0.0 * 255.255.0.0 U 0 0 0 docker0 192.168.1.0 * 255.255.255.0 U 0 0 0 br0 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 root@Tower:~# ip route default via 192.168.1.1 dev br0 127.0.0.0/8 dev lo scope link 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.34 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown root@Tower:~# Edited March 25, 2017 by chesh Quote Link to comment
Squid Posted March 25, 2017 Share Posted March 25, 2017 I'd remotely reboot your router (or have buddy cycle the power). I'm not sure if its all related or not. But it does at least *look* like everything is running fine on the server itself Quote Link to comment
chesh Posted March 25, 2017 Author Share Posted March 25, 2017 Well, sh*t, that's all it was. Thanks, Squid! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.