V 3.0.3950
Develop
Plex
Version 1.13.9.5439
Ubuntu 18.04.1 LTS
/logs/
directory or the Admin page):2018-10-30 01:28:17.138 +00:00 [Error] StatusCode: TooManyRequests, Reason: , RequestUri: http://api.themoviedb.org/3/movie/103218?api_key=*************************************&append_to_response=videos,release_dates
2018-10-30 01:28:17.162 +00:00 [Error] Retrying RequestUri: http://api.themoviedb.org/3/movie/437667?api_key=************************************* Because we got Status Code: TooManyRequests
2018-10-30 01:28:17.172 +00:00 [Error] Retrying RequestUri: http://api.themoviedb.org/3/movie/318342?api_key=*************************************&append_to_response=videos,release_dates Because we got Status Code: TooManyRequests
2018-10-30 01:28:17.210 +00:00 [Error] Retrying RequestUri: http://api.themoviedb.org/3/movie/174209?api_key=*************************************&append_to_response=videos,release_dates Because we got Status Code: TooManyRequests
2018-10-30 01:28:17.215 +00:00 [Error] Retrying RequestUri: http://api.themoviedb.org/3/movie/17707?api_key=*************************************&append_to_response=videos,release_dates Because we got Status Code: TooManyRequests
2018-10-30 01:28:17.215 +00:00 [Error] Retrying RequestUri: http://api.themoviedb.org/3/movie/370391?api_key=************************************* Because we got Status Code: TooManyRequests
2018-10-30 01:28:17.230 +00:00 [Error] Retrying RequestUri: http://api.themoviedb.org/3/movie/103218?api_key=*************************************&append_to_response=videos,release_dates Because we got Status Code: TooManyRequests
The requests are not marked available. It also doesnt work when manually running the sync in settings.
There is no info in the log folder, i've added the log info, its only showing too many requests error, I don't think that that is the culprit.
Also I checked the Ombi.db and Plexepisode, PlexSeasonContent,PlexServerContent is completely empty.
I have no idea anymore what I can do to get it working.
All the Plex content is now in the Ombi external db
OK, found that database.
Nothing in the plex tables, although the Sonarr and Radarr tables are filled.
Is Plex actually envied the settings?
On Thu, 1 Nov 2018, 5:36 am pyto00, notifications@github.com wrote:
OK, found that database.
Nothing in the plex tables, although the Sonarr and Radarr tables are
filled.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tidusjar/Ombi/issues/2626#issuecomment-434936152, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGVaLKrYsQ7QP-kSasqZj4aRQW2iabDVks5uqohygaJpZM4YBlU6
.
Yes, plex is enabled in settings. Screenshots below
An update.
When an requested movie has been downloaded and indexed. Ombi does set its status to " available "
BUT only in the search tab.
In the Requests tab it doesnt changes the movies status automatically.
This is what I am talking about this whole time, I suddenly noticed that I was not clear about this.
This can be a feature request if this is not yet implemented.
So what you are seeing is that Ombi is probably not picking up the movie from your Plex server for some reason. Can you make sure all the metadata for the movie is correct and it's correctly matched inside Plex?
I don't know how to make it clear to you but i'll try it once more :).
So I can assume that the metadata collected by plex is correct because Ombi does pick up the movie and list it as " available" in search
But when U look at the same media in the requested list it doest mark it as available.
Here is an example:
This is a movie on the " search " page. It is marked available because it is indexed by plex already.
This is the same movie on the " requests ' page, where it is not marked as available. I have to do it manually.
I always thought that when the movie is on plex, it automatically marks the movie as available on both the " search" and "requests" page
So when it's available in the search, it means that we have picked up the status of available from Radarr (it's slightly confusing why we do this, but I was just trying it out to get multiple statuses from multiple sources). But it get marked as available (properly available) when we find the media on Plex.
Ok , So that means that there still is somethin wrong with the connection to the plex server. Correct ?
Potentially. Do you mind jumping on discord so I can investigate further?
I'll hop on discord after work today.
Any updates on this? I am seeing the exact same thing.
No update as of yet. I've been too busy to be able to look into these issues.
Have you tried the develop branch?
I just installed the develop branch and still the same. ..
I requested a movie, it sent the request to Radarr and radarr successfuly
got the movie and up into PLEX. If I search for the movie, it shows as
avail, however it is still "Processing request" in the requests tab..
On Tue, Nov 13, 2018, 5:01 PM Jamie <[email protected] wrote:
No update as of yet. I've been too busy to be able to look into these
issues.Have you tried the develop branch?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tidusjar/Ombi/issues/2626#issuecomment-438454903, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF4JQviGF08G50WYmh2SigTHWlZgJmzpks5uu0FAgaJpZM4YBlU6
.
How long did you wait? Since it's all in a job that needs to run. Go into your Plex settings and run the recently added job.
I waited overnight, and I also ran it manually, still didn't work..
:(Anything else I can try?
On Wed, Nov 14, 2018 at 1:58 PM Jamie notifications@github.com wrote:
How long did you wait? Since it's all in a job that needs to run. Go into
your Plex settings and run the recently added job.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tidusjar/Ombi/issues/2626#issuecomment-438777823, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF4JQksysWkaxIyi-T7hrQeSwoDw2Ng_ks5uvGfAgaJpZM4YBlU6
.
--
ScottB
Can you jump on discord?
sure. just got on it. Never used it before though :)
magicscott is my name
On Wed, Nov 14, 2018 at 3:03 PM Jamie notifications@github.com wrote:
Can you jump on discord?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tidusjar/Ombi/issues/2626#issuecomment-438799157, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF4JQg6P3mf8Sr4xSiC-lPAKIlPuLlziks5uvHcLgaJpZM4YBlU6
.
--
ScottB
Join the Ombi server :P
The link is on the readme (the Chat button)
ha. Got it. I'm in.
@tidusjar does it make a difference if during these sort of investigations we have folks run incognito? or does the cache not cache the stuff we are looking at here? just a thought.
It is. Strange issue. For some reason he cannot connect to Plex, I've been able to connect to his Plex server but he cannot. Still trying to work it out.
👍
I'm seeing the same issue.
Let me know if you need more specific information
Have you guys tried the develop version yet?
I am on version 3.0.3973 of develop. Issue is stillt the same.
I see that there is a new version. I'm going to update now and report back.
any updates @pyto00 ?
@goldenpipes
Currently on version 3.0.4007.
Ran the 'Recently Added Sync' to test if it would mark movies as available on the "Requests" page but it still does not.
Here is an example.
Search:
Requests:
still The same issue here as well.
On Thu, Dec 6, 2018 at 3:08 PM pyto00 notifications@github.com wrote:
@goldenpipes https://github.com/goldenpipes
Currently on version 3.0.4007.
Ran the 'Recently Added Sync' to test if it would mark movies as available
on the "Requests" page but it still does not.
Here is an example. This movie is indexed by plex and watchable.Search:
[image: search]
https://user-images.githubusercontent.com/16019397/49609006-8d8e6780-f99a-11e8-949b-c158253aa63d.PNGRequests:
[image: requests]
https://user-images.githubusercontent.com/16019397/49609175-0b527300-f99b-11e8-9e9c-babe951732ca.PNG—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tidusjar/Ombi/issues/2626#issuecomment-445012558, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF4JQqR7TjZtQMN7VUPjygGY3K7_xC44ks5u2XlIgaJpZM4YBlU6
.
--
ScottB
Same issue with me as well...
same issue
same
Same here as well
Can someone email me their ombiexternal dB and include what movie or show is missing?
So actually, I run mine in a proxmox lxc container and I stumbled upon a relevant Common Error in the Wiki...
Updating my locale to en_US.UTF-8, rebooting and running a manual sync on recently added fixed the problem on my end!
tarkah!!!! You nailed it! I don't run in proxmox. However, I updated the locale to en_US.UTF-8 and BOOM! It worked.. been trying to figure this out for over a month! tidusjar, make a note :)
My automated system is now complete!
Does anyone know how to set locale in docker? Will the docker container take a variable?
Does anyone know how to set locale in docker? Will the docker container take a variable?
Its pretty simple.
check out: http://jaredmarkell.com/docker-and-locales/
@magicscott Awesome!! I just happened to be the magical intersection of that issue and this one :)
its early in the morning for me, but my locale is set to en_US.UTF-8 and BOOM still the same problem :D
My locale is en_US.UTF-8 and I have the same problem. Movies fine. TV bad. Looks to be an API request problem. Too many lookups? API block?
2018-12-13 21:41:06.269 +01:00 [Error] StatusCode: NotFound, Reason: Not Found, RequestUri: http://api.tvmaze.com/lookup/shows?thetvdb=350300
2018-12-13 21:41:06.269 +01:00 [Error] StatusCode: NotFound, Reason: Not Found, RequestUri: http://api.tvmaze.com/lookup/shows?thetvdb=354068
2018-12-13 21:41:06.272 +01:00 [Error] StatusCode: NotFound, Reason: Not Found, RequestUri: http://api.tvmaze.com/lookup/shows?thetvdb=354539
2018-12-13 21:41:06.274 +01:00 [Error] StatusCode: NotFound, Reason: Not Found, RequestUri: http://api.tvmaze.com/lookup/shows?thetvdb=349935
2018-12-13 21:41:06.274 +01:00 [Error] StatusCode: NotFound, Reason: Not Found, RequestUri: http://api.tvmaze.com/lookup/shows?thetvdb=273836
2018-12-13 21:46:06.935 +01:00 [Error] There was no season numer 1 in Sonarr for title "The Rookie"
2018-12-13 21:48:28.471 +01:00 [Error] StatusCode: TooManyRequests, Reason: Too Many Requests, RequestUri: http://api.tvmaze.com/shows/34379/episodes
2018-12-13 21:48:28.978 +01:00 [Error] StatusCode: TooManyRequests, Reason: Too Many Requests, RequestUri: http://api.tvmaze.com/lookup/shows?thetvdb=245821
2018-12-13 21:48:28.980 +01:00 [Error] StatusCode: NotFound, Reason: Not Found, RequestUri: http://api.tvmaze.com/shows/0/episodes
2018-12-13 21:48:29.715 +01:00 [Error] StatusCode: TooManyRequests, Reason: Too Many Requests, RequestUri: http://api.tvmaze.com/search/shows?q=Amateur
2018-12-13 21:48:32.643 +01:00 [Error] Something bad happened, ErrorMiddleware caught this
Newtonsoft.Json.JsonSerializationException: Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Generic.List`1[Ombi.Api.TvMaze.Models.TvMazeEpisodes]' b ecause the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
TVMaze has this statement
API calls are rate limited to allow at least 20 calls every 10 seconds per IP address. If you exceed this rate, you might receive an HTTP 429 error. We say at least, because rate limiting takes place on the backend but not on the edge cache. So if your client is only requesting common/popular endpoints like shows or episodes (as opposed to more unique endpoints like searches or embedding), you're likely to never hit the limit. For an optimal throughput, simply let your client back off for a few seconds when it receives a 429.
So based on that, is it possible that because I have shows with TVDB IDs which "do not exist" Ombi is retying and hitting the API limit? Just a thought.
I am also running v3.0.3988
@tidusjar I can send you mine. But this counts for every movie on plex.
I request a movie
radarr grabs it
sabnzbd downloads it
plex indexes it
Done.
But Ombi doesn't get the feedback from plex to update the requested movies status.
@tidusjar @tarkah
The problem seems to be solved!
I run Ombi on Ubuntu 18.04.1 LTS
I ran the following command
sudo localectl set-locale LANG=en_IN.UTF-8
Then rebooted the server. After that I ran the full manual sync.
few seconds later my phone went crazy with notifications from Ombi, every movie has been marked as available.
So for me updating the locale to en_IN.UTF-8 solved this problem.
It doesnt have to be en_US.UTF-8 exactly. As en_IN.UTF-8 worked for me too.
That does explain a lot of the issues that I couldn't figure out!
I ran the command as suggested, rebooted and manually full sync. This did not resolve for me.
sudo localectl set-locale LANG=en_IN.UTF-8
This did not solve my issue...I am migrating to a docker image today so we will see if that resolves it.
I am on docker, and i have this issue.
OK, can someone who still has the issue email me their OmbiExternal db please?
@tidusjar I send it to you this morning (my timezone )
@bott0r Thanks, after applying the fix above can you ensure the plex server is enabled in the ombi settings, run a scan and re-send it?
@bott0r Thanks, after applying the fix above can you ensure the plex server is enabled in the ombi settings, run a scan and re-send it?
I'll give it a try..
fix applied:
root@2f184c90199f:/# locale
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8
root@2f184c90199f:/#
emby (not plex for me) restarted, ombi restarted, and run the manual cacher, no change, db sent
@bott0r
Before the fix when I ran locale it already said en_US.UTF-8 was set.
It seems that you have to re-set it to get it all working.
I swapped over to my docker instance and it now is working...so weird but glad it is fixed for me.
I'm running Ombi in a docker container, can someone explain to me how I apply this UTF-8 fix. Do I apply it in the container or on the host
open a shell, connect to your ombi container and check if the locals are already set. If not, change your container starting parameter and set them -e lang=whaterver etc.
I have the same problem, but I'm running with Emby. Versions; Ombi 3.0.4036-master and Emby 3.6.0.79 beta
Thought this might be because i'm on Emby beta and just maybe they changed the imdbid / tmdbid api urls, but this post changes things since it also happends on Plex.
Hosting environment: Production,
Content root path: /opt/ombi,
Now listening on: http://[::]:3579,
Application started. Press Ctrl+C to shut down.,
info: Ombi.Schedule.Jobs.Ombi.RefreshMetadata[0],
Starting the Metadata refresh,
info: Ombi.Schedule.Jobs.Ombi.RefreshMetadata[0],
The Media item '******' Unmasked does not have a TheMovieDbId, searching for TheMovieDbId,
I checked a few and they have both id's in place. Is this related, and can I help in any way?
@AciDCooL It's been fixed in develop for Emby
Hello,
i have still this issue, i can not set my locale. In LC_All is still nothing. Is there a way to set this?
Hello,
i have still this issue, i can not set my locale. In LC_All is still nothing. Is there a way to set this?
Why can't you set your locale ? What is keeping it from executing it ?
When i executing it nothing happend.
It seems I also have the problem on linux (using installed version in /opt)
My locale is defined and I'm using latest version of Plex :
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
what can I do to help ?
I'm also having this issue. I'm using Ubuntu 16.04.4
LANG=en_IN.UTF-8
LANGUAGE=
LC_CTYPE="en_IN.UTF-8"
LC_NUMERIC="en_IN.UTF-8"
LC_TIME="en_IN.UTF-8"
LC_COLLATE="en_IN.UTF-8"
LC_MONETARY="en_IN.UTF-8"
LC_MESSAGES="en_IN.UTF-8"
LC_PAPER="en_IN.UTF-8"
LC_NAME="en_IN.UTF-8"
LC_ADDRESS="en_IN.UTF-8"
LC_TELEPHONE="en_IN.UTF-8"
LC_MEASUREMENT="en_IN.UTF-8"
LC_IDENTIFICATION="en_IN.UTF-8"
LC_ALL=
Already tried to redefine local and reboot ?
sudo localectl set-locale LANG=en_US.UTF-8
Yes, I have tried that multiple times now. Redfined locale, rebooted, still not working.
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
This is working now. On my server I set my locale with the command "sudo localectl set-locale LANG=en_US.UTF-8" and then rebooted like was suggested (I did this 3 times before). I also re-added my Plex connection and ran a manual full sync. Ombi is now marking requests as available again! I'm not sure which actually fixed it.
I have my Ombi running in a Docker container. LC_ALL
is still undefined for me, and I cannot seem to set it:
root@cc30e04c6f0e:~# locale
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
root@cc30e04c6f0e:~# localectl set-locale LANG=en_IN.UTF-8
bash: localectl: command not found
What now?
Running in docker with the hotio Ombi docker image, all settings are at en_US.UTF-8 and still doesn't work. Do you have any recommendations on next troubleshooting steps or potential resolution?
Still an issue
Most helpful comment
I am on version 3.0.3973 of develop. Issue is stillt the same.
I see that there is a new version. I'm going to update now and report back.