v1.0.13 Crashing on DS214Play/RS814 with DSM 7.1.1 #63
Comments
|
Which NAS model are you using? You have downloaded the x86 (32bit) static version. This version does not exist at 0.2xx. Also the x86 version is for old NAS models, perhaps you need the x86_64 version? (see also the table in the documentation https://github.com/eizedev/AirConnect-Synology#how-to-install) |
|
@smlomas Ah, sorry, totally missed the topic. 214play is a 32bit arch (evansport), so https://github.com/eizedev/AirConnect-Synology/releases/download/1.0.13-20221216/AirConnect-dsm7-x86-1.0.13-20221216.spk should be the correct package. I also have a 214play, i will also test it later this week. |
|
I have the same problem after upgrading a RS814 from DSM 6.2 to DSM DSM 7.1.1-42962 Update 3 and then installing the AirConnect-dsm7-arm-static-1.0.13-20221216.spk. After downgrading to AirConnect-dsm7-arm-static-0.2.51.2-20220206.spk everything works fine. |
|
@tschniewind Have you tried using the I have no Synology device with ARM architecture, so i cannot reproduce the error or any error for this platform. In general, the Synology package has only changed to a limited extent compared to the old version. What has changed are the two binaries airupnp and aircast because the developer of AirConnect has completely rebuilt this. Maybe there is a problem with the v1 version and you have to open an issue in the official AirConnect project. |
|
Thanks for your reply. There seem to be no difference in using static or not. See the attached logfile written after a fresh install (removing the old package before). Even if the log says that AriConnect is started it is shown as stopped after a fiew seconds in the package manager. So there is unforunately no crash output. |
|
This looks like airconnect is crashing and not related to the package. Could you please take a look at other logfiles located in /var/log, for example /var/log/messages? |
|
Yes indeed I found something in /var/log/messages: |
|
@tschniewind Interesting! This is probably a bug of aircast/airupnp ARM binaries in connection to your architecture. If @philippe44 needs the core dump file for debugging, it would be great if you provide it to him. |
eizedev
added
bug
@eizedev Many thanks for your support. Hope that @philippe44 my help. |
|
It's likely that I don't build binaries for armv5 anymore |
|
I think that armadaxp is base on armv7 |
|
you're right - I need a log then (not a core dump) |
|
where can I find the log you need? |
|
I'm not sure how @eizedev launches airconnect, but otherwise if you know how to launch it manually, it's -f |
|
@philippe44 default command line (airupnp) - config.xml is by default empty/not existing:
@tschniewind The log file is the You could also adjust the config in Change Readme for the config part: https://github.com/eizedev/AirConnect-Synology#airconnectconf |
|
Seems not to produce helpful infos. I deinstalled the 0.51-package an installed the 1.0.13-package. Then changed the loglevel for airupnp and started again, changed loglevel for aircast and started again. But after each try the package is not shown as started within the synology-ui and the each try after changing the loglevel logs first stopping ariConnect [17:15:15] & [17:19:39]: |
|
That's not the log I'm looking for |
|
This is taken from /volume1/@appstore/AirConnect/log/airconnect.log |
|
that's only the log output from the installation/synology package, really strange. Do you have SSH access to your NAS? Could you please stop the Airconnect-Synology package or kill the airupnp and aircast processes and run it manually? With Logging Level Info:
That should produce any suitable log output in The log entries from aircast/airupnp also have another timestamp: In my example the timestamps only in format HH:MM:SS "Hour:Minute:Second" are from my package. |
|
FATAL: kernel too old |
|
Ah, that explains why no log messages for airupnp or aircast will be written @philippe44 @tschniewind could you please post the output of |
|
ah - In the update I've made to all my build tools, it includes min kernel and glibc. Having a kernel below 4.x is really a big risk |
|
cat /proc/version |
|
oh, sorry about that but running on 3.2 is really really really bad |
|
Doesn't come the linux kernel with the DSM-Installation? |
|
Synology does not update the kernel on older hardware models when updating to the newest DSM 7 Synology os release. This is really crappy from Synology. I have a similar situation on my NAS. I also still have kernel 3.10 despite the latest DSM version. |
|
Synology is applying security updates and other changes heavily in there DSM versions, but the kernel version still stays on old release. Synology has never changed the kernel version on any model, i.e. the kernel version that came with the model when it was initially released will be the kernel version for that model forever. When that kernel version becomes incompatible with a new DSM version the model stops getting DSM updates. |
|
so there is no chance to get AirConnect run under this linux kernel? |
|
Could you please check your glibc version using @philippe44 Can you tell us the minimum versions of the kernel and glibc? |
You have to stick with older versions. More recent ones requires at least 4.x and changing that would mean rebuilding all my toolchains in favor of old stuff and that's precisely the very painful effort I went through : get everything up to date |
|
@philippe44 I think the kernel is not the main problem, I think glibc is the showstopper. /volume1/@appstore/AirConnect/airupnp -v
v1.0.13 (Dec 10 2022 @ 11:10:19)
/lib64/libc.so.6 --version
GNU C Library (GNU libc) stable release version 2.26, by Roland McGrath et al.
Copyright (C) 2017 Free Software Foundation, Inc.
uname -r
3.10.108 |
4.4.302 and 2.23 |
|
/lib/libc.so.6 --version |
|
interesting, I have an older kernel than 4.4 but "newer" glibc and on my system it is running. |
|
I'm not in front of an arm machine now but use ldd to check what I wrote |
|
ldd is not available on Synology devices, you could only the the version directly at the libraries running My system is also a x86_64 architecture. Perhaps this is the different to @tschniewind |
|
@tschniewind You could stay at 0.2.51.2 I will update the documentation with this information. @philippe44 is this "limitation" only for older ARMv7 architectures or also for other architectures? My x86_64 cpu arch with kernel 3.10. can still run airupnp and aircast. |
|
The limitation is on all Linux builds. I'm surprised that it runs on your machine, as all my compilers (I build them using crosstools-ng) have 4.4.320 and 2.23 set |
|
I just saw your config for crosstools-ng. Strange while it is running on my system. https://github.com/philippe44/cross-compiling/blob/8bf4f5b4e05ca5454540c7c0a4a80c8b4b7d7cfd/crosstools-ng-1.25.0/.config.stretch.x86_64#L282 Any chance that you have used an older CT_LINUX_VERSION on armv7 than I also have an older x86 Synology NAS. It has the same kernel version as @tschniewind but aircast/airupnp 1.0.13 is still running on this old system: root@Storebox:~# ./aircast-linux-x86
[19:54:13.559022] main:884 Starting aircast version: v1.0.13 (Dec 10 2022 @ 11:14:03)
[19:54:13.559313] main:891 no config file, using defaults
[19:54:13.559628] Start:662 Binding to 192.168.1.11
[19:54:13.930364] AddCastDevice:613 [0x8ec9320]: creating MAC
[19:54:13.930474] AddCastDevice:627 [0x8ec9320]: adding renderer (SHIELD) with mac CCCC85116FE6
^C[19:54:15.148203] DeleteCastDevice:379 [0x8ec9320]: Cast device stopped
^C^Croot@Storebox:~# ^C
root@Storebox:~# ./airupnp-linux-x86
[19:57:56.426503] main:1355 Starting airupnp version: v1.0.13 (Dec 10 2022 @ 11:10:21)
[19:57:56.426798] main:1362 no config file, using defaults
[19:57:56.428479] Start:1087 Binding to 192.168.1.11:49152
[19:57:56.591762] AddMRDevice:1007 [0xb3078010] skipping Sonos slave 192.168.1.120 - Sonos Sub
root@Storebox:~# uname -a
Linux Storebox 3.2.101 #42661 SMP PREEMPT Mon Jun 27 15:08:01 CST 2022 i686 GNU/Linux synology_evansport_214play
root@Storebox:~# /lib/libc.so.6 --version
GNU C Library (GNU libc) stable release version 2.26
root@Storebox:~# file aircast-linux-x86
aircast-linux-x86: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 4.4.255, strippedEdit: On my Synology router with newer kernel ( So anyway, don't know why it is still running on my older devices but I would appreciate it if it stays like this ;-) |
|
It is strange indeed - I have to check exactly how kernel version is checked. I know how glibc is during loading, but I've never checked precisely re kernel. And don't worry, it will not change I don't want to rebuild all the tool chains and all the libraries that I need - it's a very cumbersome task. |
|
@smlomas als already mentioned, please install https://github.com/eizedev/AirConnect-Synology/releases/download/1.0.13-20221216/AirConnect-dsm7-x86-1.0.13-20221216.spk on your DS214play. I have just tested in on my DS214play, this version works without any problems. |
eizedev
changed the title
|
For anyone having a problem with modern versions of the software. Simply use the older version. For example for Synology DS218j I found 0.2.51.2-20 version to be working alright, while all the recent ones are crashing with |
I was running a v0.2xxx release ok, with the occasional restart needed. Initially just ran the upgrade to 1.0.13, from the DSM GUI, but airupnp stops immediately after it reports it has started. Have uninstalled, then reinstalled, but still crashes out.
using : AirConnect-dsm7-x86-static-1.0.13-20221216.spk
[11:08:44] Starting AirConnect ...
[11:08:44] Linking airconnect configuration to "/volume1/airconnect/airconnect.conf".
[11:08:44] Linking airupnp configuration to "/volume1/airconnect/config.xml".
[11:08:44] Starting airupnp on 10.1.1.10:49154
[11:08:44] AirConnect successfully started on ip "10.1.1.10"!
[11:08:49] Status: airupnp not running!
The text was updated successfully, but these errors were encountered: