tos2 panic when release cron image starts #144

Closed
opened 2022-05-01 10:15:59 +02:00 by Jef Roosens · 1 comment

When the cron image starts, it seems to first go through a few loops of crashing due to a panic with the following response:

V panic: tos2: nil string
v hash: 91a9137
C.backtrace returned less than 2 frames

This seems to be some internal error caused during the refreshing of the repos. Looking into the source code, this function is used in the JSON module so perhaps this could be the cause.

When the cron image starts, it seems to first go through a few loops of crashing due to a panic with the following response: ``` V panic: tos2: nil string v hash: 91a9137 C.backtrace returned less than 2 frames ``` This seems to be some internal error caused during the refreshing of the repos. Looking into the source code, this function is used in the JSON module so perhaps this could be the cause.
Jef Roosens added this to the 0.3.0 milestone 2022-05-01 10:15:59 +02:00
Jef Roosens added the
bug
label 2022-05-01 10:15:59 +02:00
Jef Roosens changed title from tos2 panic when release image starts to tos2 panic when release cron image starts 2022-05-01 10:16:06 +02:00

I'm not really seeing this error anymore & it's not very disruptive as long as the user has proper restarting of the containers configured, which they should.

I'm not really seeing this error anymore & it's not very disruptive as long as the user has proper restarting of the containers configured, which they should.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vieter-v/vieter#144
There is no content yet.