Merijeek

So, I'd been running for some time without issues. I went ahead and allowed an update (no, I don't know why...) and now I can't get a connection. Log file is showing me: 2016-10-08 16:03:30,788 DEBG 'start-script' stdout output: Sat Oct 8 16:03:30 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected] Sat Oct 8 16:03:30 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Sat Oct 8 16:03:30 2016 TLS_ERROR: BIO read tls_read_plaintext error Sat Oct 8 16:03:30 2016 TLS Error: TLS object -> incoming plaintext read error Sat Oct 8 16:03:30 2016 TLS Error: TLS handshake failed Any suggestions what I've got going on here?

Well hell, that covers it. Told you it was something stupid.

Obviously I'm missing something super basic here. I'm trying to create a Win10 (and when that was an issue, Win10) VM. However, when I get to the spot in the installation where I'd format/partition I'm not seeing any available disks. I've not had luck finding a walkthrough so that I can figure out which vital step I'm missing. (Note: I've looked at the FAQ, but don't see VirtIO listed)

Hi all - I just had to wipe my dockers. Usually not a big deal, but they tend to go spastic on me after a couple weeks. Fortunately I've got my configs stored, so usually it isn't a problem. I just paste the config back into the CLI and off I go. But not now. Here's my config: docker run -d \ --cap-add=NET_ADMIN \ -p 8112:8112 \ -p 8118:8118 \ --name=delugevpn \ -v /mnt/user/Incoming:/data \ -v /mnt/user/config/delugevpn:/config \ -v /etc/localtime:/etc/localtime:ro \ -e VPN_ENABLED=yes \ -e VPN_USER= \ -e VPN_PASS= \ -e VPN_REMOTE=nl.privateinternetaccess.com \ -e VPN_PORT=1194 \ -e VPN_PROTOCOL=udp \ -e VPN_PROV=pia \ -e ENABLE_PRIVOXY=yes \ -e LAN_NETWORK=192.168.1.0/24 \ -e DEBUG=false \ -e PUID=0 \ -e PGID=0 \ binhex/arch-delugevpn I've obviously cleared my user and pass. What I'm getting in my logs as a try and fail to connect is: 2016-07-20 21:56:44,219 DEBG 'start-script' stdout output: Wed Jul 20 21:56:44 2016 SIGUSR1[soft,tls-error] received, process restarting 2016-07-20 21:56:46,238 DEBG 'start-script' stdout output: Wed Jul 20 21:56:46 2016 UDPv4 link local: [undef] Wed Jul 20 21:56:46 2016 UDPv4 link remote: [AF_INET]46.166.190.207:1194 2016-07-20 21:56:46,412 DEBG 'start-script' stdout output: Wed Jul 20 21:56:46 2016 WARNING: file 'credentials.conf' is group or others accessible 2016-07-20 21:56:46,597 DEBG 'start-script' stdout output: Wed Jul 20 21:56:46 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected] Wed Jul 20 21:56:46 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Wed Jul 20 21:56:46 2016 TLS_ERROR: BIO read tls_read_plaintext error Wed Jul 20 21:56:46 2016 TLS Error: TLS object -> incoming plaintext read error Wed Jul 20 21:56:46 2016 TLS Error: TLS handshake failed 2016-07-20 21:56:46,597 DEBG 'start-script' stdout output: Wed Jul 20 21:56:46 2016 SIGUSR1[soft,tls-error] received, process restarting 2016-07-20 21:56:48,616 DEBG 'start-script' stdout output: Wed Jul 20 21:56:48 2016 UDPv4 link local: [undef] Wed Jul 20 21:56:48 2016 UDPv4 link remote: [AF_INET]46.166.190.233:1194 2016-07-20 21:56:48,792 DEBG 'start-script' stdout output: Wed Jul 20 21:56:48 2016 WARNING: file 'credentials.conf' is group or others accessible 2016-07-20 21:56:48,970 DEBG 'start-script' stdout output: Wed Jul 20 21:56:48 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected] Wed Jul 20 21:56:48 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Wed Jul 20 21:56:48 2016 TLS_ERROR: BIO read tls_read_plaintext error Wed Jul 20 21:56:48 2016 TLS Error: TLS object -> incoming plaintext read error Wed Jul 20 21:56:48 2016 TLS Error: TLS handshake failed So...any idea what's up? And why I'm seeing a self-signed cert from Columbus Ohio? I don't have logs from before, but I'm thinking the Cleveland thing isn't normal.

Updated to 23. We'll see what happens. Did one large data move and it was fine, but it doesn't happen anywhere every time. So, we'll see.

Looks like I'm running 21, so I'll try 23 when I'm back at home. Is there a good way for me to test this afterwards other than doing a big move and see if I need to power cycle it when it freezes?

I was moving about 12GB from ShareA to ShareB. Both are located on the same unRAID server. Check back in a few minutes and find that my move is now stuck at 23%. Check the web UI and it's unresponsive. I've noticed before that when I have an issue with my server, it comes down to when I'm in the middle of a large file move. It seems to me that this is file system corruption. That's what it seems like to me, anyway. However, yesterday I went ahead and followed the XFS for Unraid6 instructions from https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS. For about 14TB of mixed-sized disks (1TB - 5TB) I didn't have a single test take more than about 3 minutes. None of them created anything in lost+found (I assume, since the folder never got created off /). So...assuming I ran xfs_repair correctly, and I believe I did, what else can I do?

So, I made it a good 10 days before it froze for me again. The only potential cause I can see is that I was doing a big file move (call it 30-40GB) from Share A to Share B. Came back in the morning all dockers were unresponsive, GUI was unresponsive, and restarting network didn't help. Powerdown went as far as me typing powerdown and advancing to the next line and that was that. Anyone have any suggestions?

