Description

I found that when I installed Scrutiny app from the catalog, that if I specified more than one disk, it would timeout when starting.

By modifying the healthcheck timeout from 5s to 10s in the yaml, then it started correctly.

Ie

```
healthcheck:
interval: 10s
retries: 30
start_period: 10s
test: >-
curl --silent --output /dev/null --show-error --fail
http://127.0.0.1:8080/api/health
timeout: 5s
```

`timeout: 5s` -> `timeout: 10s`

It seems that this timeout code is specified in the base library, in healthcheck.py,

```
class Healthcheck:
def _init_(self, render_instance: "Render"):
self._render_instance = render_instance
self._test: str | list[str] = ""
self._interval_sec: int = 10
self._timeout_sec: int = 5
self._retries: int = 30
self._start_period_sec: int = 10
self._disabled: bool = False
```

It may be that a default timeout of 5s is is too short.

When it fails, the app log shows

```
4-11-13 03:15:15.012553+00:00s6-rc: info: service s6rc-oneshot-runner: starting
2024-11-13 03:15:15.018647+00:00s6-rc: info: service s6rc-oneshot-runner successfully started
2024-11-13 03:15:15.018961+00:00s6-rc: info: service fix-attrs: starting
2024-11-13 03:15:15.025921+00:00s6-rc: info: service fix-attrs successfully started
2024-11-13 03:15:15.026223+00:00s6-rc: info: service legacy-cont-init: starting
2024-11-13 03:15:15.032061+00:00cont-init: info: running /etc/cont-init.d/01-timezone
2024-11-13 03:15:20.015043+00:00s6-rc: fatal: timed out
2024-11-13 03:15:20.019007+00:00s6-sudoc: fatal: unable to get exit status from server: Operation timed out
```

Session ID: f1d8785f-02dc-6cfc-b538-ccdb6b1b3ffd

Steps to Reproduce

None

Expected Result

None

Actual Result

None

Environment

None

Hardware Health

None

Error Message (if applicable)

Activity

Show:

Bug Clerk last week

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Stavros Kois last week

Nope, nothing changed in the last week.
I’ll close this for now, if you can reproduce it, please let me know!

Thanks

Stuart Espey last week

Hmmm, today I have been unable to reproduce. I also tried restarting, and moving the docker dataset back to a spinning rust pool.

This is the current logs…



And I note that the difference seems to be setting 01-timezone is not timing out?



vs


I wonder if anything changed in the app to fix?

Stavros Kois last week

Sorry for the delay,
I’ve been trying to reproduce, even dropped startup to 1s and timeout to 1s as well. Still starts fine.

Can you please set S6_VERBOSITY to 5 via additional environment variables.
Lets see if we can see something there.

Stuart Espey November 14, 2024 at 4:11 AM

btw, left it deploying for 2 hours. no change.

Cannot Reproduce
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Stavros Kois

Reporter

Stuart Espey

Fix versions

Time remaining

0m

Priority

Katalon Platform

Created November 13, 2024 at 4:53 AM
Updated last week
Resolved last week
Loading...