Understood. Well I can just return to the previous unRaid OS(RC), right? To do that I would just copy the files from the previous folder to the root of the USB boot drive, right?

 

Again, thanks so much for the help. I really appreciate it!

Correct

@limetech  I think this is going to wind up being a recurring issue for people  

@Squid - sorry to bother you again. 

I tried copying the files in the previous folder but I am still running 6.4.0_rc16b. I actually moved the files there instead of copying them.

 

I know this is really dumb but I forgot to do a full backup of my USB before I upgraded. Will it work if I backup the current contents of the config folder and then recreate the USB drive from a windows machine using the USB creator tool?

[mention=10290]Squid[/mention] - sorry to bother you again. [emoji20]
I tried copying the files in the previous folder but I am still running 6.4.0_rc16b. I actually moved the files there instead of copying them.
 
I know this is really dumb but I forgot to do a full backup of my USB before I upgraded. Will it work if I backup the current contents of the config folder and then recreate the USB drive from a windows machine using the USB creator tool?

Did you reboot after copying the files

Never mind. I did in fact make a backup copy before upgrading (thank god). So I have a backup copy of my USB's contents before I did the upgrade. 

 

Should I just shut the server down, unplug the USB and then replace all the files with my backup from a Windows system?

Never mind. I did in fact make a backup copy before upgrading (thank god). So I have a backup copy of my USB's contents before I did the upgrade. 
 
Should I just shut the server down, unplug the USB and then replace all the files with my backup from a Windows system?

If you choose. You only need to replace all the bz* files

Great. I moved just the BZ* files and everything is back to normal. Thanks for the help!

3 hours ago, Squid said:

thoughts @binhex?

 

@Squid well TRYING not to slope my shoulders too much here hehe, so the problem doesn't exist in 6.3.5, and only started happening in the very latest RC right? so only RC 16b is affected?. and does happen even when no VPN is involved, so its not related to the use of OpenVPN, but DOES stop happening if you switch to Host mode as opposed to Bridge mode right?. 

 

If i got all of the above correct then the finger of blame i would think points at either the kernel bump up in rc16 (bug in the kernel) or possibly the networking stack, if this has been changed (unlikely i would of thought for a RC).

 

As has been seen you CANNOT run any of my vpn docker containers in host mode, it will break your host and you will loose all connectivity if you try this, thus i have code in to prevent people doing this, so running this in host mode is out of the question as a "quick fix", i REALLY hope @limetech fixes this before official release or i am going to be a yery busy bunny telling people to roll back to 6.3.5.

 

Unfortunately i dont have a test rig and im currently using 6.3.5 so im limited as to what i can test for you guys 

interesting, i see the in the changelog for rc 16b that this includes a patch to the kernel, and this patch looks to mess with the networking stack:-

 

https://www.mail-archive.com/[email protected]/msg204727.html

 

patch is for tun/tap/bridge for virtio, whilst this is docker we are talking about not kvm, the vpn dockers do make use of the tun adapter, and of course docker is using bridge mode, co-incidence?, maybe, but it could just be a bad patch.

20 minutes ago, binhex said:

interesting, i see the in the changelog for rc 16b that this includes a patch to the kernel, and this patch looks to mess with the networking stack:-

 

https://www.mail-archive.com/[email protected]/msg204727.html

 

patch is for tun/tap/bridge for virtio, whilst this is docker we are talking about not kvm, the vpn dockers do make use of the tun adapter, and of course docker is using bridge mode, co-incidence?, maybe, but it could just be a bad patch.

 

Yeah, next release is moving to 4.14.7 where better patch from upstream is included.  Not sure if this will solve vm shutdown issues (which we never see btw).

2 hours ago, binhex said:

Unfortunately i dont have a test rig

At the time was grasping at straws, as it seemed to affect your container only...

Sorry for the delay. Do you guys need anything from me? Anything I can test to help out?

@binhex Just so you are aware I was on 6.4.0_rc14. I upgraded to 16b and the problems started a couple hours after.

8 hours ago, Tbigs2011 said:

Sorry for the delay. Do you guys need anything from me? Anything I can test to help out?

 

As it looks like Limetech will be pumping out a new RC, the only thing i would REALLY like is for you to report back when the new RC is released and let us know if this fixes the issue with docker containers running torrent clients, obviously im more concerned with any docker images ive produced :-).

19 hours ago, binhex said:

 

As it looks like Limetech will be pumping out a new RC, the only thing i would REALLY like is for you to report back when the new RC is released and let us know if this fixes the issue with docker containers running torrent clients, obviously im more concerned with any docker images ive produced :-).

 

No problem. I will be sure to post back here to le you all know.

No more traces for me on rc17b

I updated both of my unRaid systems and I am no longer having the Trace Calls. You can consider this resolved for me.