Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agents show EXITED in supervisorctl #438

Open
nancyc12 opened this issue Jan 9, 2025 · 1 comment
Open

Agents show EXITED in supervisorctl #438

nancyc12 opened this issue Jan 9, 2025 · 1 comment

Comments

@nancyc12
Copy link
Contributor

nancyc12 commented Jan 9, 2025

Issue

Some agents in TEL agent hosts were found to be EXITED and could not recover themselves.

ubuntu@juju-462031-0:~$ sudo supervisorctl status | grep EXITED
hp-eliteone800-g6-all-in-one-pc-c28167                        EXITED    Jan 06 11:01 AM
rpi3bp009                                                     EXITED    Jan 06 11:12 AM
rpi4b1g001                                                    EXITED    Jan 06 11:09 AM
rpi4b2g001                                                    EXITED    Jan 06 02:30 PM
rpi4b2g002                                                    EXITED    Jan 06 11:06 AM
rpi4b4g001                                                    EXITED    Jan 06 02:29 PM
rpi4b4g002                                                    EXITED    Jan 06 11:04 AM
rpi4b8g001                                                    EXITED    Jan 06 02:22 PM
rpi4b8g002                                                    EXITED    Jan 06 11:08 AM

ubuntu@juju-47ff0e-1:~$ sudo supervisorctl status | grep EXITED
rpi400001                                                      EXITED    Jan 06 02:32 PM

ubuntu@juju-ccf3c0-0:~$ sudo supervisorctl status | grep EXITED
cm3p001                                                        EXITED    Jan 06 11:21 AM
dell-precision7550-c27818                                      EXITED    Jan 09 08:29 AM
rpi400002                                                      EXITED    Jan 06 11:09 AM

Log

ubuntu@juju-462031-0:~$ sudo supervisorctl tail -f rpi4b8g002
==> Press Ctrl-C to exit <==
68c75fc38c/events (Caused by ResponseError('too many 503 error responses'))
[25-01-06 11:08:04]   ERROR: (cmd.py:32)| 'NoneType' object has no attribute 'status_code'
Traceback (most recent call last):
  File "/srv/testflinger-venv/lib/python3.10/site-packages/testflinger_agent/cmd.py", line 27, in main
    start_agent()
  File "/srv/testflinger-venv/lib/python3.10/site-packages/testflinger_agent/__init__.py", line 139, in start_agent
    agent.process_jobs()
  File "/srv/testflinger-venv/lib/python3.10/site-packages/testflinger_agent/agent.py", line 328, in process_jobs
    event_emitter.emit_event(TestEvent.CLEANUP_START)
  File "/srv/testflinger-venv/lib/python3.10/site-packages/testflinger_agent/event_emitter.py", line 55, in emit_event
    self.client.post_status_update(
  File "/srv/testflinger-venv/lib/python3.10/site-packages/testflinger_agent/client.py", line 448, in post_status_update
    % (status_update_uri, job_request.status_code)
AttributeError: 'NoneType' object has no attribute 'status_code

Workaround

Manually start each agent.

sudo supervisorctl start rpi4b8g002
Copy link

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/CERTTF-474.

This message was autogenerated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant