Unexplained increase of occurrence of "May be handled cleanly by calling instance: otherwise will result in an error" from publisher
The segment publisher on segments.ligo.org sometimes produces a message, sent by email, that looks like this:
/usr/lib/python3.6/site-packages/dqsegdb/urifunctions.py:299: UserWarning: Warning: Issue accessing URL: https://segments.ligo.org/dq/V1/DQ_SATURATION_SUSP_OR/1
warn("Warning: Issue accessing URL: %s" % url)
/usr/lib/python3.6/site-packages/dqsegdb/urifunctions.py:300: UserWarning: Code: 500
warn("Code: %s" % str(e.code))
/usr/lib/python3.6/site-packages/dqsegdb/urifunctions.py:301: UserWarning: Message: Internal Server Error
warn("Message: %s" % str(e.msg))
/usr/lib/python3.6/site-packages/dqsegdb/urifunctions.py:304: UserWarning: May be handled cleanly by calling instance: otherwise will result in an error.
warn("May be handled cleanly by calling instance: otherwise will result in an error.")
Note that this is the entire stack trace and contents of the email, not just an excerpt.
This has shown up intermittently since I started at LIGO (first email: 2018.09.28), though the details of the message sometimes vary. The message usually shows up in sets corresponding to all of or a subset of the IFOs (G,H,L,V). There were ~10 clusters in all of 2022, but there have been 5 clusters from 2023.05.24-06.01.
It would be good to figure out what causes this error and what we can do to stop it.
Edited by Robert Bruntz