#Hello I am having an issue with the
1 messages · Page 1 of 1 (latest)
Uninstalling and reinstalling didn't fix either
Log (1/2):
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
Add-on: Studio Code Server
Fully featured Visual Studio Code (VSCode) experience integrated in the Home Assistant frontend.
Add-on version: 5.8.0
You are running the latest version of this add-on.
System: Home Assistant OS 10.3 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.6.3
Home Assistant Supervisor: 2023.06.4
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[09:57:22] INFO: Configuring timezone (Europe/London)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-user: starting
log (2/2):
s6-rc: info: service init-mysql: starting
s6-rc: info: service init-mosquitto: starting
s6-rc: info: service init-code-server: starting
s6-rc: info: service init-mysql successfully started
s6-rc: info: service init-code-server successfully started
s6-rc: info: service init-user successfully started
s6-rc: info: service code-server: starting
s6-rc: info: service code-server successfully started
[09:57:26] INFO: Starting code-server...
s6-rc: info: service init-mosquitto successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[2023-07-02T08:57:30.710Z] info Wrote default config file to ~/.config/code-server/config.yaml
[2023-07-02T08:57:33.171Z] info code-server 4.14.1 5c199629305a0b935b4388b7db549f77eae82b5a
[2023-07-02T08:57:33.178Z] info Using user-data-dir /data/vscode
[2023-07-02T08:57:33.255Z] info Using config file ~/.config/code-server/config.yaml
[2023-07-02T08:57:33.257Z] info HTTP server listening on http://0.0.0.0:1337/
[2023-07-02T08:57:33.259Z] info - Authentication is disabled
[2023-07-02T08:57:33.261Z] info - Not serving HTTPS
[2023-07-02T08:57:33.264Z] info Session server listening on /data/vscode/code-server-ipc.sock
Same here, issue started today.
I'm also using the same versions of HA Components on a Pi 4.
[12:04:38] INFO: Starting code-server...
s6-rc: info: service init-mysql successfully started
s6-rc: info: service init-mosquitto successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[2023-07-02T10:04:41.649Z] info Wrote default config file to ~/.config/code-server/config.yaml
[2023-07-02T10:04:43.318Z] info code-server 4.14.1 5c199629305a0b935b4388b7db549f77eae82b5a
[2023-07-02T10:04:43.321Z] info Using user-data-dir /data/vscode
[2023-07-02T10:04:43.392Z] info Using config file ~/.config/code-server/config.yaml
[2023-07-02T10:04:43.392Z] info HTTP server listening on http://0.0.0.0:1337/
[2023-07-02T10:04:43.393Z] info - Authentication is disabled
[2023-07-02T10:04:43.393Z] info - Not serving HTTPS
[2023-07-02T10:04:43.393Z] info Session server listening on /data/vscode/code-server-ipc.sock
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service init-mysql: stopping
s6-rc: info: service init-mosquitto: stopping
s6-rc: info: service code-server: stopping
s6-rc: info: service init-mysql successfully stopped
s6-rc: info: service init-mosquitto successfully stopped
[12:06:07] INFO: Service code-server exited with code 0 (by signal 0)
...
@signal atlas Could this be related to the Health Check Update last week?
Workaround is to disable the Watchdog
Now its working again out of a sudden
After executing the healthcheck command manually inside the container, it crashed again.