Closed dewitpj closed 3 years ago
Hm, from the logs I can't see why the system would shut down. How much memory do you assign the VM?
Can you login on the terminal and try to get the journal from the last boot?
journalctl -b -1
Hey,
I have 2gig assigned (can bump to 4 if needed) - 566 meg used according to "free". I don't have journalcrl for some reason. Is it included in the base image ?
Thanks
@dewitpj journalctl is only accessible from the OS shell, either via terminal or by using SSH to connect to the underlying OS (see https://developers.home-assistant.io/docs/operating-system/debugging).
Hi,
I got similar problem - after updating OS to 6.0 after some time host stops responding for ping on wifi connection. I configured wired connection and it looks it is available after loss of wifi.
In journal I see something strange:
Jun 16 17:21:32 home-rpi wpa_supplicant[342]: wlan0: CTRL-EVENT-DISCONNECTED bssid=76:4d:28:f9:af:97 reason=2
Jun 16 17:21:32 home-rpi wpa_supplicant[342]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
Jun 16 17:21:32 home-rpi NetworkManager[334]:
Larger journal log:
16 17:21:27 home-rpi kernel: audit: type=1325 audit(1623864087.801:184): table=nat family=2 entries=13 op=xt_replace pid=4808 subj==unconfined comm="iptables"
Jun 16 17:21:27 home-rpi audit[4809]: NETFILTER_CFG table=nat family=2 entries=14 op=xt_replace pid=4809 subj==unconfined comm="iptables"
Jun 16 17:21:28 home-rpi kernel: eth0: renamed from veth4be4a5f
Jun 16 17:21:28 home-rpi NetworkManager[334]:
After downgrading os to 5.13 everything is working well as before.
@piio
I got similar problem - after updating OS to 6.0 after some time host stops responding for ping on wifi connection.
Shutdown and disconnect from WiFi doesn't seem the same issue to me. This requires a separate issue.
I have the same issue running on a VM. HA unavailable. Strange thing however, i find that if I just hit enter in the cli, it starts working again for a short while. HA been rock solid for me up until the latest update. I am running on Oracle MV VirtualBox. Core 2021-21.6.5, supervisior-2021.6.3. Upgraded from 5.* and issue started
System Health
version: core-2021.6.5 installation_type: Home Assistant OS dev: false hassio: true docker: true virtualenv: false python_version: 3.8.9 os_name: Linux os_version: 5.10.42 arch: x86_64 timezone: Europe/London
GitHub API: ok Github API Calls Remaining: 4949 Installed Version: 1.12.4 Stage: running Available Repositories: 842 Installed Repositories: 8
can_reach_server: ok remaining_requests: 25
logged_in: true subscription_expiration: 6 July 2021, 1:00 relayer_connected: true remote_enabled: true remote_connected: true alexa_enabled: false google_enabled: true can_reach_cert_server: ok can_reach_cloud_auth: ok can_reach_cloud: failed to load: timeout
host_os: Home Assistant OS 6.0 update_channel: stable supervisor_version: supervisor-2021.06.3 docker_version: 20.10.6 disk_total: 30.8 GB disk_used: 8.8 GB healthy: true supported: true board: ova supervisor_api: ok version_api: ok installed_addons: File editor (5.3.1), ESPHome (1.18.0), Samba share (9.5.1), Terminal & SSH (9.1.3), TasmoAdmin (0.15.0), texecom2mqtt (1.0.42), Home Assistant Google Drive Backup (0.104.3), Node-RED (9.1.4)
dashboards: 4 resources: 4 views: 30 mode: storage
Update: Still losing all access to HA (local web on VM, external web, Nabu Case, tried disabling integrations, still no joy. However, I can confirm that just hitting enter at the CLI works each time and HA starts responding again for a short while.
After downgrading to 5.13, the issue is resolved
I did a manual reboot of the box and since then it's been stable - been a few days so happy to close it for me
Hardware Environment
Home Assistant OS release:
Journal logs:
journalctl not found
Kernel logs:
Description of problem:
Is the problem reproducible?
For me, yes
Has this been working before (is this a regression?)
Yes, system was stable before the upgrade
Has there been attempt to rule out hardware issues? (different SD card etc.)
No, no changes on VM/Server hosting VM