We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Thanks for the report. Is this still occurring for anyone in a recent
release of Ubuntu?
** Changed in: avahi (Ubuntu)
Status: Confirmed = Incomplete
--
feisty avahi-autoipd fails on fopen()
https://bugs.launchpad.net/bugs/83521
You received this bug notification because you are a
I am having similar problems with avahi permissions on 7.10 avahi
version 0.6.20
--
feisty avahi-autoipd fails on fopen()
https://bugs.launchpad.net/bugs/83521
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
This report appears to be remarkably similar to bug #78078.
--
feisty avahi-autoipd fails on fopen()
https://bugs.launchpad.net/bugs/83521
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Yes, except that I did not experience any network connection issue like
there. So... I am not sure.
Anyway, since then I purged Avahi from my laptop -- given that I float
around on cellular, hotel, and public wireless, I really do not want
Avahi broadcast/discover... so it is gone , and I cannot
Confirmed in feisty, avahi-daemon version 0.6.17-0ubuntu3.
Attached my last boot daemon.log.
** Attachment added: daemon.log
http://launchpadlibrarian.net/8130751/daemon.log
** Changed in: avahi (Ubuntu)
Status: Unconfirmed = Confirmed
--
feisty avahi-autoipd fails on fopen()
My wireless connection is failing with the same symptoms. If I take off
all encryption, deleting the /var/lib/avahi-autoipd directory works,
however if using WPA personal I can't get a connection. This problem
started occurring after updating from edgy to the feisty fawn release.
--
feisty
strace output at the fopen() error:
write(2, Found user \'avahi-autoipd\' (UID ..., 73) = 73
write(2, \n, 1) = 1
umask(0)= 022
mkdir(/var/lib/avahi-autoipd, 0755) = -1 EEXIST (File exists)
umask(022) = 0
well, this seems to have been a fluke, perhaps caused by a previous
version of avahi-autoipd.
After I stopped avahi-autoipd, deleted the /var/lib/avahi-autoipd
directory, and restarted it, it went without any glitches.
I will keep on trying but, right now, I am considering it as a fluke.
--
nope, not a fluke. I rebooted and, after the reboot I get this:
Feb 6 11:51:10 xango avahi-autoipd(eth1)[25328]: Found user 'avahi-autoipd'
(UID 107) and group 'avahi-autoipd' (G
ID 113).
Feb 6 11:51:10 xango avahi-autoipd(eth1)[25328]: Successfully called chroot().
Feb 6 11:51:10 xango
Can you run
ls -la /var/lib/avahi-autoipd
and paste the output? (when this problem is occuring)
--
feisty avahi-autoipd fails on fopen()
https://launchpad.net/bugs/83521
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sure. It is happening right now. In fact, it happens every time, unless
I remove /var/lib/avahi-autoipd. Then, on the first run, no problems.
[EMAIL PROTECTED]:/var/lib$ ls -la avahi-autoipd/
total 10
drwxr-xr-x 2 avahi-autoipd avahi-autoipd 128 2007-02-06 11:53 .
drwxr-xr-x 72 root
And, looking at both the source code and at the strace output above, we
see the reason for the file permissions... umask () would do that.
Additionally, *after* chrooting to /var/lib/avahi-autoipd, we see two
failed open() calls:
open(/proc/sys/kernel/ngroups_max, O_RDONLY) = -1 ENOENT (No
I have attached two runs of avahi-autoipd, done as follows:
1. sudo avahi-autoipd -k eth0
2. sudo rm -rf /var/lib/avahi-autoipd
3. sudo strace -ff -v -x -o avahi-autoipd-strace avahi-autoipd -D eth0
(on another terminal, after avahi got stable)
4. sudo avahi-autoipd -k eth0
The collected
14 matches
Mail list logo