See, kids? And that's why we ask questions!

Well, that'd be nice, but unfortunately I'm already on XFS. I'll run through the checks and see what I see. I'm running the tests detailed here for XFS: http://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui I start in maintenance mode. Then I click the "Check" button. And it's telling me the total size is 5TB, which is the size of my parity drive. This is still the full test, right?

So, this is probably the cause of all the docker/not docker issues I've been having. Further testing today has shown me this...I'll do my best to explain. It's odd. I've got DelugeVPN and Sickrage running. They go to /mnt/user/Incoming, which has /Completed and /Temp under it. So, I'm doing some manual file cleanup, and I'm copying a file from the /Completed folder, and, poof. Frozen. SMB is now gone, WebGUI is gone. I can't restart inetd. I telnet to the box, and try a powerdown, and when that doesn't get past the "gathering diagnostics" stage, try a shutdown -rn, which also doesn't work. Just plain running "diagnostics" sits forever. Eventually I manually power it off. Time passes, and I find that the exact same thing happens again within an hour. So, I do some more poking around. I telnet in and I do: cd /mnt ls (shows what's expected) cd user (good) cd Inc (tab) And boom, I'm done. CLI session is frozen. Checking the /mnt/disk[1/2/3/4] folders, it seems that Completed only exists on disk3 and disk4. I've been suspicious of Disk3 for a while, because it tends to run hot, but that doesn't mean the issue isn't Disk4. Has anyone got any suggestions on how to determine what my actual problem is?

All dockers quit, SMB quit, could CLI but that was it. A restart from CLI did nothing, so I ended up doing a hard reboot. System wasn't up even a day, and at the time I was running New Permissions because I'm still having an issue with files being owned by root rather than nobody. I did manage to grab a diagnostics before the reboot, however. So, that is attached. Same system as this one: https://lime-technology.com/forum/index.php?topic=49153.0 unraid-diagnostics-20160523-2148.zip

Alright, had it happen again. Server running without a hitch for just over 5 days. Then, I went to stop binhex-sickrage. After a minute I lost SMB. Sickrage wouldn't stop. Then I lost the GUI. I forgot to do the inetd restart so I eventually did a shutdown -rn because a regular shutdown and powerdown don't actually every do anything. I did manage a diagnostics and have attached it. ...and now that the reboot is complete, I've got no docker containers, according to the server. So...that's nice. Anything of interest in the syslog that anyone can see? unraid-diagnostics-20160522-2022.zip

Well, its just Docker acting funny. I think. From what I understand it should be impossible for Docker to mess up the function of the unRAID install in general. I completely blew away my docker.img and I've got it pared down to just 3 containers - PlexMediaServer, binhex-sickrage, binhex-delugevpn. I've gone two days with no blowups. So I'm going to treat it gently for a bit and see what the deal is.

Unfortunately, it's too late for that. However, Docker is still being extremely unpleasant. I've recreated it from scratch, yet somehow am unable to actually start it. It stays stopped.

According to this thread: http://lime-technology.com/forum/index.php?topic=47514.0 I apparently need to: And if you also copy config/super.dat, you'll keep your drive assignments including parity. Copying config/disk.cfg should also be safe, has disk settings. If you copy config/share.cfg and the config/shares folder, you'll keep all your share settings. If you copy config/ident.cfg and config/network.cfg, you'll keep your network settings. Is that the extent of it? It seems all you need to do is create a new bootable and copy those files back over to keep the above settings. That it? I'd like to know for sure before doing anything.

I have been having all sorts of general weirdness with my system for a while now. I've had Docker seemingly kill the WebUI, and now I'm at the point where I lose everything but ping and CLI when I'm running Deluge on a local machine with the files located on the UnRaid box. Anyway, I've seen enough weirdness that I'd like to basically default my system. I don't want to lose my disk setup, but the rest of it can go and I'll rebuild the stuff that I care about. Maybe I'll even work out what combination made things go weird. Can anyone point me to some instructions that let me default the system without causing any issues with the disk setup, assuming it's possible?

Well, it appears (For reasons I'll never know) that a reboot of the container took care of that for me. Of course, it also changed my VPN IP which caused other headaches, so I guess the solution is "don't reboot it too often". I have the feeling PIA won't give me a way to always land on the same external IP.

As far as your tracker showing connectable, is that something on their site? Or is it something that shows somewhere in Deluge? I'm looking using their site, which shows not connectable. Is there somewhere I should be checking in Deluge?

Yes, I have two seeding but I'm still not showing connectable. The only thing I'm really seeing in the log is this repeating every 5 minutes: 2016-05-15 10:25:44,757 DEBG 'deluge-script' stdout output: [info] Deluge incoming port 43265 open [info] Sleeping for 5 mins before rechecking listen interface and port (port checking is for PIA only)

Yup, I'm using nl.privateinternetaccess.com. I'm going to take a wild guess and say that's Netherlands.

Hmm. Still an issue. According the DelugeVPN I'm at 43265. Now, I believe that is that, I shouldn't need to allow anything over on the PIA portal or anything. So...should that be that? Or is there a step I'm missing? According to my tracker I'm not connectable, and according to http://www.yougetsignal.com/tools/open-ports/ my PIA's IP isn't available at that port.

Check the log. Right. My wife is right, I do keep getting dumber.

Can you not set sickrage to copy the file instead of move it? I can at least do that in sonarr. I did that now, thanks for the idea. I guess it means I'll just have to manually clear them out occasionally. But still, at least they don't go away instantly.

What should be a silly simple question that I can't find an answer to... I'm using DelugeVPN with PIA - and I can't figure out where to find what port I'm forwarding, if I am forwarding one. Can anyone remind me where to look?