Something seems to be causing problems with zodbot. At 12:04 UTC Rathann mentioned in #fedora-devel that zodbot was saying <zodbot> Something blew up, please try again to commands. I could get whoami to work but not fasinfo at that time. I did a reload and after 2 minutes it responded saying it had worked. I tested and could get fasinfo
<zodbot> Something blew up, please try again
At 13:50 UTC zodbot gave me a blew up. I did a reload again which seemed to fix it. I am wondering if someone is abusing zodbot somewhere we need to look at.
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
Yeah, this looks to me like the same traceback as noted before:
ERROR 2023-04-25T09:46:41 supybot Uncaught exception in ['fasinfo']. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/fasjson_client/response.py", line 41, in __call__ call_result = self.operation(**kwargs).response().result File "/usr/lib/python3.6/site-packages/bravado/http_future.py", line 239, in response six.reraise(*sys.exc_info()) File "/usr/lib/python3.6/site-packages/six.py", line 693, in reraise raise value File "/usr/lib/python3.6/site-packages/bravado/http_future.py", line 200, in response swagger_result = self._get_swagger_result(incoming_response) File "/usr/lib/python3.6/site-packages/bravado/http_future.py", line 124, in wrapper return func(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/bravado/http_future.py", line 303, in _get_swagger_result self.request_config.response_callbacks, File "/usr/lib/python3.6/site-packages/bravado/http_future.py", line 334, in unmarshal_response raise_on_unexpected(incoming_response) File "/usr/lib/python3.6/site-packages/bravado/http_future.py", line 408, in raise_on_unexpected raise make_http_exception(response=http_response) bravado.exception.HTTPInternalServerError: 500 INTERNAL SERVER ERROR: {"message": "Internal Server Err or"} During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/supybot/plugins/Fedora/plugin.py", line 310, in _get_person_b y_username person = self.fasjsonclient.get_user(username=username).result File "/usr/lib/python3.6/site-packages/fasjson_client/response.py", line 43, in __call__ raise APIError.from_bravado_error(e) fasjson_client.errors.APIError: Internal Server Error During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/supybot/callbacks.py", line 1552, in _callCommand self.callCommand(command, irc, msg, *args, **kwargs) File "/usr/lib/python3.6/site-packages/supybot/utils/python.py", line 90, in g f(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/supybot/callbacks.py", line 1518, in callCommand method(irc, msg, *args, **kwargs) File "/usr/lib/python3.6/site-packages/supybot/commands.py", line 1116, in newf f(self, irc, msg, args, *state.args, **state.kwargs) File "/usr/lib/python3.6/site-packages/supybot/plugins/Fedora/plugin.py", line 707, in fasinfo person = self._get_person_by_username(irc, name) File "/usr/lib/python3.6/site-packages/supybot/plugins/Fedora/plugin.py", line 317, in _get_person_by_username self.log.error(e) File "/usr/lib64/python3.6/logging/__init__.py", line 1337, in error self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.6/site-packages/supybot/log.py", line 88, in _log msg = format(msg, *args) File "/usr/lib/python3.6/site-packages/supybot/utils/str.py", line 631, in format return _formatRe.sub(sub, s) TypeError: expected string or bytes-like object ERROR 2023-04-25T09:46:41 supybot Exception id: 0x8228a
https://github.com/fedora-infra/supybot-fedora/issues/94
I mean we could keep this here to track things, but it seems like a duplication to me. ;(
@ryanlerch said he would look into it. I'll note on the upstream ticket that it's happening more.
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.