Portainer 1.20.r1 not starting after update to ADM 3.3

[TheSwede86]

Hello,

Running an Asustor AS5004T and after I updated to ADM 3.3 I can see that Couch and Sonarr works but Portainer and Sabnzbd stopped working, tried re-installing them to no avail.
Trying to find the log both for Portainer and Sabnzbd to easier troubleshoot and if needed upload them here, where can I find them when I have SSH:ed into my NAS?
I can't find any logs in either;
/usr/local/AppCentral/portainer/
or
/usr/local/AppCentral/sabnzbdplus

trying "start-stop.sh" in "/usr/local/AppCentral/sabnzbdplus/CONTROL" I get this;

Code: Select all

admin@AS5004T-9FDD:/volume1/.@plugins/AppCentral/sabnzbdplus/CONTROL $ sh start-stop.sh start
Performing SABnzbdplus prestartup checks at Mon May 27 19:55:48 CEST 2019...
 Creating Symbolic links for required utils... Done
crontab: must be suid to work properly
Done
Already on 'master'
Your branch is up to date with 'origin/master'.
Already up to date.
Checking out files: 100% (1848/1848), done.st........Checking out files:  95% (1768/1848)
HEAD is now at 0db7c3e Merge pull request #1580 from clinton-hall/dev
Already up to date.
 Done
Starting SABnzbdplus Done (Mon May 27 19:56:13 CEST 2019)

when doing the same for portainer (in "/usr/local/AppCentral/portainer/CONTROL") I get;

Code: Select all

admin@AS5004T-9FDD:/volume1/.@plugins/AppCentral/portainer/CONTROL $ sh start-stop.sh start
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.38/containers/json?all=1: dial unix /var/run/docker.sock: connect: permission denied
Start portainer  ...
"docker start" requires at least 1 argument.
See 'docker start --help'.

Usage:  docker start [OPTIONS] CONTAINER [CONTAINER...]

Start one or more stopped containers

Any ideas?

Best Regards - TheSwede86