Replies: 1 comment
-
After running /opt/tpot/update.sh -y we are back in business, but it a bit worrying this can brake over the weekend without a clear cause. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
Please adivse how to debug and get things running again.
Cheers,
Andre
Running a T-pot installation as a VM server for weeks it suddenly died this weekend:
Jun 13 09:03:23 loudtransaction systemd[1]: tpot.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit tpot.service has entered the 'failed' state with result 'exit-code'.
Jun 13 09:03:23 loudtransaction systemd[1]: Failed to start tpot.
░░ Subject: A start job for unit tpot.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit tpot.service has finished with a failure.
░░
░░ The job identifier is 1361 and the job result is failed.
Jun 13 09:03:23 loudtransaction systemd[1]: tpot.service: Consumed 1.648s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit tpot.service completed and consumed the indicated resources.
Beta Was this translation helpful? Give feedback.
All reactions