Bug 144

Summary: avahi-daemon fail to start with qemumips sdk image
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Jiajun Xu <jiajun.xu>
Component: meta-yoctoAssignee: Saul Wold <sgw>
Status: VERIFIED FIXED QA Contact:
Severity: minor    
Priority: Medium CC: jiajun.xu, kevin.tian, liang.li2, poky.bs.watcher, poky.watcher, richard.purdie, sgw, susie.li, xianchao.zhang, yi.zhao, yongkang.you
Version: 0.9   
Target Milestone: 0.9 M4   
Hardware: x86   
OS: mips   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---

Description Jiajun Xu 2010-07-26 19:58:11 UTC
Testing Env:    
Host: Ubuntu 10.04 LTS
Kernel: 2.6.32-21-generic-pae
Poky gitinfo(used to build qemu-native):
faf6b2d33e8ce7fe7fdf5d8379b19c2e49b8c997 (git://git.pokylinux.org/poky.git)
Image location: http://yoctobuild01.jf.intel.com/milestone/20100725-1/

With qemumips sdk image from milestone build, avahi-daemon fails to start. It prompts that "Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory"

#######
$ avahi-daemon
Found user 'avahi' (UID 43) and group 'avahi' (GID 103)
Successfully dropped root privileges.
avahi-daemon 0.6.27 starting up.
dbus_bus_get_private(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
WARNING: Failed to contact D-Bus daemon
avahi-daemon 0.6.27 exiting.
#######
Comment 1 Kevin Tian 2010-07-27 04:26:53 UTC
I tried same SDK image copied from you. Avahi just launched successfully. A bit weird...
Comment 2 Jiajun Xu 2010-07-27 05:43:31 UTC
(In reply to comment #1)
> I tried same SDK image copied from you. Avahi just launched successfully. A bit
> weird...

Strange. Let's check it tomorrow.
Comment 3 Jiajun Xu 2010-07-28 05:56:19 UTC
Today Kevin and I checked on my machine, it even cannot be reproduced again on my machine. So how about mark the bug as "minor" and track the status in M3?
Comment 4 Qing He 2010-08-11 19:59:08 UTC
Can anyone reproduce this bug now?
Comment 5 Kevin Tian 2010-08-11 20:11:33 UTC
I think no. Perhaps we can lower its priority to low, until we reproduce it again...
Comment 6 xianchao zhang 2010-09-07 02:12:33 UTC
I have tried with M3 images(20100905), and found avahi-daemon has not started, and
If run it by hand, will arise segment fault

steps to reproduce:

1. download image
2. boot up with sdk image
3. run command like this:

root@qemumips:~# connmand
 Segmentation fault
Comment 7 Jiajun Xu 2010-09-07 08:38:28 UTC
(In reply to comment #6)
> I have tried with M3 images(20100905), and found avahi-daemon has not started,
> and
> If run it by hand, will arise segment fault
> steps to reproduce:
> 1. download image
> 2. boot up with sdk image
> 3. run command like this:
> root@qemumips:~# connmand
>  Segmentation fault

Xianchao,
The bug is for avahi-daemon. But according to your comments, since you tried to run connmand, not avahi-daemon.
Comment 8 xianchao zhang 2010-09-07 23:51:15 UTC
(In reply to comment #7)
> (In reply to comment #6)
> > I have tried with M3 images(20100905), and found avahi-daemon has not started,
> > and
> > If run it by hand, will arise segment fault
> > steps to reproduce:
> > 1. download image
> > 2. boot up with sdk image
> > 3. run command like this:
> > root@qemumips:~# connmand
> >  Segmentation fault
> 
> Xianchao,
> The bug is for avahi-daemon. But according to your comments, since you tried to
> run connmand, not avahi-daemon.

Sorry, I make a mistake. the above comments should be for connmand segfault issue with sato/sdk with qemumips.
Comment 9 Jiajun Xu 2010-09-07 23:56:37 UTC
(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > I have tried with M3 images(20100905), and found avahi-daemon has not started,
> > > and
> > > If run it by hand, will arise segment fault
> > > steps to reproduce:
> > > 1. download image
> > > 2. boot up with sdk image
> > > 3. run command like this:
> > > root@qemumips:~# connmand
> > >  Segmentation fault
> > 
> > Xianchao,
> > The bug is for avahi-daemon. But according to your comments, since you tried to
> > run connmand, not avahi-daemon.
> Sorry, I make a mistake. the above comments should be for connmand segfault
> issue with sato/sdk with qemumips.

Xianchao,
Do you meet avahi-daemon issue with qemumips image? If not, you can mark the bug as RESOLVED FIXED and verifiy it.
Comment 10 xianchao zhang 2010-09-08 00:21:16 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > (In reply to comment #6)
> > > > I have tried with M3 images(20100905), and found avahi-daemon has not started,
> > > > and
> > > > If run it by hand, will arise segment fault
> > > > steps to reproduce:
> > > > 1. download image
> > > > 2. boot up with sdk image
> > > > 3. run command like this:
> > > > root@qemumips:~# connmand
> > > >  Segmentation fault
> > > 
> > > Xianchao,
> > > The bug is for avahi-daemon. But according to your comments, since you tried to
> > > run connmand, not avahi-daemon.
> > Sorry, I make a mistake. the above comments should be for connmand segfault
> > issue with sato/sdk with qemumips.
> 
> Xianchao,
> Do you meet avahi-daemon issue with qemumips image? If not, you can mark the
> bug as RESOLVED FIXED and verifiy it.

Already done.
Comment 11 liang li 2011-10-24 23:28:50 UTC
It also happend on sato,sato-sdk images of qemuppc and qemumips and sato-sdk images of mpc8315e-rdb in nightly build (20111023-1) from below:
http://autobuilder.pokylinux.org/nightly/20111023-1/machines/

form boot messages ,get below error:
Starting syslogd/klogd: done
 * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon                       [fail]

from target images , run "ps -ef | grep connmand" ,below error:
root@mpc8315e-rdb:/etc/init.d# ps -ef | grep connmand
root     17358   313  0 14:27 pts/0    00:00:00 grep connmand
root@mpc8315e-rdb:/etc/init.d# 

the connmand process not startup when the target images start up.
Comment 12 Yi Zhao 2011-10-25 01:57:00 UTC
I reported a new bug to trace this issue. Please see bug 1699.
Comment 13 liang li 2011-11-15 20:00:51 UTC
(In reply to comment #11)
> It also happend on sato,sato-sdk images of qemuppc and qemumips and sato-sdk
> images of mpc8315e-rdb in nightly build (20111023-1) from below:
> http://autobuilder.pokylinux.org/nightly/20111023-1/machines/
> 
> form boot messages ,get below error:
> Starting syslogd/klogd: done
>  * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon                       [fail]
> 
> from target images , run "ps -ef | grep connmand" ,below error:
> root@mpc8315e-rdb:/etc/init.d# ps -ef | grep connmand
> root     17358   313  0 14:27 pts/0    00:00:00 grep connmand
> root@mpc8315e-rdb:/etc/init.d# 
> 
> the connmand process not startup when the target images start up.

use sato,sato-sdk images built manually on git master branch,the error not met.
git info :acbf65b9a6f14ed2b2f471e104c30cca11647b6c
Comment 14 Richard Purdie 2011-11-24 11:07:30 UTC
The various useradd.bbclass fixed have meant this is now fixed in master. It was being caused by the avahi user creation code failing to work correctly.
Comment 15 liang li 2011-11-24 18:37:56 UTC
verified on nightly build 20111117-4:
http://autobuilder.pokylinux.org/nightly/20111117-4/machines/
git branch : poky/master
git info : f2d077255d9ddf9b87e9a781b989bcce69047cf5