EBMS Tickets

Issue Number 527
Summary [Literature] Unable to import citations
Created 2019-09-05 00:18:08
Issue Type Bug
Submitted By Juthe, Robin (NIH/NCI) [E]
Assigned To
Status Closed
Resolved 2019-09-13 14:02:29
Resolution Fixed
Path /home/bkline/backups/jira/oceebms/issue.249315
Description

I'm unable to import PMID: 30342310 and PMID: 30693488.

 

The error message for both import attempts reads:

Job status = Failure:
Request error returned by NLM(HTTP CODE 502): Unable to route request! service name: /http/service/ratecontrol dtab: base dtab: override dtab:

Comment entered 2019-09-05 07:38:31 by Kline, Bob (NIH/NCI) [C]

I filed a ticket with the NLM support center, and reported the problem directly to Nick Ide, who has been our main contact there over the years. Got an automated confirmation of the ticket submission, as well as an out-of-office reply from Nick's email account, saying he's out until Monday. Will keep you posted.

Comment entered 2019-09-05 08:44:24 by Juthe, Robin (NIH/NCI) [E]

Thanks, Bob! As you probably gleaned already, we were able to import citations during the day yesterday. I imported citations late in the afternoon, maybe around 5pm. I first noticed the problem around midnight last night.

Comment entered 2019-09-05 08:48:05 by Kline, Bob (NIH/NCI) [C]

I found someone at NLM (wasn't easy). Problem is fixed now. Please try again.

Comment entered 2019-09-05 09:00:41 by Juthe, Robin (NIH/NCI) [E]

This is great! Thank you so much!! I just verified this by importing the two citations above. Now go get back to enjoying your vacation 🙂

Comment entered 2019-09-06 09:14:29 by Juthe, Robin (NIH/NCI) [E]

Unfortunately, this issue is back. I just tried to import PMID: 30573798 and got the following error message:

Job status = Failure:

Request error returned by NLM(HTTP CODE 502): Unable to route request! service name: /http/service/ratecontrol dtab: base dtab: override dtab:

Comment entered 2019-09-06 09:24:04 by Kline, Bob (NIH/NCI) [C]

Yes, I noticed early this morning that our scheduled jobs had failed overnight again. The first time I tested, I got the failure, then subsequent times it worked. I had guessed that they had by coincidence noticed the problem at the same time I did and had fixed it, but now it looks more like intermittent gremlins. I reported the continuing problems, and they confirmed that they're scrambling to find a permanent fix.

Comment entered 2019-09-06 09:29:58 by Juthe, Robin (NIH/NCI) [E]

Thanks, Bob.

Comment entered 2019-09-06 13:30:08 by Kline, Bob (NIH/NCI) [C]

From John Gillen at NLM:

The last 502 status was returned at 9:12 AM EDT.

Please try again.

Comment entered 2019-09-06 13:35:47 by Juthe, Robin (NIH/NCI) [E]

This is working too. Thank you!

Elapsed: 0:00:00.000536