search

petio-team / petio

Petio Request, Discover, Review
https://petio.tv
MIT License
253 stars 28 forks source link

TV Show request stuck at no status #456

Closed hbooo closed 3 years ago

hbooo commented 3 years ago

Describe the bug When I try to request the tv show Panic (2021), I have an error in the docker logs and request is added with the status "no status"

To Reproduce Steps to reproduce the behavior:

  1. Go to petio home page
  2. Search for panic
  3. Request the tvshow from listing or from tv show page
  4. Request is added with no status

Expected behavior Request should be added with the correct status

Logs (node:227) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'hostname' of undefined at Sonarr.process (/app/api/services/sonarr.js:32:22) at Sonarr.get (/app/api/services/sonarr.js:72:17) at Sonarr.lookup (/app/api/services/sonarr.js:141:17) at Sonarr.addShow (/app/api/services/sonarr.js:214:31) at /app/api/requests/process.js:284:26 at Array.map (<anonymous>) at processRequest.sendToDvr (/app/api/requests/process.js:281:37) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:93:5) (node:227) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)

Desktop (please complete the following information):

Additional context Sonarr Version 3.0.6.1262 Petio Version 0.5.1-alpha

AshDyson commented 3 years ago

Thanks for the bug report. We'll look into this. I think it is something specific to your Sonarr setup as I was able to request the show without error but will continue digging and find the issue

hbooo commented 3 years ago

Thanks, let me know if you need more information

Update : I tried with Angry_Cuban13's proxy config file for sonarr and got a new error : 2021-06-09 14:30:10 error: [HPM] Error occurred while proxying request 192.168.1.96:7777/services/sonarr/paths/e5f13479-fe24-47ee-bade-daaac9ceadb2 to http://localhost:7778/ [ECONNRESET] (https://nodejs.org/api/errors.html#errors_common_system_errors)

and later in the logs : 2021-06-09 14:30:16 error: SERVICE - SONARR: [Sonarr] Unable to add series 2021-06-09 14:30:16 error: Error: Request failed with status code 400

hbooo commented 3 years ago

More info, I have this error in Sonarr : image and Profiles page in sonarr looks like this : image

ADRFranklin commented 3 years ago

I'm looking into this issue right now, I've also started experiencing it locally.

ADRFranklin commented 3 years ago

@hbooo Could you try something for me? Could you tell me if you have any custom user profiles, are they set for your user and can you try deleting them and re-creating them, and then try send a request.

hbooo commented 3 years ago

Sorry for the late answer, I only have default user profile in Petio

hbooo commented 3 years ago

Tried with a new profile in Petio (with auto approved) but still the same error in sonarr logs : `[Warn] SonarrErrorPipeline: Invalid request Validation failed:

-- LanguageProfileId: Language profile does not exist`

hbooo commented 3 years ago

Did a reinstall of Sonarr and now everything works fine. I think something went wrong when I upgraded from v2 to v3