ADS-B Feeder failing after updating to Home Assistant Operating System OS 10.0

[gracar2002]

After updating HAOS 10.0 ADS-B Feeder keeps crashing.

It very briefly starts up but then immediately crashes. After 10 crashes Watchdog stop trying to resurrect (expected behaviour).

Logs: 23-04-18 17:00:25 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon ADS-B Multi-Portal Feeder is failed, restarting... 23-04-18 17:00:25 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_f1c878cb_adsb-multi-portal-feeder application 23-04-18 17:00:25 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on ghcr.io/maxwinterstein/homeassistant-adsb-multi-portal-feeder-amd64 with version 1.20.0 23-04-18 17:00:33 ERROR (MainThread) [asyncio] Task exception was never retrieved future: <Task finished name='Task-11722' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:989> exception=AddonsJobError('Rate limit exceeded, more then 10 calls in 0:30:00')> Traceback (most recent call last): File "/usr/src/supervisor/supervisor/addons/addon.py", line 1003, in watchdog_container await self._restart_after_problem(self, event.state) File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 144, in wrapper raise on_condition( supervisor.exceptions.AddonsJobError: Rate limit exceeded, more then 10 calls in 0:30:00

[yousaf465]

check your ram usage

[gracar2002]

RAM steady at ~1.5GB before starting add-on. Spikes hitting 7.1GB when it attempts to start.

[MaxWinterstein]

wow, that does not look good. Are you able to obtain the full log of the addon, e.g. via docker logs...?

[gracar2002]

Freely admit I might have the wrong logs. used docker logs [container ID]

Got: `s6-rc: info: service dump1090: starting s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service dump1090 successfully started s6-rc: info: service netcat: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service init-upintheair: starting s6-rc: info: service confd-piaware: starting s6-rc: info: service confd-layers: starting s6-rc: info: service confd-html: starting s6-rc: info: service confd-fr24feed: starting s6-rc: info: service conf-planefinder: starting s6-rc: info: service conf-adsbexchange: starting s6-rc: info: service banner: starting s6-rc: info: service netcat successfully started s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service init-upintheair successfully started s6-rc: info: service conf-adsbexchange successfully started s6-rc: info: service adsbexchange-feed: starting s6-rc: info: service adsbexchange-feed successfully started s6-rc: info: service adsbexchange-stats: starting s6-rc: info: service adsbexchange-mlat: starting s6-rc: info: service conf-planefinder successfully started s6-rc: info: service planefinder: starting s6-rc: info: service adsbexchange-mlat successfully started s6-rc: info: service adsbexchange-stats successfully started s6-rc: info: service planefinder successfully started s6-rc: info: service planefinder-log: starting [dump1090] Tue Apr 18 18:57:17 2023 BST dump1090-fa v8.2 starting up. s6-rc: info: service planefinder-log successfully started [dump1090] rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 1090) 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[412]: INFO Backend set to env 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[412]: INFO Starting confd 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[412]: INFO Backend source(s) set to 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[427]: INFO Backend set to env 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[427]: INFO Starting confd 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[427]: INFO Backend source(s) set to 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[332]: INFO Backend set to env 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[332]: INFO Starting confd 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[332]: INFO Backend source(s) set to 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[332]: INFO Target config /usr/lib/fr24/public_html/layers.js out of sync 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[427]: INFO Target config /etc/fr24feed.ini out of sync 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[412]: INFO Target config /usr/lib/fr24/public_html/config.js out of sync 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[412]: INFO Target config /usr/lib/fr24/public_html/config.js has been updated 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[332]: INFO Target config /usr/lib/fr24/public_html/layers.js has been updated 2023-04-18T18:57:17+01:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[427]: INFO Target config /etc/fr24feed.ini has been updated s6-rc: info: service confd-html successfully started s6-rc: info: service confd-layers successfully started s6-rc: info: service http: starting s6-rc: info: service confd-fr24feed successfully started s6-rc: info: service fr24feed: starting s6-rc: info: service confd-piaware successfully started Add-on: ADS-B Multi-Portal Feeder s6-rc: info: service piaware: starting s6-rc: info: service http successfully started s6-rc: info: service fr24feed successfully started s6-rc: info: service piaware successfully started Dump1090 based feeder for FlightRadar24, FlightAware and more

[dump1090] Found Rafael Micro R820T tuner Add-on version: 1.20.0 You are running the latest version of this add-on. [planefinder] tail: cannot open '/planefinder/log/*.log' for reading: No such file or directory [dump1090] rtlsdr: tuner gain set to 49.6 dB (gain step 28) [fr24feed] 2023-04-18 18:57:18 | __ ____ [fr24feed] 2023-04-18 18:57:18 | | || |(_) | | | | | | / \ / | [fr24feed] 2023-04-18 18:57:18 | | | | | _ | | | | | | _ _`' / /' / /| | [fr24feed] 2023-04-18 18:57:18 | | | | || | / ` || ' \ | || '|/ ` | / | / _ || '_| / / / /| | [fr24feed] 2023-04-18 18:57:18 | | | | || || (| || | | || | | | | (| || (| || (| || | ./ /_ | [fr24feed] 2023-04-18 18:57:18 | _| |||| _, ||| || _||| _,| _,| _,||| ___/ |/ [fr24feed] 2023-04-18 18:57:18 | / | [fr24feed] 2023-04-18 18:57:18 | |/ [fr24feed] 2023-04-18 18:57:18 | [main][i]FR24 Feeder/Decoder [fr24feed] 2023-04-18 18:57:18 | [main][i]Version: 1.0.34-0/generic [fr24feed] 2023-04-18 18:57:18 | [main][i]Built on Jan 10 2023 10:09:01 (decoder-v1.0.34-0-7c5301b.git/Linux/static_amd64) [fr24feed] 2023-04-18 18:57:18 | [main][i]Running on: debian="11" [fr24feed] 2023-04-18 18:57:18 | [main][i]Local IP(s): 172.30.33.7 [fr24feed] 2023-04-18 18:57:18 | [main][i]Copyright 2012-2023 Flightradar24 AB [fr24feed] 2023-04-18 18:57:18 | [main][i]https://www.flightradar24.com [fr24feed] 2023-04-18 18:57:18 | [main][i]DNS mode: PING [fr24feed] 2023-04-18 18:57:18 | [main][i]Automatic updates are DISABLED [fr24feed] 2023-04-18 18:57:18 | 23-04-18 18:57:18.103 [I][http-server.cpp:270] [httpd]Server started, listening on :::8754 [dump1090] Allocating 4 zero-copy buffers System: Home Assistant OS 10.0 (amd64 / generic-x86-64) [fr24feed] 2023-04-18 18:57:18 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled Home Assistant Core: 2023.4.5 [fr24feed] 2023-04-18 18:57:18 | [d]TLSConnection::ctor(): Enable verify_peer in production code! [fr24feed] 2023-04-18 18:57:18 | [main][i]Reader thread started [fr24feed] 2023-04-18 18:57:18 | [master][i]Starting processing thread [fr24feed] 2023-04-18 18:57:18 | [reader][i]Initializing reader [fr24feed] 2023-04-18 18:57:18 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005) [fr24feed] 2023-04-18 18:57:18 | [reader][i]Connected to the receiver, configuring [fr24feed] 2023-04-18 18:57:18 | [reader][i]Configured, processing messages Home Assistant Supervisor: 2023.04.0

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service banner successfully started s6-rc: info: service legacy-services: starting [fr24feed] 2023-04-18 18:57:18 | [time][i]Synchronizing time via NTP s6-rc: info: service legacy-services successfully started [fr24feed] 2023-04-18 18:57:18 | [time][i]Time synchronized correctly, offset +0.000 seconds [fr24feed] 2023-04-18 18:57:18 | [main][i]Feed Network client started [fr24feed] 2023-04-18 18:57:18 | [feed][i]Downloading configuration [fr24feed] 2023-04-18 18:57:18 | [feed][d]fetching configuration [fr24feed] 2023-04-18 18:57:18 | [feed][i]configuring decoder [fr24feed] 2023-04-18 18:57:18 | [feed][c]Max range AIR: 350.0nm [fr24feed] 2023-04-18 18:57:18 | [feed][c]Max range GND: 100.0nm [fr24feed] 2023-04-18 18:57:18 | [feed][i]configuration changed [fr24feed] 2023-04-18 18:57:18 | [feed][i]defined 3 servers [fr24feed] 2023-04-18 18:57:18 | [feed][c]Timestamps: optional [fr24feed] 2023-04-18 18:57:18 | 23-04-18 18:57:18.564 [I][receiver_ac_sender.cpp:137] Stopping ReceiverACSender threads for feed [fr24feed] 2023-04-18 18:57:18 | 23-04-18 18:57:18.564 [D][receiver_ac_sender.cpp:141] Stop called on non-running network thread for feed [fr24feed] 2023-04-18 18:57:18 | 23-04-18 18:57:18.564 [I][receiver_ac_sender.cpp:96] Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.24:8099, feed: EGPH187, send_interval: 5s/1s, max age: 15s, send metadata: true, mode: 1, filtering: true [fr24feed] 2023-04-18 18:57:18 | 23-04-18 18:57:18.564 [I][crxstats.cpp:588] [stats]Stats thread started [fr24feed] 2023-04-18 18:57:18 | [feed][n]EGPH187@185.218.24.22:8099/UDP [fr24feed] 2023-04-18 18:57:18 | 23-04-18 18:57:18.564 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.22:8099 for feed EGPH187 [fr24feed] 2023-04-18 18:57:18 | [feed][n]connecting [fr24feed] 2023-04-18 18:57:18 | [feed][n]connected via UDP (fd 23) [fr24feed] 2023-04-18 18:57:18 | [feed][n]working`

Please let me know if I've got this wrong.

[yousaf465]

https://github.com/home-assistant/operating-system/discussions/2432#discussioncomment-5648679 I think this is related.

[gracar2002]

Have rolled back to 9.5 which has resolved. Happy to go forward if it'd be useful for testing.

[blackpearlla]

Same issue here.

[yousaf465]

Have rolled back to 9.5 which has resolved. Happy to go forward if it'd be useful for testing.

https://discord.com/channels/330944238910963714/332167321311510530/1097971441716170853 try this might help

[magtimmermans]

I have the same issue

[gracar2002]

Have rolled back to 9.5 which has resolved. Happy to go forward if it'd be useful for testing.

https://discord.com/channels/330944238910963714/332167321311510530/1097971441716170853 try this might help

Potentially a private channel Discord giving me "nothing found."

[yousaf465]

Have rolled back to 9.5 which has resolved. Happy to go forward if it'd be useful for testing.

https://discord.com/channels/330944238910963714/332167321311510530/1097971441716170853 try this might help

Potentially a private channel Discord giving me "nothing found."

it is Home assistant discord.
https://discord.gg/home-assistant general channel

[medivb]

I have the same issue too. Let me know if I can help. I’m sticking to OS V10, so able to run whatever test is needed…

[therealhalifax]

Have rolled back to 9.5 which has resolved. Happy to go forward if it'd be useful for testing.

How you did that? I have the same issue, but my Backup does not contain the OS.

[Tntdruid]

@therealhalifax login to ssh and type ha os --upgrade 9.5

[therealhalifax]

@therealhalifax login to ssh and type ha os --upgrade 9.5

Unfortunately that command dosnt work. Nether Upgrade or Update are found. Unknown Flag - - upgrade

I am on a x86 machine.

[Tntdruid]

@therealhalifax my bad it's

ha os update --version 9.5

[GenericStudent]

This issue seems related to the "SERVICE_ENABLE_HTTP" option, with it disabled (and no GUI available) the container boots up correctly and cracks on reporting aircraft.

[fshultz]

This issue seems related to the "SERVICE_ENABLE_HTTP" option, with it disabled (and no GUI available) the container boots up correctly and cracks on reporting aircraft.

Can confirm-- maybe it doesn't use as much memory when the HTTP service isn't enabled so it can run. Also thinking of downgrading for now. Another add-on (NUT) also isn't working for me now after the upgrade.

[GenericStudent]

HAving a climb inside the container, could it be that the OS update changed how journal logs are handled? This is the output of manually invoking the thttpd server from within the container:

root@f1c878cb-adsb-multi-portal-feeder:/# strace /thttpd -D -h 0.0.0.0 -p 8080 -d /usr/lib/fr24/public_html -l /dev/null -M 60
execve("/thttpd", ["/thttpd", "-D", "-h", "0.0.0.0", "-p", "8080", "-d", "/usr/lib/fr24/public_html", "-l", "/dev/null", "-M", "60"], 0xffffda348a48 /* 26 vars */) = 0
set_tid_address(0x443638)               = 4808
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
connect(3, {sa_family=AF_UNIX, sun_path="/dev/log"}, 12) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/zoneinfo/Europe/London", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_CLOEXEC) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=3678, ...}) = 0
mmap(NULL, 3678, PROT_READ, MAP_SHARED, 4, 0) = 0xffff9efc9000
close(4)                                = 0
brk(NULL)                               = 0xebd000
brk(0xebf000)                           = 0xebf000
mmap(0xebd000, 4096, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xebd000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff9efc8000
munmap(0xffff9efc8000, 4096)            = 0
getuid()                                = 0
openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 4
fcntl(4, F_SETFD, FD_CLOEXEC)           = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff9efc8000
fcntl(4, F_SETFD, FD_CLOEXEC)           = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffff9efc7000
read(4, "root:x:0:0:root:/root:/bin/bash\n"..., 1024) = 1024
lseek(4, -151, SEEK_CUR)                = 873
close(4)                                = 0
munmap(0xffff9efc8000, 4096)            = 0
chdir("/usr/lib/fr24/public_html")      = 0
getcwd("/usr/lib/fr24/public_html", 4096) = 26
setsid()                                = 4808
prlimit64(0, RLIMIT_NOFILE, NULL, {rlim_cur=1073741816, rlim_max=1073741816}) = 0
prlimit64(0, RLIMIT_NOFILE, NULL, {rlim_cur=1073741816, rlim_max=1073741816}) = 0
prlimit64(0, RLIMIT_NOFILE, {rlim_cur=1073741816, rlim_max=1073741816}, NULL) = 0
mmap(NULL, 4294967284, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xfffe9efc7000
mmap(NULL, 8589934548, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate memory)
clock_gettime(CLOCK_REALTIME, {tv_sec=1681935084, tv_nsec=614269322}) = 0
getpid()                                = 4808
sendto(3, "<26>Apr 19 20:11:24 thttpd[4808]"..., 65, 0, NULL, 0) = -1 ENOTCONN (Transport endpoint is not connected)
connect(3, {sa_family=AF_UNIX, sun_path="/dev/log"}, 12) = -1 ENOENT (No such file or directory)
exit_group(1)                           = ?
+++ exited with 1 +++

And /dev/log points to:

root@f1c878cb-adsb-multi-portal-feeder:/# ls -alh /dev/log
lrwxrwxrwx 1 root root 28 Apr 19 07:39 /dev/log -> /run/systemd/journal/dev-log

which doesn't exist (not even /run/systemd/)

Running thttpd with a different logging option (-l /dev/null or -l /tmp/thttpd.log didn't seem to make much difference)

I've got to go but hopefully this could be a helpful pointer.

[MaxWinterstein]

Wow, I am pleasantly surprised how many people seem to use this add-on - I never saw/did any statistic ❤️

@fshultz is there any GitHub repo for NUT that might have a similar issue?

@GenericStudent thanks for pointing this out (and all others)

---

I am running on a different os myself (OrangePi 5 user) but can try to replicate it on a VM. Just need to find some time :(

[Tntdruid]

@MaxWinterstein it's a very nice add-on you made 👍

[yousaf465]

Wow, I am pleasantly surprised how many people seem to use this add-on - I never saw/did any statistic ❤️

@fshultz is there any GitHub repo for NUT that might have a similar issue?

@GenericStudent thanks for pointing this out (and all others)

I am running on a different os myself (OrangePi 5 user) but can try to replicate it on a VM. Just need to find some time :(

https://twitter.com/yousaf465/status/1642231186381590528 BeardedTinker @BeardedTinker uses it too. https://www.youtube.com/BeardedTinker

anyone of HA Youtuber's video on this add-on will increase the numbers exponentially.

[agners]

I am looking at an issue from HAOS side which is related (see https://github.com/home-assistant/operating-system/issues/2486). In that case it seems that with HAOS 10 the radio is no longer (properly) forwarded:

[dump1090] rtlsdr: no supported devices found.

@MaxWinterstein the issue the NUT add-on was facing got solved with PR https://github.com/hassio-addons/addon-nut/pull/290. You can find the background why this is necessary in this blog post.

Sidenote: I think I need to get a suitable radio too, this seems like fun :smile:

[MaxWinterstein]

@agners this seems like the perfect explanation!

Will try to build some quick fix for this!

[CoMPaTech]

Cool @MaxWinterstein - I spotted the same issue, thttp OOM errors on the console. Unfortunately also after deploying #150

[MaxWinterstein]

Cool @MaxWinterstein - I spotted the same issue, thttp OOM errors on the console. Unfortunately also after deploying #150

Did you try v1.20.2? There was a v1.20.1 that was incorrect.

[CoMPaTech]

Did you try v1.20.2? There was a v1.20.1 that was incorrect. Verified my steps, HA says 1.20.2, docker images -a confirms (HASSOS on Proxmox), OS 10.0, SV 2023.4.0, HA 2023.4.5

[MaxWinterstein]

mhm, I guess the ulimit might not be used with all those s6 overlay stuff.

As Thom-x seems quite quick: https://github.com/Thom-x/docker-fr24feed-piaware-dump1090/issues/107

Will wait until his new version is released, might be quicker than me overloading all those files.

[mrkaqz]

Not sure if it is the same things happen to me after update to OS 10 or not, Here is the logs from add-on

As I read it has error that time zone not set to GMT and it all stop.

---

s6-rc: info: service adsbexchange-mlat successfully started Add-on: ADS-B Multi-Portal Feeder 2023-04-21T11:54:38+07:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[358]: INFO Backend set to env 2023-04-21T11:54:38+07:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[358]: INFO Starting confd 2023-04-21T11:54:38+07:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[358]: INFO Backend source(s) set to 2023-04-21T11:54:38+07:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[358]: INFO Target config /etc/piaware.conf out of sync 2023-04-21T11:54:38+07:00 f1c878cb-adsb-multi-portal-feeder /opt/confd/bin/confd[358]: INFO Target config /etc/piaware.conf has been updated s6-rc: info: service confd-piaware successfully started s6-rc: info: service piaware: starting Dump1090 based feeder for FlightRadar24, FlightAware and more

s6-rc: info: service piaware successfully started Add-on version: 1.20.2 [dump1090] Found Rafael Micro R820T tuner You are running the latest version of this add-on. [fr24feed] 2023-04-21 11:54:38 | __ ____ [fr24feed] 2023-04-21 11:54:38 | | || |(_) | | | | | | / \ / | r24feed]m[du0m 2023-04-21 11:54:38 | | | | | _ | | | | | | _ _`' / /' / /| | p1094m[f0] rtlsdr: tuner gain set to 49.6 dB (gain step 28) r24feed] 2023-04-21 11:54:38 | | | | || | / ` || ' \ | || '|/ ` | / | / _ || '_| / / / /| | [fr24feed] 2023-04-21 11:54:38 | | | | || || (| || | | || | | | | (| || (| || (| || | ./ /_ | [fr24feed] 2023-04-21 11:54:38 | _| |||| _, ||| || _||| _,| _,| _,||| ___/ |/ [fr24feed] 2023-04-21 11:54:38 | / |
[fr24feed] 2023-04-21 11:54:38 | |/
[fr24feed] 2023-04-21 11:54:38 | error | Local time: 2023-04-21 11:54:38 +0700 [fr24feed] 2023-04-21 11:54:38 | error | GMT+0 time: 2023-04-21 04:54:38 +0700 [fr24feed] 2023-04-21 11:54:38 | error | Your machine should be set as GMT+0 time zone! [fr24feed] 2023-04-21 11:54:38 | warning | Time zone is not set to GMT+0 [fr24feed] 2023-04-21 11:54:38 | [main][i]FR24 Feeder/Decoder [fr24feed] 2023-04-21 11:54:38 | [main][i]Version: 1.0.34-0/generic [fr24feed] 2023-04-21 11:54:38 | [main][i]Built on Jan 10 2023 10:09:01 (decoder-v1.0.34-0-7c5301b.git/Linux/static_amd64) [fr24feed] 2023-04-21 11:54:38 | [main][i]Running on: debian="11" [fr24feed] 2023-04-21 11:54:38 | [main][i]Local IP(s): 172.30.33.8 [fr24feed] 2023-04-21 11:54:38 | [main][i]Copyright 2012-2023 Flightradar24 AB [fr24feed] 2023-04-21 11:54:38 | [main][i]https://www.flightradar24.com [fr24feed] 2023-04-21 11:54:38 | [main][i]DNS mode: PING [fr24feed] 2023-04-21 11:54:38 | [main][i]Automatic updates are DISABLED [fr24feed] 2023-04-21 11:54:38 | 23-04-21 11:54:38.764 [E][:] Local time: 2023-04-21 11:54:38 +0700 [fr24feed] 2023-04-21 11:54:38 | 23-04-21 11:54:38.764 [E][:] GMT+0 time: 2023-04-21 04:54:38 +0700 [fr24feed] 2023-04-21 11:54:38 | 23-04-21 11:54:38.764 [E][:] Your machine should be set as GMT+0 time zone! [fr24feed] 2023-04-21 11:54:38 | 23-04-21 11:54:38.764 [W][:] Time zone is not set to GMT+0 [fr24feed] 2023-04-21 11:54:38 | 23-04-21 11:54:38.764 [I][http-server.cpp:270] [httpd]Server started, listening on :::8754 System: Home Assistant OS 10.0 (amd64 / qemux86-64) Home Assistant Core: 2023.4.5 [dump1090] Allocating 4 zero-copy buffers [piaware] **** [piaware] piaware version 8.2 is running, process ID 486 [piaware] your system info is: Linux f1c878cb-adsb-multi-portal-feeder 6.1.24 #1 SMP PREEMPT_DYNAMIC Mon Apr 17 09:34:33 UTC 2023 x86_64 GNU/Linux Home Assistant Supervisor: 2023.04.0

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service banner successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service banner: stopping s6-rc: info: service planefinder-log: stopping s6-rc: info: service piaware: stopping s6-rc: info: service netcat: stopping s6-rc: info: service http: stopping s6-rc: info: service fr24feed: stopping s6-rc: info: service adsbexchange-stats: stopping s6-rc: info: service adsbexchange-mlat: stopping s6-rc: info: service banner successfully stopped s6-rc: info: service planefinder-log successfully stopped s6-rc: info: service planefinder: stopping s6-rc: info: service piaware successfully stopped s6-rc: info: service confd-piaware: stopping s6-rc: info: service netcat successfully stopped s6-rc: info: service http successfully stopped s6-rc: info: service init-upintheair: stopping s6-rc: info: service confd-layers: stopping s6-rc: info: service confd-html: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fr24feed successfully stopped s6-rc: info: service confd-fr24feed: stopping s6-rc: info: service adsbexchange-stats successfully stopped s6-rc: info: service confd-piaware successfully stopped s6-rc: info: service init-upintheair successfully stopped s6-rc: info: service adsbexchange-mlat successfully stopped s6-rc: info: service adsbexchange-feed: stopping s6-rc: info: service confd-layers successfully stopped s6-rc: info: service confd-html successfully stopped s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service confd-fr24feed successfully stopped s6-rc: info: service planefinder successfully stopped s6-rc: info: service conf-planefinder: stopping s6-rc: info: service adsbexchange-feed successfully stopped s6-rc: info: service conf-adsbexchange: stopping s6-rc: info: service dump1090: stopping s6-rc: info: service conf-planefinder successfully stopped s6-rc: info: service conf-adsbexchange successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service dump1090 successfully stopped s6-rc: info: service s6rc-oneshot-runner successfully stopped

