Problems after rolling back from 6.9.2 to 6.8.3

[kocurek7]

Hi guys,

 

due to stability problems with 6.9.2 I rolled back to 6.8.3 version.

I thought that rolling back would be easier and everything should roll back. Well it did not.

Unfortunately after rolling back I had no dockers and no CA plugin.

 

I did assign my cache drives again and dockers are back now, but

I cannot install CA plugin which requires at least version 6.9.0 of unraid.

 

So what now? Any ideas?

 

regards,

kocurek7

[Tristankin]

There is a url for the 6.8.3 compatible version.

 

https://raw.githubusercontent.com/Squidly271/community.applications/d075fda8b8337c4c6bbd0b6d1d66b80a8870d9ba/plugins/community.applications.plg

[Tristankin]

Also if you get a error saying updates are not available for your packages, add this to your go file

 

sed -i 's#@Docker-Content-Digest:\\s*\(.*\)@#\@Docker-Content-Digest:\\s*\(.*\)@i#g' /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php

 

[kocurek7]

1 hour ago, Tristankin said:

There is a url for the 6.8.3 compatible version.

 

https://raw.githubusercontent.com/Squidly271/community.applications/d075fda8b8337c4c6bbd0b6d1d66b80a8870d9ba/plugins/community.applications.plg

Thank you very much. It worked! Now I'm going to check stability of my Intel config on 6.8.3.

 

Best regards,

kocurek7

[kocurek7]

1 hour ago, Tristankin said:

Also if you get a error saying updates are not available for your packages, add this to your go file

 

sed -i 's#@Docker-Content-Digest:\\s*\(.*\)@#\@Docker-Content-Digest:\\s*\(.*\)@i#g' /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php

 

 

Well... How did you know that? 🙂

I am not so advanced user... Which go file do you mean? What is the path?

 

[Tristankin]

I know as I am another lowley intel user fighting for stability with the i915 module loaded.

from terminal

 

nano /boot/config/go

 

Paste that sed string to the end of the go file content.

[Tristankin]

You will also need to do a reboot for it to take effect, or you have to change a line of config and I can't remember how to find that one.

[kocurek7]

1 minute ago, Tristankin said:

You will also need to do a reboot for it to take effect, or you have to change a line of config and I can't remember how to find that one.

 

Thank you very much. I added that line to /boot/config/go and rebooted unraid.

 

It helped with almost all dockers, but one app - bazarr still shows update not available.

I'm attaching screenshot.

 

 

Any ideas? Maybe I should reinstall bazarr?

 

And another problem came up - Fix Common Problems is alerting about this:

Should I just ignore that warning?

 

... and in Plugins I can see big "UPDATE" button:

 

... just ignore it or try to upgrade? (which will probably fail due to unraid v. 6.8.3.

 

regards,

kocurek7

[Tristankin]

Yeah ignore and dont update, 

 

Try clicking the advanced toggle in the top right of the docker list and click force update, that might fix it?

[kocurek7]

4 minutes ago, Tristankin said:

Yeah ignore and dont update, 

 

Try clicking the advanced toggle in the top right of the docker list and click force update, that might fix it?

 

You were right. Force updating fixed it:

 

 

Thank you very much for your help.

 

regards

kocurek7

[Tristankin]

No worries. Glad to help.