* [Buildroot] [Bug 12586] New: avahi failure
@ 2020-02-28 5:08 bugzilla at busybox.net
2020-02-28 5:09 ` [Buildroot] [Bug 12586] " bugzilla at busybox.net
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: bugzilla at busybox.net @ 2020-02-28 5:08 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=12586
Bug ID: 12586
Summary: avahi failure
Product: buildroot
Version: 2019.11.1
Hardware: All
OS: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: sam.petrocelli at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 8376
--> https://bugs.busybox.net/attachment.cgi?id=8376&action=edit
.config file
It seems some systemd services are failing to load on start up. In particular,
I get the following avahi error:
# systemctl status avahi-daemon.service[J
avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-11-19 05:15:16 EST; 1h
13min ago
Process: 1860 ExecStart=/usr/sbin/avahi-daemon -s (code=exited,
status=255/EXCEPTION)
Main PID: 1860 (code=exited, status=255/EXCEPTION)
Nov 19 05:15:16 morepork systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Nov 19 05:15:16 morepork avahi-daemon[1860]: Failed to find user 'avahi'.
Nov 19 05:15:16 morepork systemd[1]: avahi-daemon.service: Main process exited,
code=exited, status=255/EXCEPTION
Nov 19 05:15:16 morepork systemd[1]: avahi-daemon.service: Failed with result
'exit-code'.
Nov 19 05:15:16 morepork systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
Nov 19 05:15:16 morepork systemd[1]: avahi-daemon.service: Start request
repeated too quickly.
Nov 19 05:15:16 morepork systemd[1]: avahi-daemon.service: Failed with result
'exit-code'.
Nov 19 05:15:16 morepork systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] [Bug 12586] avahi failure
2020-02-28 5:08 [Buildroot] [Bug 12586] New: avahi failure bugzilla at busybox.net
@ 2020-02-28 5:09 ` bugzilla at busybox.net
2020-02-28 12:36 ` bugzilla at busybox.net
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: bugzilla at busybox.net @ 2020-02-28 5:09 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=12586
--- Comment #1 from Sam Petrocelli <sam.petrocelli@gmail.com> ---
Created attachment 8381
--> https://bugs.busybox.net/attachment.cgi?id=8381&action=edit
busybox.config
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] [Bug 12586] avahi failure
2020-02-28 5:08 [Buildroot] [Bug 12586] New: avahi failure bugzilla at busybox.net
2020-02-28 5:09 ` [Buildroot] [Bug 12586] " bugzilla at busybox.net
@ 2020-02-28 12:36 ` bugzilla at busybox.net
2020-03-02 4:37 ` bugzilla at busybox.net
2020-05-18 7:34 ` bugzilla at busybox.net
3 siblings, 0 replies; 5+ messages in thread
From: bugzilla at busybox.net @ 2020-02-28 12:36 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=12586
--- Comment #2 from Peter Seiderer <ps.report@gmx.net> ---
Your .config enables no filesystem image, how do you run it on the target?
Note that the result under target is not a usable filesystem (see e.g.
cat target/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM) and will miss the user/group
entries for avahi...
On the target the following avahi user/group entries should exist:
$ grep avahi /etc/passwd
avahi:x:1000:1000::/:/bin/false
$ grep avahi /etc/group
avahi:x:1000:
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] [Bug 12586] avahi failure
2020-02-28 5:08 [Buildroot] [Bug 12586] New: avahi failure bugzilla at busybox.net
2020-02-28 5:09 ` [Buildroot] [Bug 12586] " bugzilla at busybox.net
2020-02-28 12:36 ` bugzilla at busybox.net
@ 2020-03-02 4:37 ` bugzilla at busybox.net
2020-05-18 7:34 ` bugzilla at busybox.net
3 siblings, 0 replies; 5+ messages in thread
From: bugzilla at busybox.net @ 2020-03-02 4:37 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=12586
--- Comment #3 from Sam Petrocelli <sam.petrocelli@gmail.com> ---
Thanks for the reply. Yeah, I guess that's where the problem is. Unfortunately,
developers that came before have configured the system such that we have custom
python scripts that copy the files out of target and staging and we create a
file system outside of buildroot ourselves. (We also have a similar thing going
on for the kernel as well). I am in the process of getting everything undated
and standardized. What we want right now is a way that we can essentially copy
all of these files for the rootfs out. I see that if we make a tar fs, all the
passwd systemd, avahi, etc is all in there, but we want these files without
having to deal with untar. Do you have any suggestions for this? Thank you.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] [Bug 12586] avahi failure
2020-02-28 5:08 [Buildroot] [Bug 12586] New: avahi failure bugzilla at busybox.net
` (2 preceding siblings ...)
2020-03-02 4:37 ` bugzilla at busybox.net
@ 2020-05-18 7:34 ` bugzilla at busybox.net
3 siblings, 0 replies; 5+ messages in thread
From: bugzilla at busybox.net @ 2020-05-18 7:34 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=12586
Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
Hello Sam. You can write your own filesystem image logic in Buildroot, so that
you can re-use everything Buildroot does under "fakeroot", such as creating
users, adjusting permissions and ownerships, etc. I believe you can even add
your own filesystem format in your separate BR2_EXTERNAL tree, if you're using
that.
In any case, there's nothing to fix in Buildroot here: we explicitly state that
the contents of output/target is not the final root filesystem, and this cannot
be changed as Buildroot does not run as root.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-05-18 7:34 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-28 5:08 [Buildroot] [Bug 12586] New: avahi failure bugzilla at busybox.net
2020-02-28 5:09 ` [Buildroot] [Bug 12586] " bugzilla at busybox.net
2020-02-28 12:36 ` bugzilla at busybox.net
2020-03-02 4:37 ` bugzilla at busybox.net
2020-05-18 7:34 ` bugzilla at busybox.net
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.