[dartfrogdk]

Still not working after update

[blackpearlla]

the update is not working for me. The Container stops suddenly without any informations.

the only information i got from portainer log is:

Container addon_f1c878cb_adsb-multi-portal-feeder exited with status code 137

[SenMorgan]

I can confirm that the ADS-B Feeder is still failing even after the update.

[MaxWinterstein]

I just released v1.20.3 - pls test

[blackpearlla]

now it works. what was the problem?

[CoMPaTech]

I just released v1.20.3 - pls test

AWesomeness :) confirmed working

[mrkaqz]

Confirmed it works now.

Thanks

On Fri, Apr 21, 2023, 14:44 Tom @.***> wrote:

I just released v1.20.3 - pls test

AWesomeness :) confirmed working

— Reply to this email directly, view it on GitHub https://github.com/MaxWinterstein/homeassistant-addons/issues/149#issuecomment-1517413087, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVKQU4COX32F22HVMNRRV3XCI3HRANCNFSM6AAAAAAXC3DGLI . You are receiving this because you commented.Message ID: @.***>

[SenMorgan]

I can confirm that it works again with version 1.20.3! Thanks @MaxWinterstein

[gracar2002]

Works for me. Happy to close.

[maweki]

Anybody experiencing unusually high CPU usage with this Addon since OS V10? It usually sat at ~3% and now it idles with 20% with the addon enabled.

Edit:

[SenMorgan]

Anybody experiencing unusually high CPU usage with this Addon since OS V10? It usually sat at ~3% and now it idles with 20% with the addon enabled.

Yeap, I can confirm It. Here I disabled this addon for a while and you can see the result:

[mrkaqz]

Yes, my system consume 20% more when this add-on started.

On Fri, Apr 21, 2023, 15:41 Mario Wenzel @.***> wrote:

Anybody experiencing unusually high CPU usage with this Addon since OS V10? It usually sat at ~3% and now it idles with 20% with the addon enabled.

— Reply to this email directly, view it on GitHub https://github.com/MaxWinterstein/homeassistant-addons/issues/149#issuecomment-1517484880, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVKQUZKH3YKUPMVZUSEVGLXCJB47ANCNFSM6AAAAAAXC3DGLI . You are receiving this because you commented.Message ID: @.***>

[MaxWinterstein]

Pls continue the CPU discussion at #151

---

Glad the fix worked, thanks to all here 👍