Running a query on staging datagrepper which should always return results - e.g. https://apps.stg.fedoraproject.org/datagrepper/raw?category=ci&delta=172800 - often gives an empty list, or a list where the last recorded message was two hours ago when there definitely were messages published more recently than that. Refreshing the page several times will give different results.
Trying to load a detailed message - e.g. https://apps.stg.fedoraproject.org/datagrepper/id?id=2021-305938fe-8d1f-4f50-88b3-ad3615994b11&is_raw=true&size=extra-large - often gives a "Can't reconnect until invalid transaction is rolled back" error, but sometimes works.
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
@abompard might you be able to look at this?
Sure, I restarted httpd and it seems to work fine now.
Note that /datagrepper is the "old" instance, the new code is running at /datagrepper2.
/datagrepper
/datagrepper2
Please reopen if you still have the errors.
Metadata Update from @abompard: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Not aware of the "old" / "new" distinction. From a quick look at the commit log, "new" seems to be a rewrite to Python 3 / fedora-messaging / message schemas? Is that what's going on? If so, cool.
Log in to comment on this ticket.