Closed Locke closed 1 year ago
Please install the debug binaries of myMPD and set the loglevel to debug. Is IPv6 enabled on your system?
It seems to be a bug in the code for detection of enabled IPv6.
Installed mympd-dbgsym
(was showing two frames) and then libc6-dbg
(now showing 3 frames):
Not sure if I set the loglevel correctly, IO tried it via adding this to the override.conf file:
[Service]
Environment="MYMPD_LOGLEVEL=7"
pi@raspberrypi:~$ sudo systemctl restart mympd.service
pi@raspberrypi:~$ sudo systemctl status mympd.service
● mympd.service - myMPD server daemon
Loaded: loaded (/usr/lib/systemd/system/mympd.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mympd.service.d
└─override.conf
Active: failed (Result: core-dump) since Thu 2023-10-05 12:45:18 CEST; 2s ago
Docs: man:mympd(1)
Process: 31027 ExecStart=/usr/bin/mympd (code=dumped, signal=SEGV)
Main PID: 31027 (code=dumped, signal=SEGV)
CPU: 134ms
Oct 05 12:45:17 raspberrypi systemd[1]: Started myMPD server daemon.
Oct 05 12:45:18 raspberrypi systemd[1]: mympd.service: Main process exited, code=dumped, status=11/SEGV
Oct 05 12:45:18 raspberrypi systemd[1]: mympd.service: Failed with result 'core-dump'.
pi@raspberrypi:~$ sudo journalctl -u mympd.service -b0
-- Journal begins at Sat 2022-09-10 16:48:32 CEST, ends at Thu 2023-10-05 12:45:37 CEST. --
Oct 05 01:33:46 raspberrypi systemd[1]: Started myMPD server daemon.
Oct 05 01:33:47 raspberrypi systemd[1]: mympd.service: Main process exited, code=dumped, status=11/SEGV
Oct 05 01:33:47 raspberrypi systemd[1]: mympd.service: Failed with result 'core-dump'.
// ...
Oct 05 12:14:53 raspberrypi systemd[1]: Started myMPD server daemon.
Oct 05 12:14:54 raspberrypi systemd[1]: mympd.service: Main process exited, code=dumped, status=11/SEGV
Oct 05 12:14:54 raspberrypi systemd[1]: mympd.service: Failed with result 'core-dump'.
Oct 05 12:45:17 raspberrypi systemd[1]: Started myMPD server daemon.
Oct 05 12:45:18 raspberrypi systemd[1]: mympd.service: Main process exited, code=dumped, status=11/SEGV
Oct 05 12:45:18 raspberrypi systemd[1]: mympd.service: Failed with result 'core-dump'.
pi@raspberrypi:~$ sudo coredumpctl info
PID: 31027 (mympd)
UID: 61876 (61876)
GID: 61876 (61876)
Signal: 11 (SEGV)
Timestamp: Thu 2023-10-05 12:45:17 CEST (1min 9s ago)
Command Line: /usr/bin/mympd
Executable: /usr/bin/mympd
Control Group: /system.slice/mympd.service
Unit: mympd.service
Slice: system.slice
Boot ID: 9de7616502254fd5bb8f5a3d3061851e
Machine ID: 2c9b9d45656b45afb58b1f0a4682f91a
Hostname: raspberrypi
Storage: /var/lib/systemd/coredump/core.mympd.61876.9de7616502254fd5bb8f5a3d3061851e.31027.1696502717000000.zst
Message: Process 31027 (mympd) of user 61876 dumped core.
Stack trace of thread 31027:
#0 0x0000000000aa59a4 main (mympd + 0x59a4)
#1 0x00000000f76db740 __libc_start_main (libc.so.6 + 0x17740)
#2 0x0000000000aa6b88 $a (mympd + 0x6b88)
Yes, I use dualstack (native IPv6 2a02:8071:BBBB::/59 + NATed IPv4 192.168.178.0/24) to connect to the internet and also have a VPN dualstack (native IPv6 2a01:4f8:AAAA::/64 + NATed IPv4 10.8.0.0/24, 192.168.1.0/24, 192.168.2.0/24).
IPs/MACs are redacted.
pi@raspberrypi:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether dc:a6:MAC:LAN brd ff:ff:ff:ff:ff:ff
inet 192.168.178.X1/24 brd 192.168.178.255 scope global dynamic eth0
valid_lft 824659sec preferred_lft 824659sec
inet6 2a02:8071:X2/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 7179sec preferred_lft 3579sec
inet6 fe80::dea6:X3/64 scope link
valid_lft forever preferred_lft forever
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 0a:69:MAC:BR brd ff:ff:ff:ff:ff:ff
inet 192.168.2.1/24 brd 192.168.2.255 scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::869:Y2/64 scope link
valid_lft forever preferred_lft forever
4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 500
link/none
inet 10.8.0.Z1/24 scope global tun0
valid_lft forever preferred_lft forever
inet6 2a01:4f8:Z2/80 scope global
valid_lft forever preferred_lft forever
inet6 fe80::3214:Z3/64 scope link stable-privacy
valid_lft forever preferred_lft forever
pi@raspberrypi:~$ ip r
default via 192.168.178.1 dev eth0 proto dhcp src 192.168.178.X1 metric 1024
10.8.0.0/24 dev tun0 proto kernel scope link src 10.8.0.Z1
192.168.1.0/24 via 10.8.0.1 dev tun0
192.168.2.0/24 dev br0 proto kernel scope link src 192.168.2.1
192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.X1
192.168.178.1 dev eth0 proto dhcp scope link src 192.168.178.X1 metric 1024
pi@raspberrypi:~$ ip -6 r
::1 dev lo proto kernel metric 256 pref medium
2a01:4f8:ZZZZ::2 via fe80::2e91:X0 dev eth0 metric 1 pref medium
2a01:4f8:ZZZZ:2::/80 dev tun0 proto kernel metric 256 pref medium
2a01:4f8:ZZZZ::/64 dev tun0 metric 1024 pref medium
2a02:8071:XXXX::/64 dev eth0 proto ra metric 1024 expires 6955sec pref medium
2a02:8071:XXXX::/59 via fe80::2e91:X0 dev eth0 proto ra metric 1024 expires 1555sec pref medium
fe80::/64 dev br0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev tun0 proto kernel metric 256 pref medium
default via fe80::2e91:X0 dev eth0 proto ra metric 1024 expires 1555sec mtu 1500 pref medium
I only now noticed on https://jcorporation.github.io/myMPD/debug the section "If myMPD aborts with a segmentation fault" and changed the override.conf file again to include catchsegv, now I got some more output:
Oct 05 12:49:16 raspberrypi systemd[1]: Started myMPD server daemon.
Oct 05 12:49:16 raspberrypi catchsegv[31569]: Segmentation fault (core dumped)
Oct 05 12:49:17 raspberrypi catchsegv[31576]: *** Segmentation fault
Oct 05 12:49:17 raspberrypi catchsegv[31576]: Register dump:
Oct 05 12:49:17 raspberrypi catchsegv[31576]: R0: 01863f78 R1: 00000029 R2: 00000000 R3: 0186414c
Oct 05 12:49:17 raspberrypi catchsegv[31576]: R4: 01861300 R5: 00000000 R6: 00000000 R7: 0000f1b4
Oct 05 12:49:17 raspberrypi catchsegv[31576]: R8: 0093d004 R9: 00000008 SL: 0093caa8 FP: fff89e28
Oct 05 12:49:17 raspberrypi catchsegv[31576]: IP: 00000002 SP: fff89df0 LR: f76aa420 PC: 008359a4
Oct 05 12:49:17 raspberrypi catchsegv[31576]: CPSR: 20000010
Oct 05 12:49:17 raspberrypi catchsegv[31576]: Trap: 00000000 Error: 00000000 OldMask: 00000000
Oct 05 12:49:17 raspberrypi catchsegv[31576]: Addr: 00000000
Oct 05 12:49:17 raspberrypi catchsegv[31576]: Backtrace:
Oct 05 12:49:17 raspberrypi catchsegv[31579]: Memory map:
Oct 05 12:49:17 raspberrypi catchsegv[31579]: 00830000-0092c000 r-xp 00000000 b3:02 1177506 /usr/bin/mympd
Oct 05 12:49:17 raspberrypi catchsegv[31579]: 0093c000-0093d000 r--p 000fc000 b3:02 1177506 /usr/bin/mympd
Oct 05 12:49:17 raspberrypi catchsegv[31579]: 0093d000-0093e000 rw-p 000fd000 b3:02 1177506 /usr/bin/mympd
Oct 05 12:49:17 raspberrypi catchsegv[31579]: 0185d000-0187e000 rw-p 00000000 00:00 0 [heap]
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f74ca000-f74e6000 r-xp 00000000 b3:02 1177673 /lib/arm-linux-gnueabihf/libgcc_s.so.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f74e6000-f74f5000 ---p 0001c000 b3:02 1177673 /lib/arm-linux-gnueabihf/libgcc_s.so.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f74f5000-f74f6000 r--p 0001b000 b3:02 1177673 /lib/arm-linux-gnueabihf/libgcc_s.so.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f74f6000-f74f7000 rw-p 0001c000 b3:02 1177673 /lib/arm-linux-gnueabihf/libgcc_s.so.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f74f7000-f7555000 r-xp 00000000 b3:02 1181198 /lib/arm-linux-gnueabihf/libm-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7555000-f7564000 ---p 0005e000 b3:02 1181198 /lib/arm-linux-gnueabihf/libm-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7564000-f7565000 r--p 0005d000 b3:02 1181198 /lib/arm-linux-gnueabihf/libm-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7565000-f7566000 rw-p 0005e000 b3:02 1181198 /lib/arm-linux-gnueabihf/libm-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7566000-f756c000 r-xp 00000000 b3:02 1189223 /usr/lib/arm-linux-gnueabihf/libogg.so.0.8.4
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f756c000-f757b000 ---p 00006000 b3:02 1189223 /usr/lib/arm-linux-gnueabihf/libogg.so.0.8.4
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f757b000-f757c000 r--p 00005000 b3:02 1189223 /usr/lib/arm-linux-gnueabihf/libogg.so.0.8.4
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f757c000-f757d000 rw-p 00006000 b3:02 1189223 /usr/lib/arm-linux-gnueabihf/libogg.so.0.8.4
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f757d000-f758f000 r-xp 00000000 b3:02 1177733 /lib/arm-linux-gnueabihf/libz.so.1.2.11
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f758f000-f759e000 ---p 00012000 b3:02 1177733 /lib/arm-linux-gnueabihf/libz.so.1.2.11
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f759e000-f759f000 r--p 00011000 b3:02 1177733 /lib/arm-linux-gnueabihf/libz.so.1.2.11
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f759f000-f75a0000 rw-p 00012000 b3:02 1177733 /lib/arm-linux-gnueabihf/libz.so.1.2.11
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f75a0000-f75a3000 r-xp 00000000 b3:02 1181197 /lib/arm-linux-gnueabihf/libdl-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f75a3000-f75b2000 ---p 00003000 b3:02 1181197 /lib/arm-linux-gnueabihf/libdl-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f75b2000-f75b3000 r--p 00002000 b3:02 1181197 /lib/arm-linux-gnueabihf/libdl-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f75b3000-f75b4000 rw-p 00003000 b3:02 1181197 /lib/arm-linux-gnueabihf/libdl-2.31.so
Oct 05 12:49:17 raspberrypi systemd[1]: mympd.service: Main process exited, code=exited, status=139/n/a
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f75b4000-f76f2000 r-xp 00000000 b3:02 1181196 /lib/arm-linux-gnueabihf/libc-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f76f2000-f7701000 ---p 0013e000 b3:02 1181196 /lib/arm-linux-gnueabihf/libc-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7701000-f7703000 r--p 0013d000 b3:02 1181196 /lib/arm-linux-gnueabihf/libc-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7703000-f7704000 rw-p 0013f000 b3:02 1181196 /lib/arm-linux-gnueabihf/libc-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7704000-f7707000 rw-p 00000000 00:00 0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7707000-f772c000 r-xp 00000000 b3:02 1177522 /usr/lib/arm-linux-gnueabihf/liblua5.4.so.0.0.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f772c000-f773c000 ---p 00025000 b3:02 1177522 /usr/lib/arm-linux-gnueabihf/liblua5.4.so.0.0.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f773c000-f773d000 r--p 00025000 b3:02 1177522 /usr/lib/arm-linux-gnueabihf/liblua5.4.so.0.0.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f773d000-f773e000 rw-p 00026000 b3:02 1177522 /usr/lib/arm-linux-gnueabihf/liblua5.4.so.0.0.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f773e000-f775f000 r-xp 00000000 b3:02 1177937 /usr/lib/arm-linux-gnueabihf/libFLAC.so.8.3.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f775f000-f776f000 ---p 00021000 b3:02 1177937 /usr/lib/arm-linux-gnueabihf/libFLAC.so.8.3.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f776f000-f7770000 r--p 00021000 b3:02 1177937 /usr/lib/arm-linux-gnueabihf/libFLAC.so.8.3.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7770000-f7771000 rw-p 00022000 b3:02 1177937 /usr/lib/arm-linux-gnueabihf/libFLAC.so.8.3.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7771000-f777f000 r-xp 00000000 b3:02 1189121 /usr/lib/arm-linux-gnueabihf/libid3tag.so.0.3.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f777f000-f778f000 ---p 0000e000 b3:02 1189121 /usr/lib/arm-linux-gnueabihf/libid3tag.so.0.3.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f778f000-f7790000 r--p 0000e000 b3:02 1189121 /usr/lib/arm-linux-gnueabihf/libid3tag.so.0.3.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7790000-f7791000 rw-p 0000f000 b3:02 1189121 /usr/lib/arm-linux-gnueabihf/libid3tag.so.0.3.0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7791000-f7985000 r-xp 00000000 b3:02 1177530 /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7985000-f7994000 ---p 001f4000 b3:02 1177530 /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7994000-f79ad000 r--p 001f3000 b3:02 1177530 /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f79ad000-f79ae000 rw-p 0020c000 b3:02 1177530 /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f79ae000-f79b2000 rw-p 00000000 00:00 0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f79b2000-f7a1b000 r-xp 00000000 b3:02 1177531 /usr/lib/arm-linux-gnueabihf/libssl.so.1.1
Oct 05 12:49:17 raspberrypi systemd[1]: mympd.service: Failed with result 'exit-code'.
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7a1b000-f7a2a000 ---p 00069000 b3:02 1177531 /usr/lib/arm-linux-gnueabihf/libssl.so.1.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7a2a000-f7a30000 r--p 00068000 b3:02 1177531 /usr/lib/arm-linux-gnueabihf/libssl.so.1.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7a30000-f7a33000 rw-p 0006e000 b3:02 1177531 /usr/lib/arm-linux-gnueabihf/libssl.so.1.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7a33000-f7a98000 r-xp 00000000 b3:02 1181106 /usr/lib/arm-linux-gnueabihf/libpcre2-8.so.0.10.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7a98000-f7aa7000 ---p 00065000 b3:02 1181106 /usr/lib/arm-linux-gnueabihf/libpcre2-8.so.0.10.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7aa7000-f7aa8000 r--p 00064000 b3:02 1181106 /usr/lib/arm-linux-gnueabihf/libpcre2-8.so.0.10.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7aa8000-f7aa9000 rw-p 00065000 b3:02 1181106 /usr/lib/arm-linux-gnueabihf/libpcre2-8.so.0.10.1
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7aa9000-f7ac1000 r-xp 00000000 b3:02 1181206 /lib/arm-linux-gnueabihf/libpthread-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7ac1000-f7ad1000 ---p 00018000 b3:02 1181206 /lib/arm-linux-gnueabihf/libpthread-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7ad1000-f7ad2000 r--p 00018000 b3:02 1181206 /lib/arm-linux-gnueabihf/libpthread-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7ad2000-f7ad3000 rw-p 00019000 b3:02 1181206 /lib/arm-linux-gnueabihf/libpthread-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7ad3000-f7ad5000 rw-p 00000000 00:00 0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7ae6000-f7ae8000 r-xp 00000000 b3:02 1181194 /lib/arm-linux-gnueabihf/libSegFault.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7ae8000-f7af7000 ---p 00002000 b3:02 1181194 /lib/arm-linux-gnueabihf/libSegFault.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7af7000-f7af8000 r--p 00001000 b3:02 1181194 /lib/arm-linux-gnueabihf/libSegFault.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7af8000-f7af9000 rw-p 00002000 b3:02 1181194 /lib/arm-linux-gnueabihf/libSegFault.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7af9000-f7b1b000 r-xp 00000000 b3:02 1177365 /lib/arm-linux-gnueabihf/ld-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7b24000-f7b2a000 rw-p 00000000 00:00 0
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7b2a000-f7b2b000 r-xp 00000000 00:00 0 [sigpage]
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7b2b000-f7b2c000 r--p 00022000 b3:02 1177365 /lib/arm-linux-gnueabihf/ld-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: f7b2c000-f7b2d000 rw-p 00023000 b3:02 1177365 /lib/arm-linux-gnueabihf/ld-2.31.so
Oct 05 12:49:17 raspberrypi catchsegv[31579]: fff6a000-fff8b000 rw-p 00000000 00:00 0 [stack]
Oct 05 12:49:17 raspberrypi catchsegv[31579]: ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]
Log is not very helpful, but I think I found a bug. I will patch devel today. A chance that you can test the devel branch?
I can try to compile it later tonight, but would appreciate a .deb for armhf if you have any.
-- gesendet von einem mobilen Endgerät
On Thu, 5 Oct 2023, 16:50 Jürgen Mang, @.***> wrote:
Log is not very helpful, but I think I found a bug. I will patch devel today. A chance that you can test the devel branch?
— Reply to this email directly, view it on GitHub https://github.com/jcorporation/myMPD/issues/1121#issuecomment-1749065366, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAANFEPOHL23MVY66OQI3BLX53CK7AVCNFSM6AAAAAA5TMRKNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGA3DKMZWGY . You are receiving this because you authored the thread.Message ID: @.***>
Patch is now in devel. There is no .deb for devel available.
I could compile it without issues.
First compiled master to successfully reproduce the issue, then devel which starts without issues :rocket:
This fixes a SEGV (probably same issue, an strace gave no hints, but i am not savvy at that anyway) on Debian x86_64 trixie/sid with mpd 0.23.12.
@therion23 but 12.0.4 works also for you?
Just tested - yes, 12.0.4-release fixed it (missed its release apparently), only 12.0.3 had that issue.
myMPD version: 12.0.3-1
Describe the bug
I just upgraded to the latest release, now the service does not start anymore. It fails with signal=SEGV.
To Reproduce
sudo systemctl daemon-reload
sudo systemctl restart mympd.service
As several attempts were failing and I deleted
/var/cache/mympd
and/var/cache/private/mympd
. Deleting those did not help, I rebooted, but the issue remains.Expected behavior
Service starts.
Screenshots
N/A
Server plattform (please complete the following information):
Client plattform (please complete the following information):
N/A
Debug logs (please attach if it can be useful)
First crash and content of custom config:
Installed systemd-coredump to get more details, rebooted, then tried to manually start:
I did not terminate systemd-run. From https://jcorporation.github.io/myMPD/debug I understand that it should continue running in foreground.
Configuration (please attach if it can be useful)
Please ping me if you need this.
tar -cf mympd_state.tar /var/lib/mympd/state
)tar -cf mympd_config.tar /var/lib/mympd/config
)mpd.conf
Additional context
My first guess is an incompatible glibc or another core library.
Earlier I installed some updates, but rebooted and the mympd service did start without problems.
Extended version info: