XBMC-Server (headless/minified) Libraryscanner

There are a number of things you can do to find the issue. First ensure that you are running the correct image, it should be nicjo814/docker-kodi-headless and not nicjo814/kodi-headless. Next you could try to delete the /opt/kodi-server/share/kodi/portable_data/temp/addons_install.log within the docker container and rerun the docker exec command. Then check the addons_install.log to make sure that the watchdog plugin has been installed properly. Please let me know if you manage to fix the issue.

How get i access to the /opt/kodi-server/share/kodi/portable_data/temp/addons_install.log?

To "enter" a running container, issue the command:  docker exec -it <container id> bash This will give you a new bash shell within the container. From there you can find the log file in the place previously described.

the file /opt/kodi-server/share/kodi/portable_data/temp/addons_install.log does not exists. i retry the installation but no addons_install.log created.

@just.RooT I'm sorry, but I think I sent you in the wrong direction regarding the log file... The file is only created when the docker container is initiated with the -e KODIADDONS parameter. Could you instead open a Bash shell in the running container and see if the file /root/addon_install.php exists in there? If so issue the command: /root/addon_install.php service.watchdog within that shell and post any output here. Really sorry for giving you the wrong info before...

no problem
I hope we can solve this problem.
I get following output:

/root/addon_install.php service.watchdog
Start searching for addon service.watchdog...
Downloading addon service.watchdog from Gotham repo...
--2015-08-02 17:58:49--  http://mirrors.xbmc.org/addons/gotham/service.watchdog/service.watchdog-0.9.6.zip
Resolving mirrors.xbmc.org (mirrors.xbmc.org)... 89.16.176.16
Connecting to mirrors.xbmc.org (mirrors.xbmc.org)|89.16.176.16|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://ftp.fau.de/xbmc/addons/gotham/service.watchdog/service.watchdog-0.9.6.zip [following]
--2015-08-02 17:58:49--  http://ftp.fau.de/xbmc/addons/gotham/service.watchdog/service.watchdog-0.9.6.zip
Resolving ftp.fau.de (ftp.fau.de)... 131.188.12.211, 2001:638:a000:1021:21::1
Connecting to ftp.fau.de (ftp.fau.de)|131.188.12.211|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 114957 (112K) [application/zip]
Saving to: ‘service.watchdog-0.9.6.zip’


100%[========================================================================================================================================================================>] 114,957     --.-K/s   in 0.09s


2015-08-02 17:58:49 (1.18 MB/s) - ‘service.watchdog-0.9.6.zip’ saved [114957/114957]


Installing addon...
Addon service.watchdog successfully installed.


Start searching for addon xbmc.python...
NOTICE: Addon xbmc.python not found.

It looks fine... Could you stop/remove the container and "rerun" the image again so you get a new container when the plugin is already installed?

Could you also check within the container which version of the plugin is listed in the addon.xml file in the directory /opt/kodi-server/share/kodi/portable_data/addons/service.watchdog. It should say version 0.9.6 if installation went well...

I just got back to civilization after some hiking and realized that Kodi 15.0 final has been released. There is a new image available for this version with the tag "15.0" on my docker hub. Use docker pull nicjo814/docker-kodi-headless:15.0 to pull the latest version. As before it's based on the excellent images by sparklyballs with some minor modifications.

it wont work -.-
now i complete reinstalled the docker, and container etc.
Same issue.

Maybe it will work with Kodi 15?
i´m depressed...

That's really strange. I tested it the other day with the 14.2 image and it worked fine.. Could you try to bind-mount to a new directory to get a fresh start? It's done via the "-v" flag (the directory entered before the colon)...

By the way I did not add any settings file for the watchdog plugin, but instead let it use it's default settings.

I did the following now:
1. Install new Container with new portable_data path
2. Just add the Mysql Environment variables
3. start the container: no errors.
4. add the following files:
- mediasources.xml
- sources.xml
- passwords.xml
5. restart Container: no errors.
6. install watchdog via docker exec -t fccb0cb0c370 /root/addon_install.php service.watchdog
7. restart container: ERROR: EXCEPTION: Error: Window is NULL, this is not possible ...

Ok, I just did a new install and realized that when you don't have debug logging enabled in your advancedsettings.xml file (it's off by default) it looks like Kodi fails with that exception being thrown. However when debug logging is turned on the log keeps filling up with watchdog data (it's running). Could you test to just throw a new video file into any of the directories that the watchdog plugin monitors to see if your library updates properly?

sounds stupid, but how to upgrade to v15 if i already have a working 14.2. Do i need to delete v14.2 and download v15 and repeat all the process again?

nicjo814: Thank you! You´re right. It works , blame on me.

Other Question:
Is it possible to upgrade the database from MyVideos90 to MyVideos93? I dont wanna lose my "watched movie"-informations

so this means we have to enable logging all the time?

No, it just looks like it fails. But u can ignore the Exception. Watchdog will work anyway.

@nicjo814
Iv read that kodi v15.0 no longer support some devices specifically AppleTV 2. may I request that you keep your 14.2 repo be active.

Thanks

Zitat von rals2007

@nicjo814
Iv read that kodi v15.0 no longer support some devices specifically AppleTV 2. may I request that you keep your 14.2 repo be active.

Thanks

Sure! I have no plans to remove any of the finished images.

Since kodi with watch dog is running, omv will Not shutdown automatically (autoshutdown-plugin) , cause of nfs access. Any ideas?