[Support] Linuxserver.io - Kodi-Headless


Recommended Posts

Maybe part of the issue is the terribly long influx of JSON requests:

 

06:06:52.856 T:47504899983104   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2747}]
06:06:52.856 T:47504904185600   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2746}]
06:06:52.856 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.856 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2748}]
06:06:52.862 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.862 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2749}]
06:06:52.864 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.864 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2750}]
06:06:52.868 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.868 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2751}]
06:06:52.868 T:47504904185600   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.868 T:47504904185600   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2752}]
06:06:52.869 T:47504899983104   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.869 T:47504899983104   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2753}]

And it's still running now, 3000 and counting.

Link to comment
8 hours ago, Living Legend said:

How can CP handle a Kodi database scrape and update?

 

I see how I can send a notification to Kodi so Kodi performs the scrape.  But how can CP actually perform its own scrape and DB update?

 

And without this working, what other reason do you have to run a headless Kodi?

 

Correct, CP handles notifications for single updates but no scrape.  I do that from my PC.  I assume you aren't using Krypton but Jarvis? I'm hoping Krypton works better (no more segfaults at least) than the current Jarvis.

Link to comment

Anyone else with any ideas as to why the movie library is  being overlooked on the scan, and why I'm getting the never ending 

 

06:06:52.856 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2748}]
06:06:52.862 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers

 

Link to comment
It looks like the backup plan of running a libreelec vm is going to be the new plan.

 

 

No idea why it's not working for you, working ok for me since we made the container, only difference is I use IP address rather than name in the sources.xml

 

Might be worth a shot?

 

Link to comment

Yeah, right here.

 

On 3/28/2017 at 1:12 AM, dalben said:

 The movie being overlooked has been a bug for a while.  I let CP handle that or fire up kodi on my pc and run a manual update. 

 

It used to work for me, no problems.  But then after deciding to start my library from scratch, I haven't been able to get the container to update movies.

 

Also, any ideas why I keep getting that never ending JSON request in the debug log?

 

06:06:52.856 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2748}]
06:06:52.862 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers

the id on line #1 will increment and continue

Edited by Living Legend
Link to comment
1 hour ago, Living Legend said:

Yeah, right here.

 

 

It used to work for me, no problems.  But then after deciding to start my library from scratch, I haven't been able to get the container to update movies.

 

Also, any ideas why I keep getting that never ending JSON request in the debug log?

 


06:06:52.856 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2748}]
06:06:52.862 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers

the id on line #1 will increment and continue

 

Just turned on debug logging and checked definitely scanned my movies directory.

 

18:47:17.554 T:47002372306688  NOTICE: VideoInfoScanner: Finished scan. Scanning for video info took 00:38

Things I've thought of that you may have done differently to me.

 

1.  I have no smb security on my shares

2.  I used /mnt/cache/appdata not /mnt/user/appdata

3.  I always do my initial scan on another machine then use headless to keep it updated.

Link to comment

1. I also have no security.

2. I use /mnt/user/appdata.  Why do you think this may make a difference for one source and not the other?

3. I do this as well.  My initial scan to introduce the entire library to Kodi was done on 1 PC.  Now, as movies are downloaded, they are supposed to  be updated by the headless version.  That's what I had been doing for a couple years until recently...

Link to comment
26 minutes ago, Living Legend said:

1. I also have no security.

2. I use /mnt/user/appdata.  Why do you think this may make a difference for one source and not the other?

3. I do this as well.  My initial scan to introduce the entire library to Kodi was done on 1 PC.  Now, as movies are downloaded, they are supposed to  be updated by the headless version.  That's what I had been doing for a couple years until recently...

 

Dunno, don't necessarily think it would make a difference, just trying to think the problem through, it's odd and looking at dalben's issue I think this is different.   Is it worth a reinstall?  Wondering if you've got database corruption or something?

Link to comment
17 minutes ago, CHBMB said:

 

Dunno, don't necessarily think it would make a difference, just trying to think the problem through, it's odd and looking at dalben's issue I think this is different.   Is it worth a reinstall?  Wondering if you've got database corruption or something?

 

I have done quite a few redos on the entire library, from deleting the docker, to deleting the entire library itself and rescraping.

 

Maybe I'll give it a go once more.  I'll delete everything related to the libraries and be sure to scrape everything from only one source, and then run updates from only one source.

 

Worth a shot I guess...

Link to comment
3 minutes ago, Living Legend said:

 

I have done quite a few redos on the entire library, from deleting the docker, to deleting the entire library itself and rescraping.

 

Maybe I'll give it a go once more.  I'll delete everything related to the libraries and be sure to scrape everything from only one source, and then run updates from only one source.

 

Worth a shot I guess...

Of note, I've turned off debugging now, but my log file is still growing a lot quicker than it did before.  Might try not enabling that, I'm just going to reinstall myself.  Other than the db params, you're not adding anything else to advancedsettings?

Link to comment
Just now, Living Legend said:

I'm out now, but it will be tonight's project.  You think it makes any difference what device does the initial scrape?  As long as it's not headless docker?

Not that I've noticed, I've used a couple of different clients.

Link to comment
On 28/03/2017 at 7:08 AM, Living Legend said:

Maybe part of the issue is the terribly long influx of JSON requests:

 


06:06:52.856 T:47504899983104   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2747}]
06:06:52.856 T:47504904185600   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2746}]
06:06:52.856 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.856 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2748}]
06:06:52.862 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.862 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2749}]
06:06:52.864 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.864 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2750}]
06:06:52.868 T:47504034793216   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.868 T:47504034793216   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2751}]
06:06:52.868 T:47504904185600   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.868 T:47504904185600   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2752}]
06:06:52.869 T:47504899983104   DEBUG: CWebServer[8080]: request received for /jsonrpc?Player.GetActivePlayers
06:06:52.869 T:47504899983104   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","method":"Player.GetActivePlayers","params":{},"id":2753}]

And it's still running now, 3000 and counting.

You got Yatse or some other thing hammering the webserver?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.