v18 WebServer stopped - suddenly no remote access possible anymore
#1
Hi,

Sometimes, Yatse (my android remote control app) tells me that Kodi is offline (not reachable).

However I still can use traditional remote control (CEC) and use Kodi. So Kodi is not dead obviously.

When I then just restart Kodi GUI (it is an option in Kodi 18.2 under CoreElec 9.0.2 on my Odroid C2), after restart it works again.

I checked my log, I found following:
Quote:2019-06-24 00:02:05.788 T:4092153872  NOTICE: NFS is idle. Closing the remaining connections.
2019-06-24 20:18:43.490 T:4092153872  NOTICE: ES: Stopping event server
2019-06-24 20:18:43.492 T:4092153872  NOTICE: stopping zeroconf publishing
2019-06-24 20:18:43.503 T:4092153872  NOTICE: CWebServer[80]: Stopped
2019-06-24 20:18:43.854 T:3811349360  NOTICE: ES: UDP Event server stopped
2019-06-24 20:20:09.613 T:4092153872  NOTICE: VideoPlayer::OpenFile: nfs://192.168.178.33/Multimedia/video.mkv
2019-06-24 20:20:09.614 T:3507082096  NOTICE: Creating InputStream
2019-06-24 20:20:09.651 T:3507082096  NOTICE: Creating Demuxer
2019-06-24 20:20:09.708 T:3507082096  NOTICE: Opening stream: 0 source: 256
Out of nowhere, some services stopped suddenly (also WebServer).
Afterwards a video playback started.
-> In this situation I would assume that my boy turned on TV via traditional remote control and then started a movie also via CEC (without Yatse etc.).

So if this "CWebServer[80]: Stopped" is the reason why apps like Yatse wont work any longer, why is the WebServer stopping and why not restarting again?

Best regards
eusi

P.S. FullLog: https://pastebin.com/raw/YzN0Pzp4
Reply
#2
You should ask CoreELEC about that first
Reply
#3
(2019-06-26, 00:38)eusi Wrote: So if this "CWebServer[80]: Stopped" is the reason why apps like Yatse wont work any longer, why is the WebServer stopping and why not restarting again?
It looks like Kodi's remote control server is running on port 80.  I think this might present some kind of conflict.  Perhaps there is another server application on your system which is using the same port.  Try changing the remote control port to 8080 in System Settings / Services / Control and restart your device.  If that does not work, disable Avahi (ZeroConf) in the CoreELEC service control app, then manually enter the IP/port/login credentials in Yatse (instead of using auto detection.)  If you dont need NFS, disable that too.

text:
2018-06-22 13:11:53.031 T:4092153872 NOTICE: ADDON: os.libreelec.tv v9.0 installed
2018-06-22 13:11:53.031 T:4092153872 NOTICE: ADDON: os.openelec.tv v9.0 installed
These two items appear to be the native service control apps for OpenELEC & LibreELEC.  Without double checking, I think those would be the equivalent of
text:
service.coreelec.settings
  I believe they all perform the same function and curious why you need three apps which do the same thing.  Did you install CoreELEC on top of OpenELEC and LibreELEC ?  If you dont need the two apps above anymore, you might want to uninstall them, because they could be creating an issue.

Are you booting from a Micro SD card?  As a last resort, get a new card and install a fresh copy of CoreELEC.
Reply
#4
(2019-06-28, 23:05)MB32 Wrote:
(2019-06-26, 00:38)eusi Wrote: So if this "CWebServer[80]: Stopped" is the reason why apps like Yatse wont work any longer, why is the WebServer stopping and why not restarting again?
It looks like Kodi's remote control server is running on port 80.  I think this might present some kind of conflict.  Perhaps there is another server application on your system which is using the same port.  Try changing the remote control port to 8080 in System Settings / Services / Control and restart your device.  If that does not work, disable Avahi (ZeroConf) in the CoreELEC service control app, then manually enter the IP/port/login credentials in Yatse (instead of using auto detection.)  If you dont need NFS, disable that too.

text:
2018-06-22 13:11:53.031 T:4092153872 NOTICE: ADDON: os.libreelec.tv v9.0 installed
2018-06-22 13:11:53.031 T:4092153872 NOTICE: ADDON: os.openelec.tv v9.0 installed
These two items appear to be the native service control apps for OpenELEC & LibreELEC.  Without double checking, I think those would be the equivalent of
text:
service.coreelec.settings
  I believe they all perform the same function and curious why you need three apps which do the same thing.  Did you install CoreELEC on top of OpenELEC and LibreELEC ?  If you dont need the two apps above anymore, you might want to uninstall them, because they could be creating an issue.

Are you booting from a Micro SD card?  As a last resort, get a new card and install a fresh copy of CoreELEC. 
Hi @MB32 
Thanks for your reply!

I followed your advice. Lets see if it fixes the issue (changes port and disabled zeroconf). 

Regarding the services - actually this is a good question! Some years ago, I used openelec, later on then libreelec and since a ~year coreelec. 
Even I did a fresh install of those builds, I always used the existing config files. So for example, after I installed coreelec, I used the user-profile-backup of previously installed libreelec. I didn't know that the serivces are hiding somewhere in the user-profile.

Yeah, I will try a clean install, if it is not working with the fix. Thanks mate!
Reply
#5
Ahh, okay that explains everything.  I was puzzled by how those things got there!  It certainly is reasonable to discuss here because it does not apply to just one OS, it applies to ALL of the Kodi Linux distros with no desktop user interface.  This is something that people would have to watch out for when restoring a backup, because those system control apps are intended to run on a specific Linux distro.  This is related to the icon under Kodi's System menu on embedded Linux platforms, which is used to upgrade Kodi and to control various Linux system services.  They launch automatically when Kodi starts and that is where the problem arises:  If two different scripts or apps start the same service, the two instances might contend for the same resources.

These apps should probably be visible in /System/Addons/Running.  (At least it does for 'LibreELEC configuration').  In my opinion, the list of background/service addons should also be more easily accessible in /Addons/My addons so the user will be more likely to notice anomalies like this -- but suggestions for user interface improvements are not particularly welcome here.  I also think it would be a good idea if Kodi services that are platform-specific were located in a separate directory so they are not included by default when you perform a backup.  But a change like that would have to come in a major release because it would surely break something.

Just for reference, the Backup addon was recently updated to allow for more control of what is copied, but the user would have to know what to exclude (which in this case would be any of the things mentioned above).

https://kodi.wiki/view/Add-on:Backup
Reply

Logout Mark Read Team Forum Stats Members Help
WebServer stopped - suddenly no remote access possible anymore0