RPCD crash
In ticket #1498457, the user reported, that LuCI fails to load with a Session expired
error note. He managed to figure out that it crashes on a RPC call:
I have managed to discover that the following ubus call causes rpcd to crash (and subsequent timeout):
# ubus call luci-rpc getWirelessDevices Command failed: Request timed out The tail of strace from rpcd: open("/var/run/hostapd-phy0.conf", O_RDONLY|O_LARGEFILE) = 9 read(9, "driver=nl80211\nlogger_syslog=127"..., 1024) = 1024 read(9, "key_retries=0\nwpa_key_mgmt=WPA-P"..., 1024) = 1024 read(9, "lan0-2\nctrl_interface=/var/run/h"..., 1024) = 726 read(9, "", 1024) = 0 close(9) = 0 socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 9 ioctl(9, SIOCGIFINDEX, {ifr_name="wlan0", ifr_ifindex=27}) = 0 close(9) = 0 sendmsg(7, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, msg_namelen=12, msg_iov=[{iov_base=[{nlmsg_len=28, nlmsg_type=nl80211, nlmsg_flags=NLM_F_REQUEST|NLM_F_ACK, nlmsg_seq=1666818885, nlmsg_pid=27139}, "\x01\x00\x00\x00\x08\x00\x03\x00\x1b\x00\x00\x00"], iov_len=28}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 28 recvmsg(7, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, msg_namelen=12, msg_iov=[{iov_base=[{nlmsg_len=2248, nlmsg_type=nl80211, nlmsg_flags=0, nlmsg_seq=1666818885, nlmsg_pid=27139}, "\x03\x01\x00\x00\x08\x00\x01\x00\x00\x00\x00\x00\x09\x00\x02\x00\x70\x68\x79\x30\x00\x00\x00\x00\x08\x00\x2e\x00\x02\x00\x00\x00"...], iov_len=16384}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 2248 recvmsg(7, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, msg_namelen=12, msg_iov=[{iov_base=[{nlmsg_len=36, nlmsg_type=NLMSG_ERROR, nlmsg_flags=NLM_F_CAPPED, nlmsg_seq=1666818885, nlmsg_pid=27139}, {error=0, msg={nlmsg_len=28, nlmsg_type=nl80211, nlmsg_flags=NLM_F_REQUEST|NLM_F_ACK, nlmsg_seq=1666818885, nlmsg_pid=27139}}], iov_len=16384}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 36 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} --- +++ killed by SIGSEGV +++
Not sure how to interpret this.