Bugzilla – Bug 13717
SBC r7275 fails DNS due to missing ip (no DHCP client daemon running)
Last modified: 2009-10-05 14:25:38 UTC
when the SBC is both controller and player, and connected to test.sn, I don't get served any music services or radio menus. The only menus I see are: now playing, my music, choose player, settings. This happens after creating a NEW account, that has not been registered yet. ----------------- Activating the account did not change the behavior on the SBC ----------------- rebooting SBC will reduce the menu to 3 items (removes choose player)
Note: this also happens if SBR is selected as the player
Created attachment 5708 [details] DNS error?
There is no DHCP client running. This seems to happen after a fw update. # ps -efw UID PID PPID C STIME TTY TIME CMD root 1 0 0 00:29 ? 00:00:02 init root 2 0 0 00:29 ? 00:00:00 [kthreadd] root 3 2 0 00:29 ? 00:00:00 [ksoftirqd/0] root 4 2 0 00:29 ? 00:00:00 [watchdog/0] root 5 2 0 00:29 ? 00:00:00 [events/0] root 6 2 0 00:29 ? 00:00:00 [khelper] root 40 2 0 00:29 ? 00:00:00 [kblockd/0] root 41 2 0 00:29 ? 00:00:00 [kseriod] root 53 2 0 00:29 ? 00:00:00 [pdflush] root 54 2 0 00:29 ? 00:00:00 [pdflush] root 55 2 0 00:29 ? 00:00:00 [kswapd0] root 56 2 0 00:29 ? 00:00:00 [aio/0] root 57 2 0 00:29 ? 00:00:00 [unionfs_siod/0] root 163 2 0 00:29 ? 00:00:02 [mtdblockd] root 189 2 0 00:29 ? 00:00:00 [s3c24xx-spi-gpi] root 193 2 0 00:30 ? 00:00:00 [s3c24xx-spi-gpi] root 214 2 0 00:30 ? 00:00:00 [kmmcd] root 224 2 0 00:30 ? 00:00:00 [mmcqd] root 246 2 0 00:30 ? 00:00:00 [jffs2_gcd_mtd2] root 275 1 0 00:30 ? 00:00:00 /sbin/udevd -d root 399 1 0 00:30 ? 00:00:01 /sbin/syslogd -S root 466 1 0 00:30 ? 00:00:00 /sbin/klogd root 516 1 0 00:30 ? 00:00:00 /usr/sbin/watchdog root 536 1 0 00:30 ? 00:00:00 /usr/sbin/inetd root 547 2 0 00:30 ? 00:00:11 [wlan_main_servi] root 549 2 0 00:30 ? 00:00:00 [wlan_reassoc_se] root 564 1 0 00:30 ? 00:00:00 /usr/sbin/wpa_supplicant -B -Dma rvell -ieth0 -c/etc/wpa_supplicant.conf root 566 1 0 00:30 ? 00:00:00 /usr/sbin/wpa_cli -B -a/etc/netw ork/wpa_action root 572 1 7 00:30 ? 00:01:44 /usr/bin/jive root 573 1 0 00:30 ? 00:00:00 /bin/sh root 574 1 0 00:30 tty3 00:00:00 /sbin/getty tty3 9600 VC vt100 root 611 572 1 00:30 ? 00:00:26 jive_alsa -d default -c default -b 30000 -p 2 -s 16 -f 3 root 989 516 0 00:52 ? 00:00:00 [watchdog] <defunct> root 990 573 0 00:52 ? 00:00:00 ps -efw #
It looks like if the timing between starting DHCP client daemon and wireless connecting to the AP can cause DHCP daemon to die.
== Auto-comment from SVN commit #7305 to the jive repo by felix == == https://svn.slimdevices.com/jive?view=revision&revision=7305 == Bug: 13717 +8 Description: Fix signaling udhcpc unintentionally killing it
DHCP daemon could be terminated while starting if a signal to do a renewal was received in the wrong moment. This should be fixed with r7305.
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.