Unable to login while long job running

[jasonlyle88]

Ombi build Version:

V 3.0.3304

Update Branch:

Open Beta

Media Sever:

Plex

Media Server Version:

1.13.0.5023

Operating System:

Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.5 LTS
Release:	14.04
Codename:	trusty

Problem Description:

I've been having troubles logging in. I've noticed that I can never log in when the job "RefreshMetadata.Start" is running in hangfire. As soon as that completes, I can log in no problem. I see no errors in the browser console, but in the network tab, I notice that the 'token/' request ('/api/v1/token/') times out with a status code 500.

Reproduction Steps:

Get the "RefreshMetadata.Start" job to run, then try logging in to ombi.

[tidusjar]

Logs?

[jasonlyle88]

Attached a link since it is too big to just paste here. As far as I can see, there is nothing about the actual login in the log. I attempted to log in twice, both times receiving a "500 Internal Server Error" on the request to "/api/v1/token".

However, everytime, as soon as the Ombi.Schedule.Jobs.Ombi.RefreshMetadata job is done, the login works perfectly fine. To ensure I am not fat-fingering the password, I copy and paste the password from a text file.

https://www.dropbox.com/s/cye9za6beevdu2q/ombi3.log?dl=0

[dshokouhi]

I am seeing similar behavior in Windows. The 500 Internal Server Error shows up for me as well.

[dshokouhi]

For me it seems like this issue started with 3.0.3185. As soon as I roll back to this version I am able to login immediately. As soon as I update to any other version after that login is not working.

[onedr0p]

Login has been very slow for me as well. Usually up to 1-1.5 minutes after I press the login in button. I also get the "Invalid username or password" alert even though I am in.

[tidusjar]

This has been massively improved in the develop branch if someone can give this a go and let me know?

[dshokouhi]

@tidusjar I noticed the develop branch is version 3.0.3328 while stable is 3.0.3330 so is the fix also in stable as well or are the changes separate? just want to be sure I use the right version :)

[tidusjar]

Yes the changes are also in stable.

…

On Thu, 17 May 2018, 6:18 pm Daniel Shokouhi, ***@***.***> wrote: @tidusjar <https://github.com/tidusjar> I noticed the develop branch is version 3.0.3328 while stable is 3.0.3330 so is the fix also in stable as well or are the changes separate? just want to be sure I use the right version :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2243 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGVaLOeDh56VJLc0u2Y97pbAXrmVCwXoks5tzbDxgaJpZM4T6etJ> .

[dshokouhi]

@tidusjar I am still unable to sign in with the same behavior where the token returns a 500 error. Rolling back to 3.0.3185 resolves this and allows me to login immediately again. Oddly enough I see a new message saying "invalid user name and password" but the same one works in 3.0.3185.

[dshokouhi]

Should we reopen this issue? Not sure if others have tried to see if its better for them or not. I still cannot login.

[gravufo]

I also have this issue on the latest stable (3.0.3330). I was unable to login (no feedback) and had to wait until the full sync was complete.

[dshokouhi]

@tidusjar thank you so much! Just wanted to confirm this is indeed fixed in the latest stable release.