nodeadlykittens

Thank you, that did the trick :-)

Hi Binhex. My deluge has been running well for probably a year now but this evening it seemed to be acting up (did not seem to connect to the tracker, got errors) and there was an update for it so I updated it and now it won't start. The one error seems to be: The supervisord.log is attached. Thank you for all your work :-) supervisord_screened.log

Yeah, sorry, I am an idiot. I did not keep my carrots separate. For some reason I had forgotten that the parity is real time, the only manual thing is the control of the parity. Thank you for setting me straight. Now I actually do know more. Skickat från min iPhone med Tapatalk

I was kind afraid that would be the answer, not sure I agree with the way it works though. As we manually (scheduled is still under our control) perform parity checks I assumed the parity would be more, well, sacred I guess. But I f.ed up and thank you for the information. Skickat från min iPhone med Tapatalk

Thank you That did not however go very well I'm afraid. I tried xfs_repair -v /dev/md1 and it reported that I needed to mount it (which I can't) to replay a log and that I could try xfs_repair L. I tried xfs_repair -vL /dev/md1 and it got stuck after the most initial report. I tried adding -P to reset the log, it did and it got stuck. I tried the standard repair again and now it actually started going through some of the faces but eventually it got stuck again. Not mountable, still. I formatted it with the naive assumption that it would restore the data from parity but that does not seem to have happened. I assume I made a bobo out of something in my haste. Can I force the parity to restore the data? It is not a disaster, as it's only media and the important stuff I have on multiple storage. It is however a hassle

I lost connection to one of my shares and that it was indeed not listed in unRAID. Found this gem in syslog, any idea how to go forward would be much appreciated. /Fred

Exactly, I substituted "/mnt/cache/appdata/data" with a download share and changed the corresponding values in Deluge webgui. However much as I like my idea of neat, I prefer working which is what it is doing after restoring things to default.

I have not, I wanted to keep it neat and keep it under my "download" folder. I have now reinstalled it and readded the downloads I tried, it works a lot better now. Thank you.

I use the default, nl.privateinternetaccess.com, which should support port forwarding. Have also tried sweden with same results.

Hi. I thought I'd tighten up my torrenting using the VPN version of deluge in conjunction with PIA. I am a bit stumped though as I get deluge running but something is not running as it should. I get a few kb/s in download speeds and after a short while it stops, error. Tracker timed out. I have tried replacing the files in the openvpn directory with the ones provided by PIA but as soon as I start the container the content is replaced with the old files.