No faktycznie się popisali Reinstalacja Systemu.
Po następnej Aktualizacji supervisor będzie to SAMO Bez tego NM można żyć
Trzeba będzie z tym żyć
Póki co nie ma wyjścia.
Edycja:
Po dzisiejszej aktualizacja Supervisora do 2024.04.4 wszystkie logi na czerwono. Możecie zerknąć co mu dolega ?
Innych negatywnych objawów w działaniu Homeassistanta nie zauważyłem.
aise HostNotSupportedError(
supervisor.exceptions.HostNotSupportedError: No systemd-journal-gatewayd Unix socket available
2024-04-30 21:05:46.664 ERROR (MainThread) [supervisor.host.logs] No systemd-journal-gatewayd Unix socket available
2024-04-30 21:05:46.664 ERROR (MainThread) [supervisor.api] Failed to get supervisor logs using advanced_logs API
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/api/__init__.py", line 404, in get_supervisor_logs
return await self._api_host.advanced_logs_handler(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/host.py", line 207, in advanced_logs_handler
async with self.sys_host.logs.journald_logs(
File "/usr/local/lib/python3.12/contextlib.py", line 210, in __aenter__
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/host/logs.py", line 143, in journald_logs
raise HostNotSupportedError(
supervisor.exceptions.HostNotSupportedError: No systemd-journal-gatewayd Unix socket available
2024-04-30 21:05:51.097 ERROR (MainThread) [supervisor.host.logs] No systemd-journal-gatewayd Unix socket available
2024-04-30 21:05:51.098 ERROR (MainThread) [supervisor.api] Failed to get supervisor logs using advanced_logs API
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/api/__init__.py", line 404, in get_supervisor_logs
return await self._api_host.advanced_logs_handler(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/host.py", line 207, in advanced_logs_handler
async with self.sys_host.logs.journald_logs(
File "/usr/local/lib/python3.12/contextlib.py", line 210, in __aenter__
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/host/logs.py", line 143, in journald_logs
raise HostNotSupportedError(
supervisor.exceptions.HostNotSupportedError: No systemd-journal-gatewayd Unix socket available
2024-04-30 21:05:52.028 ERROR (MainThread) [supervisor.host.logs] No systemd-journal-gatewayd Unix socket available
2024-04-30 21:05:52.028 ERROR (MainThread) [supervisor.api] Failed to get supervisor logs using advanced_logs API
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/api/__init__.py", line 404, in get_supervisor_logs
return await self._api_host.advanced_logs_handler(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/host.py", line 207, in advanced_logs_handler
async with self.sys_host.logs.journald_logs(
File "/usr/local/lib/python3.12/contextlib.py", line 210, in __aenter__
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/host/logs.py", line 143, in journald_logs
raise HostNotSupportedError(
supervisor.exceptions.HostNotSupportedError: No systemd-journal-gatewayd Unix socket available
2024-04-30 21:05:52.845 ERROR (MainThread) [supervisor.host.logs] No systemd-journal-gatewayd Unix socket available
2024-04-30 21:05:52.845 ERROR (MainThread) [supervisor.api] Failed to get supervisor logs using advanced_logs API
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/api/__init__.py", line 404, in get_supervisor_logs
return await self._api_host.advanced_logs_handler(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/host.py", line 207, in advanced_logs_handler
async with self.sys_host.logs.journald_logs(
File "/usr/local/lib/python3.12/contextlib.py", line 210, in __aenter__
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/host/logs.py", line 143, in journald_logs
raise HostNotSupportedError(
supervisor.exceptions.HostNotSupportedError: No systemd-journal-gatewayd Unix socket available
2024-04-30 21:05:53.511 ERROR (MainThread) [supervisor.host.logs] No systemd-journal-gatewayd Unix socket available
2024-04-30 21:05:53.512 ERROR (MainThread) [supervisor.api] Failed to get supervisor logs using advanced_logs API
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/api/__init__.py", line 404, in get_supervisor_logs
return await self._api_host.advanced_logs_handler(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/host.py", line 207, in advanced_logs_handler
async with self.sys_host.logs.journald_logs(
File "/usr/local/lib/python3.12/contextlib.py", line 210, in __aenter__
return await anext(self.gen)
Ale archeologia ;D
zrestartuj maszynę, a potem “jeździć i obserwować”
Aktualizacja Supervisora 2024.04.4 zawiera rollback, bo poprzednia wersja w specyficznych warunkach powodowała wywrotki.
Logi zrobione już po restarcie hosta.
To zgłoś issue
-
Krótki opis problemu, jeśli nie ma innych objawów to błędy w logach stanowią podstawę.
-
podsumowanie instalacji (tak jak jest, bo już jest sformatowane)
https://forum.arturhome.pl/t/jak-podzielic-sie-informacjami-o-swojej-instalacji-home-assistant-na-forum-lub-githubie/11366/ -
logi (formatowanie markdown)
Przypadkowo zauważyłem, że jednak błędy supervisora mają wpływ na HA.
Mianowicie nie można odczytać logów dodatków, pojawia się komunikat:
Nie udało się uzyskać logów dodatku, No systemd-journal-gatewayd Unix socket available
Logowanie zostało mocno zmienione - jaką masz wersję HA core?
Zgłosiłeś issue?
Mam dwie maszyny, na pierwszej core-2024.4.4, na drugiej core-2024.5.1.
Na obu ten same objawy.
Issue jeszcze nie zgłaszałem, nigdy tego nie robiłem, ale ten pierwszy raz musi kiedyś być
Gdzieś czytałem, że aktualizacja Debiana 11 do 12 pomaga w tym problemie. Jest taka możliwość ?
Niestety miałem ten sam problem brak logów i błąd No systemd-journal-gatewayd Unix socket available
Deb11
Krok 1, ewentualnie krok 2.
https://community.home-assistant.io/t/installing-home-assistant-supervised-using-debian-12/200253
Lub: krok 1 ewentualnie krok 2
https://github.com/home-assistant/supervised-installer
Należy wykonać kopie i pobrać ją w razie czego.
Przydatne komendy
ha core check
ha core info
ha core logs
ha core options
ha core rebuild
ha core restart
ha core start
ha core stats
ha core stop
ha core update
SUPERVISOR
ha supervisor info
ha supervisor logs
ha supervisor reload
ha supervisor update
HOST
ha host reboot
ha host shutdown
ha host update
HARDWARE
```sudo```
ha hardware info
ha hardware audio
docker stop hassio_supervisor
docker start homeassistant
Należy też zaktualizować docker z poziomy konsoli deb.
Widzę, że to grubsza robota
W opisie stoi:
Ta metoda jest uważana za zaawansowaną i powinna być używana tylko wtedy, gdy jest się ekspertem w zarządzaniu systemem operacyjnym Linux, Dockerem i siecią.
Nie wiem czy podołam, ale zaryzykuję na maszynie testowej.
Widzę, że łatwiejszym sposobem jest metoda z linka pierwszego - sekcja druga:
Czyli w tym przypadku jest aktualizacja agenta OS i Dockera. Czy jest potrzeba wykonywania sekcji 3 ?
Nigdy jej nie wykonywałem.
Edit.
Po wydaniu komendy w CLI:
apt install systemd-journal-remote -y
pojawiają się w logach takie błędy, czego one dotyczą ?
Err:3 http://ftp.us.debian.org/debian testing/main amd64 systemd-timesyncd amd64 255.4-1
404 Not Found [IP: 64.50.233.100 80]
Err:4 http://ftp.us.debian.org/debian testing/main amd64 libsystemd-shared amd64 255.4-1
404 Not Found [IP: 64.50.233.100 80]
Err:5 http://ftp.us.debian.org/debian testing/main amd64 libudev1 amd64 255.4-1
404 Not Found [IP: 64.50.233.100 80]
Err:6 http://ftp.us.debian.org/debian testing/main amd64 systemd amd64 255.4-1
404 Not Found [IP: 64.50.233.100 80]
Err:7 http://ftp.us.debian.org/debian testing/main amd64 udev amd64 255.4-1
404 Not Found [IP: 64.50.233.100 80]
Err:8 http://ftp.us.debian.org/debian testing/main amd64 systemd-dev all 255.4-1
404 Not Found [IP: 64.50.233.100 80]
Err:9 http://ftp.us.debian.org/debian testing/main amd64 libpam-systemd amd64 255.4-1
404 Not Found [IP: 64.50.233.100 80]
Err:10 http://ftp.us.debian.org/debian testing/main amd64 libsystemd0 amd64 255.4-1
404 Not Found [IP: 64.50.233.100 80]
Err:11 http://ftp.us.debian.org/debian testing/main amd64 dbus amd64 1.14.10-4
404 Not Found [IP: 64.50.233.100 80]
Err:12 http://ftp.us.debian.org/debian testing/main amd64 libdbus-1-3 amd64 1.14.10-4
404 Not Found [IP: 64.50.233.100 80]
Err:13 http://ftp.us.debian.org/debian testing/main amd64 dbus-bin amd64 1.14.10-4
404 Not Found [IP: 64.50.233.100 80]
Err:14 http://ftp.us.debian.org/debian testing/main amd64 dbus-daemon amd64 1.14.10-4
404 Not Found [IP: 64.50.233.100 80]
Err:15 http://ftp.us.debian.org/debian testing/main amd64 systemd-sysv amd64 255.4-1
404 Not Found [IP: 64.50.233.100 80]
Err:16 http://ftp.us.debian.org/debian testing/main amd64 dbus-user-session amd64 1.14.10-4
404 Not Found [IP: 64.50.233.100 80]
Err:1 http://ftp.us.debian.org/debian testing/main amd64 libnss-systemd amd64 255.4-1
Temporary failure resolving 'ftp.us.debian.org'
Err:2 http://ftp.us.debian.org/debian testing/main amd64 systemd-journal-remote amd64 255.4-1
Temporary failure resolving 'ftp.us.debian.org'
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/libnss-systemd_255.4-1_amd64.deb Temporary failure resolving 'ftp.us.debian.org'
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/systemd-journal-remote_255.4-1_amd64.deb Temporary failure resolving 'ftp.us.debian.org'
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/systemd-timesyncd_255.4-1_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/libsystemd-shared_255.4-1_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/libudev1_255.4-1_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/systemd_255.4-1_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/udev_255.4-1_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/systemd-dev_255.4-1_all.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/libpam-systemd_255.4-1_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/libsystemd0_255.4-1_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/d/dbus/dbus_1.14.10-4_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/d/dbus/libdbus-1-3_1.14.10-4_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/d/dbus/dbus-bin_1.14.10-4_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/d/dbus/dbus-daemon_1.14.10-4_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/systemd-sysv_255.4-1_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/d/dbus/dbus-user-session_1.14.10-4_amd64.deb 404 Not Found [IP: 64.50.233.100 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
root@homeAssistant:~# apt install systemd-journal-remote -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libjim0.79 libldap-2.4-2 libperl5.32 libpython3.9-minimal libpython3.9-stdlib libusb-0.1-4
perl-modules-5.32 python3.9 python3.9-minimal
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
dbus dbus-bin dbus-daemon dbus-session-bus-common dbus-system-bus-common dbus-user-session
libdbus-1-3 libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1
systemd systemd-dev systemd-sysv systemd-timesyncd udev usr-is-merged
Suggested packages:
systemd-container systemd-homed systemd-userdbd systemd-boot systemd-resolved libqrencode4
libtss2-esys-3.0.2-0 libtss2-mu-4.0.1-0 libtss2-rc0 libtss2-tcti-device0 polkitd
The following NEW packages will be installed:
dbus-bin dbus-daemon dbus-session-bus-common dbus-system-bus-common dbus-user-session
systemd-dev usr-is-merged
The following packages will be upgraded:
dbus libdbus-1-3 libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1
libzstd1 systemd systemd-journal-remote systemd-sysv systemd-timesyncd udev
13 upgraded, 7 newly installed, 0 to remove and 434 not upgraded.
Need to get 9,154 kB/9,614 kB of archives.
After this operation, 1,868 kB disk space will be freed.
Err:1 http://ftp.us.debian.org/debian testing/main amd64 libnss-systemd amd64 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:2 http://ftp.us.debian.org/debian testing/main amd64 systemd-journal-remote amd64 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:3 http://ftp.us.debian.org/debian testing/main amd64 systemd-timesyncd amd64 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:4 http://ftp.us.debian.org/debian testing/main amd64 libsystemd-shared amd64 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:5 http://ftp.us.debian.org/debian testing/main amd64 libudev1 amd64 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:6 http://ftp.us.debian.org/debian testing/main amd64 systemd amd64 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:7 http://ftp.us.debian.org/debian testing/main amd64 udev amd64 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:8 http://ftp.us.debian.org/debian testing/main amd64 systemd-dev all 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:9 http://ftp.us.debian.org/debian testing/main amd64 libpam-systemd amd64 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:10 http://ftp.us.debian.org/debian testing/main amd64 libsystemd0 amd64 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:11 http://ftp.us.debian.org/debian testing/main amd64 dbus amd64 1.14.10-4
404 Not Found [IP: 208.80.154.139 80]
Err:12 http://ftp.us.debian.org/debian testing/main amd64 libdbus-1-3 amd64 1.14.10-4
404 Not Found [IP: 208.80.154.139 80]
Err:13 http://ftp.us.debian.org/debian testing/main amd64 dbus-bin amd64 1.14.10-4
404 Not Found [IP: 208.80.154.139 80]
Err:14 http://ftp.us.debian.org/debian testing/main amd64 dbus-daemon amd64 1.14.10-4
404 Not Found [IP: 208.80.154.139 80]
Err:15 http://ftp.us.debian.org/debian testing/main amd64 systemd-sysv amd64 255.4-1
404 Not Found [IP: 208.80.154.139 80]
Err:16 http://ftp.us.debian.org/debian testing/main amd64 dbus-user-session amd64 1.14.10-4
404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/libnss-systemd_255.4-1_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/systemd-journal-remote_255.4-1_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/systemd-timesyncd_255.4-1_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/libsystemd-shared_255.4-1_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/libudev1_255.4-1_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/systemd_255.4-1_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/udev_255.4-1_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/systemd-dev_255.4-1_all.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/libpam-systemd_255.4-1_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/libsystemd0_255.4-1_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/d/dbus/dbus_1.14.10-4_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/d/dbus/libdbus-1-3_1.14.10-4_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/d/dbus/dbus-bin_1.14.10-4_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/d/dbus/dbus-daemon_1.14.10-4_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/s/systemd/systemd-sysv_255.4-1_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/d/dbus/dbus-user-session_1.14.10-4_amd64.deb 404 Not Found [IP: 208.80.154.139 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Braku plików (pakietów instalacyjnych) - zwykły błąd 404
trochę dziwne że występuje tam gdzieś po drodze
więc wygląda to tak jakbyś z tym systemem nie był na repozytoriach stabilnych
a tych pakietów nie ma w wydaniu stabilnym
błąd DNS
w ogóle jeśli nie mieszkasz w USA to nie kumam czemu używasz amerykańskiego mirrora
PS szarpiesz się z tym Debianem od miesięcy, czy istnieje jakiś mocny powód do nieprzenoszenia instalacji na coś co nie wymaga ręcznych aktualizacji np. na HAOS-generic?
Trzeba repozytoria zaktualizować, będzie bez błędów.
O, to już jakiś kierunek.
A możesz podpowiedzieć czy to chodzi o repozytoria Debiana ?
Tak. Aktualizujesz w ogóle Debiana?
Myśle, ze aktualizuje się automatycznie.
Miałem wersje 11, teraz jest 12.
System Information
version | core-2024.4.4 |
---|---|
installation_type | Home Assistant Supervised |
dev | false |
hassio | true |
docker | true |
user | root |
virtualenv | false |
python_version | 3.12.2 |
os_name | Linux |
os_version | 5.10.0-9-amd64 |
arch | x86_64 |
timezone | Europe/Warsaw |
config_dir | /config |
Home Assistant Community Store
GitHub API | ok |
---|---|
GitHub Content | ok |
GitHub Web | ok |
GitHub API Calls Remaining | 5000 |
Installed Version | 1.34.0 |
Stage | running |
Available Repositories | 1392 |
Downloaded Repositories | 18 |
Home Assistant Cloud
logged_in | false |
---|---|
can_reach_cert_server | ok |
can_reach_cloud_auth | ok |
can_reach_cloud | ok |
Home Assistant Supervisor
host_os | Debian GNU/Linux bookworm/sid |
---|---|
update_channel | stable |
supervisor_version | supervisor-2024.05.1 |
agent_version | 1.2.2 |
docker_version | 23.0.0 |
disk_total | 108.0 GB |
disk_used | 33.8 GB |
healthy | true |
supported | failed to load: Unsupported |
supervisor_api | ok |
version_api | ok |
installed_addons | Mosquitto broker (6.4.0), File editor (5.8.0), Terminal & SSH (9.13.0), Home Assistant Google Drive Backup (0.112.1), Samba share (12.3.1), Node-RED (17.0.12), ZeroTier One (0.18.0), Network UPS Tools (0.13.0), Glances (0.21.1), AC MQTT proxy for home assistant (0.6.2), InfluxDB (5.0.0), Grafana (9.2.2), Portainer (2.20.1), Network UPS Tools (0.13.0), AIS Cloudflared (0.1.13) |
Dashboards
dashboards | 2 |
---|---|
resources | 10 |
views | 40 |
mode | storage |
Recorder
oldest_recorder_run | 30 kwietnia 2024 o 06:15 |
---|---|
current_recorder_run | 8 maja 2024 o 17:16 |
estimated_db_size | 6606.43 MiB |
database_engine | sqlite |
database_version | 3.44.2 |
W katalogu: /etc/apt/sources.list mam takie wpisy. Wydaje mi się, że są to wpisy z Debiana 11.
GNU nano 7.2 //etc/apt/sources.list
# deb cdrom:[Debian GNU/Linux 11.1.0 _Bullseye_ - Official amd64 DVD Binary-1 20211009-10:08]/>
#deb cdrom:[Debian GNU/Linux 11.1.0 _Bullseye_ - Official amd64 DVD Binary-1 20211009-10:08]/ >
deb http://deb.debian.org/debian/ bullseye main
deb-src http://deb.debian.org/debian/ bullseye main
deb http://security.debian.org/debian-security bullseye-security main contrib
deb-src http://security.debian.org/debian-security bullseye-security main contrib
# bullseye-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.debian.org/debian/ bullseye-updates main contrib
deb-src http://deb.debian.org/debian/ bullseye-updates main contrib
deb http://ftp.us.debian.org/debian/ testing main non-free contrib
Za to co miałeś w logach jest odpowiedzialny ten wpis
Co mam z nim zrobić ? wykasować ?
A tym wpisami dot. Debiana Bullseye coś trzeba zrobić ? podmienić na te od Debiana bookworm ?
Zapewne tak, ale najlepiej żeby się wypowiedział ktoś, kto używa HA na Debianie.