Updated and now I can't start the CP plugin.. Tried rebooting.. any ideas?

[Supa]

I really don't want to set it all up again... Not sure where to see the exact logs...

49 freenas kernel: <118>Apr 10 23:51:49 freenas nmbd[2705]: STATUS=daemon 'nmbd' finished starting up and ready to s$
Apr 10 23:51:49 freenas kernel: <118>Apr 10 23:51:49 freenas nmbd[2705]:
Apr 10 23:51:49 freenas kernel: <118>Apr 10 23:51:49 freenas nmbd[2705]: Samba name server FREENAS is now a local master browser $
Apr 10 23:51:49 freenas kernel: <118>Apr 10 23:51:49 freenas nmbd[2705]:
Apr 10 23:51:49 freenas kernel: <118>Apr 10 23:51:49 freenas nmbd[2705]: *****
Apr 10 23:51:51 freenas kernel: <118>jexec 4 /usr/pbi/transmission-amd64/control start 192.168.1.225 12346
Apr 10 23:51:51 freenas kernel: <118>jexec 4 /usr/pbi/transmission-amd64/control start 192.168.1.225 12346
Apr 10 23:51:51 freenas kernel: <118>jexec 3 /usr/pbi/sickbeard-amd64/control start 192.168.1.228 12349
Apr 10 23:51:51 freenas kernel: <118>jexec 1 /usr/pbi/couchpotato-amd64/control start 192.168.1.227 12350
Apr 10 23:51:52 freenas kernel: <118>Apr 10 23:51:52 transmission_1 transmission-daemon[10789]: UDP Failed to set receive buffer: N$
Apr 10 23:51:52 freenas kernel: <118>Apr 10 23:51:52 transmission_1 transmission-daemon[10789]: UDP Failed to set receive buffer: r$
Apr 10 23:51:52 freenas kernel: <118>jexec 2 /usr/pbi/plexmediaserver-amd64/control start 192.168.1.226 12351


It actually might be this:

"Address in use". Any idea which address this is?

 

[joeschmuck]

Did you roll back to the previous version of FreeNAS to see if that fixes it?

 

[Joshua Parker Ruehlig]

I really don't want to set it all up again... Not sure where to see the exact logs...

49 freenas kernel: <118>Apr 10 23:51:49 freenas nmbd[2705]: STATUS=daemon 'nmbd' finished starting up and ready to s$
Apr 10 23:51:49 freenas kernel: <118>Apr 10 23:51:49 freenas nmbd[2705]:
Apr 10 23:51:49 freenas kernel: <118>Apr 10 23:51:49 freenas nmbd[2705]: Samba name server FREENAS is now a local master browser $
Apr 10 23:51:49 freenas kernel: <118>Apr 10 23:51:49 freenas nmbd[2705]:
Apr 10 23:51:49 freenas kernel: <118>Apr 10 23:51:49 freenas nmbd[2705]: *****
Apr 10 23:51:51 freenas kernel: <118>jexec 4 /usr/pbi/transmission-amd64/control start 192.168.1.225 12346
Apr 10 23:51:51 freenas kernel: <118>jexec 4 /usr/pbi/transmission-amd64/control start 192.168.1.225 12346
Apr 10 23:51:51 freenas kernel: <118>jexec 3 /usr/pbi/sickbeard-amd64/control start 192.168.1.228 12349
Apr 10 23:51:51 freenas kernel: <118>jexec 1 /usr/pbi/couchpotato-amd64/control start 192.168.1.227 12350
Apr 10 23:51:52 freenas kernel: <118>Apr 10 23:51:52 transmission_1 transmission-daemon[10789]: UDP Failed to set receive buffer: N$
Apr 10 23:51:52 freenas kernel: <118>Apr 10 23:51:52 transmission_1 transmission-daemon[10789]: UDP Failed to set receive buffer: r$
Apr 10 23:51:52 freenas kernel: <118>jexec 2 /usr/pbi/plexmediaserver-amd64/control start 192.168.1.226 12351


It actually might be this:

"Address in use". Any idea which address this is?

Can you try restarting the jail.
Then show the output of 'sockstat' from the jail
Then show the output of 'service couchpotato start' from the jail

 

[Supa]

Okay so it's running.. it's just the gui won't display "on". That's why I was confused.

I ran sockstat though.

So it appears everything is fine... lol. Besides that address is already in use error.

 

[Joshua Parker Ruehlig]

Okay so it's running.. it's just the gui won't display "on". That's why I was confused.

I ran sockstat though.

So it appears everything is fine... lol. Besides that address is already in use error.

your error is in the python daemon that communicates between the freenas gui and the couchpotato jail. Sometimes restarting the jail will fix this, but obviously this didn't work in your case.