| Summary: | avahi-daemon fail to start with qemumips sdk image | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Jiajun Xu <jiajun.xu> |
| Component: | meta-yocto | Assignee: | 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
I tried same SDK image copied from you. Avahi just launched successfully. A bit weird... (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. 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? Can anyone reproduce this bug now? I think no. Perhaps we can lower its priority to low, until we reproduce it again... 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 (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. (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. (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. (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. 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. I reported a new bug to trace this issue. Please see bug 1699. (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 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. verified on nightly build 20111117-4: http://autobuilder.pokylinux.org/nightly/20111117-4/machines/ git branch : poky/master git info : f2d077255d9ddf9b87e9a781b989bcce69047cf5 |