You are not logged in.

#1 2016-03-15 19:40:00

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

[Solved] Avahi, misbehaviors

Hello,

I found some problems to setup with avahi. Which I need to use in conjunction with cups.
Once installed, there's no user, nor group creation for avahi. Also the directory /run/avahi and its symlink are missing.
I fixed these issues manually, but today /run/avahi has disappeared.

$ grep -E '\[2016-03-1[4-6].*' /var/log/pacman.log   
[2016-03-14 16:15] [PACMAN] Running 'pacman --color auto -Sy'
[2016-03-14 16:15] [PACMAN] synchronizing package lists
[2016-03-14 16:15] [PACMAN] Running 'pacman --color auto -Sy'
[2016-03-14 16:15] [PACMAN] synchronizing package lists
[2016-03-14 08:16] [PACMAN] Running 'pacman --color auto -S -u'
[2016-03-14 08:16] [PACMAN] starting full system upgrade
[2016-03-14 08:17] [ALPM] running '70-dkms-remove.hook'...
[2016-03-14 08:17] [ALPM] transaction started
[2016-03-14 08:17] [ALPM] upgraded c-ares (1.10.0-2 -> 1.11.0-1)
[2016-03-14 08:17] [ALPM] upgraded libldap (2.4.43-3 -> 2.4.44-1)
[2016-03-14 08:17] [ALPM] upgraded virtualbox-host-dkms (5.0.16-1 -> 5.0.16-3)
[2016-03-14 08:17] [ALPM-SCRIPTLET] ==> Since version 5.0.16-2 kernel modules are loaded at boot by systemd-modules-load.
[2016-03-14 08:17] [ALPM-SCRIPTLET] ==> Read modules-load.d man page to disable them.
[2016-03-14 08:17] [ALPM] upgraded virtualbox (5.0.16-1 -> 5.0.16-3)
[2016-03-14 08:17] [ALPM] upgraded virtualbox-guest-dkms (5.0.16-1 -> 5.0.16-3)
[2016-03-14 08:17] [ALPM-SCRIPTLET] ==> Since version 5.0.16-2 kernel modules are loaded at boot by systemd-modules-load.
[2016-03-14 08:17] [ALPM-SCRIPTLET] ==> Read modules-load.d man page to disable them.
[2016-03-14 08:17] [ALPM] upgraded virtualbox-sdk (5.0.16-1 -> 5.0.16-3)
[2016-03-14 08:17] [ALPM] transaction completed
[2016-03-14 08:17] [ALPM] running '70-dkms-install.hook'...
[2016-03-14 08:17] [ALPM-SCRIPTLET] 
[2016-03-14 08:17] [ALPM-SCRIPTLET] Creating symlink /var/lib/dkms/vboxguest/5.0.16_OSE/source ->
[2016-03-14 08:17] [ALPM-SCRIPTLET]                  /usr/src/vboxguest-5.0.16_OSE
[2016-03-14 08:17] [ALPM-SCRIPTLET] 
[2016-03-14 08:17] [ALPM-SCRIPTLET] DKMS: add completed.
[2016-03-14 08:17] [ALPM-SCRIPTLET] 
[2016-03-14 08:17] [ALPM-SCRIPTLET] Kernel preparation unnecessary for this kernel.  Skipping...
[2016-03-14 08:17] [ALPM-SCRIPTLET] 
[2016-03-14 08:17] [ALPM-SCRIPTLET] Building module:
[2016-03-14 08:17] [ALPM-SCRIPTLET] cleaning build area...
[2016-03-14 08:18] [ALPM-SCRIPTLET] make KERNELRELEASE=4.4.5-1-ARCH -C /usr/lib/modules/4.4.5-1-ARCH/build M=/var/lib/dkms/vboxguest/5.0.16_OSE/build...............
[2016-03-14 08:18] [ALPM-SCRIPTLET] cleaning build area...
[2016-03-14 08:18] [ALPM-SCRIPTLET] Kernel cleanup unnecessary for this kernel.  Skipping...
[2016-03-14 08:18] [ALPM-SCRIPTLET] 
[2016-03-14 08:18] [ALPM-SCRIPTLET] DKMS: build completed.
[2016-03-14 08:18] [ALPM-SCRIPTLET] 
[2016-03-14 08:18] [ALPM-SCRIPTLET] vboxguest.ko:
[2016-03-14 08:18] [ALPM-SCRIPTLET] Running module version sanity check.
[2016-03-14 08:18] [ALPM-SCRIPTLET]  - Original module
[2016-03-14 08:18] [ALPM-SCRIPTLET]    - No original module exists within this kernel
[2016-03-14 08:18] [ALPM-SCRIPTLET]  - Installation
[2016-03-14 08:18] [ALPM-SCRIPTLET]    - Installing to /usr/lib/modules/4.4.5-1-ARCH/kernel/misc/
[2016-03-14 08:18] [ALPM-SCRIPTLET] 
[2016-03-14 08:18] [ALPM-SCRIPTLET] vboxsf.ko:
[2016-03-14 08:18] [ALPM-SCRIPTLET] Running module version sanity check.
[2016-03-14 08:18] [ALPM-SCRIPTLET]  - Original module
[2016-03-14 08:18] [ALPM-SCRIPTLET]    - No original module exists within this kernel
[2016-03-14 08:18] [ALPM-SCRIPTLET]  - Installation
[2016-03-14 08:18] [ALPM-SCRIPTLET]    - Installing to /usr/lib/modules/4.4.5-1-ARCH/kernel/misc/
[2016-03-14 08:18] [ALPM-SCRIPTLET] 
[2016-03-14 08:18] [ALPM-SCRIPTLET] vboxvideo.ko:
[2016-03-14 08:18] [ALPM-SCRIPTLET] Running module version sanity check.
[2016-03-14 08:18] [ALPM-SCRIPTLET]  - Original module
[2016-03-14 08:18] [ALPM-SCRIPTLET]    - No original module exists within this kernel
[2016-03-14 08:18] [ALPM-SCRIPTLET]  - Installation
[2016-03-14 08:18] [ALPM-SCRIPTLET]    - Installing to /usr/lib/modules/4.4.5-1-ARCH/kernel/misc/
[2016-03-14 08:18] [ALPM-SCRIPTLET] 
[2016-03-14 08:18] [ALPM-SCRIPTLET] depmod...
[2016-03-14 08:18] [ALPM-SCRIPTLET] 
[2016-03-14 08:18] [ALPM-SCRIPTLET] DKMS: install completed.
[2016-03-14 08:18] [ALPM-SCRIPTLET] 
[2016-03-14 08:18] [ALPM-SCRIPTLET] Creating symlink /var/lib/dkms/vboxhost/5.0.16_OSE/source ->
[2016-03-14 08:18] [ALPM-SCRIPTLET]                  /usr/src/vboxhost-5.0.16_OSE
[2016-03-14 08:18] [ALPM-SCRIPTLET] 
[2016-03-14 08:18] [ALPM-SCRIPTLET] DKMS: add completed.
[2016-03-14 08:18] [ALPM-SCRIPTLET] 
[2016-03-14 08:18] [ALPM-SCRIPTLET] Kernel preparation unnecessary for this kernel.  Skipping...
[2016-03-14 08:18] [ALPM-SCRIPTLET] 
[2016-03-14 08:18] [ALPM-SCRIPTLET] Building module:
[2016-03-14 08:18] [ALPM-SCRIPTLET] cleaning build area...
[2016-03-14 08:19] [ALPM-SCRIPTLET] make KERNELRELEASE=4.4.5-1-ARCH -C /usr/lib/modules/4.4.5-1-ARCH/build M=/var/lib/dkms/vboxhost/5.0.16_OSE/build..............
[2016-03-14 08:19] [ALPM-SCRIPTLET] cleaning build area...
[2016-03-14 08:19] [ALPM-SCRIPTLET] Kernel cleanup unnecessary for this kernel.  Skipping...
[2016-03-14 08:19] [ALPM-SCRIPTLET] 
[2016-03-14 08:19] [ALPM-SCRIPTLET] DKMS: build completed.
[2016-03-14 08:19] [ALPM-SCRIPTLET] 
[2016-03-14 08:19] [ALPM-SCRIPTLET] vboxdrv.ko:
[2016-03-14 08:19] [ALPM-SCRIPTLET] Running module version sanity check.
[2016-03-14 08:19] [ALPM-SCRIPTLET]  - Original module
[2016-03-14 08:19] [ALPM-SCRIPTLET]    - No original module exists within this kernel
[2016-03-14 08:19] [ALPM-SCRIPTLET]  - Installation
[2016-03-14 08:19] [ALPM-SCRIPTLET]    - Installing to /usr/lib/modules/4.4.5-1-ARCH/kernel/misc/
[2016-03-14 08:19] [ALPM-SCRIPTLET] 
[2016-03-14 08:19] [ALPM-SCRIPTLET] vboxnetflt.ko:
[2016-03-14 08:19] [ALPM-SCRIPTLET] Running module version sanity check.
[2016-03-14 08:19] [ALPM-SCRIPTLET]  - Original module
[2016-03-14 08:19] [ALPM-SCRIPTLET]    - No original module exists within this kernel
[2016-03-14 08:19] [ALPM-SCRIPTLET]  - Installation
[2016-03-14 08:19] [ALPM-SCRIPTLET]    - Installing to /usr/lib/modules/4.4.5-1-ARCH/kernel/misc/
[2016-03-14 08:19] [ALPM-SCRIPTLET] 
[2016-03-14 08:19] [ALPM-SCRIPTLET] vboxnetadp.ko:
[2016-03-14 08:19] [ALPM-SCRIPTLET] Running module version sanity check.
[2016-03-14 08:19] [ALPM-SCRIPTLET]  - Original module
[2016-03-14 08:19] [ALPM-SCRIPTLET]    - No original module exists within this kernel
[2016-03-14 08:19] [ALPM-SCRIPTLET]  - Installation
[2016-03-14 08:19] [ALPM-SCRIPTLET]    - Installing to /usr/lib/modules/4.4.5-1-ARCH/kernel/misc/
[2016-03-14 08:19] [ALPM-SCRIPTLET]
[2016-03-14 08:19] [ALPM-SCRIPTLET] vboxpci.ko:
[2016-03-14 08:19] [ALPM-SCRIPTLET] Running module version sanity check.
[2016-03-14 08:19] [ALPM-SCRIPTLET]  - Original module
[2016-03-14 08:19] [ALPM-SCRIPTLET]    - No original module exists within this kernel
[2016-03-14 08:19] [ALPM-SCRIPTLET]  - Installation
[2016-03-14 08:19] [ALPM-SCRIPTLET]    - Installing to /usr/lib/modules/4.4.5-1-ARCH/kernel/misc/
[2016-03-14 08:19] [ALPM-SCRIPTLET]
[2016-03-14 08:19] [ALPM-SCRIPTLET] depmod...
[2016-03-14 08:19] [ALPM-SCRIPTLET]
[2016-03-14 08:19] [ALPM-SCRIPTLET] DKMS: install completed.
[2016-03-15 01:14] [PACMAN] Running 'pacman --color auto -Sy'
[2016-03-15 01:14] [PACMAN] synchronizing package lists
[2016-03-15 01:14] [PACMAN] Running 'pacman --color auto -S -u'
[2016-03-15 01:14] [PACMAN] starting full system upgrade
[2016-03-15 01:14] [ALPM] transaction started
[2016-03-15 01:15] [ALPM] upgraded cmake (3.4.3-1 -> 3.5.0-1)
[2016-03-15 01:15] [ALPM] upgraded glib-perl (1.308-1 -> 1.321-1)
[2016-03-15 01:15] [ALPM] upgraded lib32-sqlite (3.11.0-1 -> 3.11.1-1)
[2016-03-15 01:15] [ALPM] upgraded pango-perl (1.226-2 -> 1.227-1)
[2016-03-15 01:15] [ALPM] upgraded talloc (2.1.5-1 -> 2.1.6-1)
[2016-03-15 01:15] [ALPM] transaction completed
[2016-03-15 02:50] [PACMAN] Running 'pacman -Sy'
[2016-03-15 02:50] [PACMAN] synchronizing package lists
[2016-03-15 02:51] [PACMAN] Running 'pacman -S --needed linux-api-headers linux-headers'
[2016-03-15 02:51] [PACMAN] Running 'pacman --color auto -S -u'
[2016-03-15 02:51] [PACMAN] starting full system upgrade
[2016-03-15 16:17] [PACMAN] Running 'pacman -R watchdog'
[2016-03-15 16:17] [ALPM] transaction started
[2016-03-15 16:17] [ALPM] removed watchdog (5.14-1)
[2016-03-15 16:17] [ALPM] transaction completed
[2016-03-15 16:19] [PACMAN] Running 'pacman -Sy'
[2016-03-15 16:19] [PACMAN] synchronizing package lists
[2016-03-15 16:20] [PACMAN] Running 'pacman -S --needed linux-api-headers linux-headers'
[2016-03-15 16:20] [PACMAN] Running 'pacman --color auto -S -u'
[2016-03-15 16:20] [PACMAN] starting full system upgrade
[2016-03-15 16:20] [ALPM] transaction started
[2016-03-15 16:20] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2016-03-15 16:20] [ALPM] upgraded pacman-mirrorlist (20160310-5 -> 20160314-1)
[2016-03-15 16:20] [ALPM] upgraded wget (1.16.3-2 -> 1.17.1-1)
[2016-03-15 16:20] [ALPM] transaction completed
[2016-03-16 02:43] [PACMAN] Running 'pacman --color auto -Sy'
[2016-03-16 02:43] [PACMAN] synchronizing package lists
[2016-03-16 02:44] [PACMAN] Running 'pacman --color auto -S -u'
[2016-03-16 02:44] [PACMAN] starting full system upgrade
[2016-03-16 02:49] [ALPM] transaction started
[2016-03-16 02:49] [ALPM] upgraded lib32-pcre (8.38-1 -> 8.38-2)
[2016-03-16 02:49] [ALPM] upgraded opera (35.0.2066.92-1 -> 36.0.2130.32-1)
[2016-03-16 02:49] [ALPM] upgraded valgrind (3.11.0-2 -> 3.11.0-3)
[2016-03-16 02:49] [ALPM] transaction completed
[2016-03-16 02:50] [PACMAN] Running 'pacman --color auto -S extra/avahi'
[2016-03-16 02:50] [ALPM] transaction started
[2016-03-16 02:50] [ALPM] reinstalled avahi (0.6.32-2)
[2016-03-16 02:50] [ALPM] transaction completed
[2016-03-16 03:03] [PACMAN] Running 'pacman -R virtualbox-guest-dkms'
[2016-03-16 03:04] [ALPM] running '70-dkms-remove.hook'...
[2016-03-16 03:04] [ALPM] transaction started
[2016-03-16 03:04] [ALPM] removed virtualbox-guest-dkms (5.0.16-3)
[2016-03-16 03:04] [ALPM] transaction completed

I don't see any affection during the installations.
Any other log that I should post ?

Last edited by TheSaint (2016-03-18 13:48:31)


do it good first, it will be faster than do it twice the saint wink

Offline

#2 2016-03-15 19:42:44

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [Solved] Avahi, misbehaviors

Why do you insist on running -Sy $package? It is just going to lead to breakage...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2016-03-15 20:14:20

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,861
Website

Re: [Solved] Avahi, misbehaviors

What happened to your avahi user/group? They only get created when the package is installed (so not reinstalled/upgraded). You can recreate them by rerunning the relevent commands: https://projects.archlinux.org/svntogit … ages/avahi

What makes you think you need a /run/avahi directory?


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#4 2016-03-17 16:55:13

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: [Solved] Avahi, misbehaviors

jasonwryan wrote:

Why do you insist on running -Sy $package? It is just going to lead to breakage...

A bit OT, but  I didn't see sign of this matters. As far as I'm aware of that issue.


do it good first, it will be faster than do it twice the saint wink

Offline

#5 2016-03-17 17:22:45

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: [Solved] Avahi, misbehaviors

WorMzy wrote:

I didn't know it. So I settled mine by doing it manually.

WorMzy wrote:

What makes you think you need a /run/avahi directory?

The problem starts by shadow.service that cannot authenticate avahi.deamon. Obviously if avahi is up, then the issue is none.
So if I reset the directory, starting avahi-deamon and starting shadow, all will go smooth. But the next reboot all gets messed, because /run/avahi  has been removed by the system.
I grepped all the /usr to find a word like /run/avahi, one is in /usr/lib/systemd/system/avahi-daemon.socket and the other is in /usr/bin/avahi-daemon itselg to mention the directory name.

$ journalctl -b -u shadow
-- Logs begin at mar 2016-03-15 20:37:20 MYT, end at ven 2016-03-18 01:17:28 MYT. --
mar 18 00:00:04 AsusG75 systemd[1]: Starting Verify integrity of password and group files...
mar 18 00:00:04 AsusG75 pwck[6327]: user 'avahi': directory '/var/run/avahi' does not exist
mar 18 00:00:04 AsusG75 pwck[6327]: pwck: no changes
mar 18 00:00:04 AsusG75 systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
mar 18 00:00:04 AsusG75 systemd[1]: Failed to start Verify integrity of password and group files.

Even setting  userID:groupID to avahi, some other procedure has the power to remove it.


do it good first, it will be faster than do it twice the saint wink

Offline

#6 2016-03-17 18:27:31

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,861
Website

Re: [Solved] Avahi, misbehaviors

/run is a tmpfs, so directories do not persist over reboots. I was asking about your /var/run/avahi directory because avahi doesn't use this path. It uses /var/run/avahi-daemon, which is automagically created when avahi-daemon is started. By the looks of things, you have manually created an avahi user with the wrong home directory, which is why you're getting the shadow.service failure.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#7 2016-03-18 13:55:19

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: [Solved] Avahi, misbehaviors

I got it now.
It seems that is starting in a proper manner, when I set

# systemctl enable avahi-daemon

One more point is that I don't need to have avahi, permanently running, I would use it when I need to print (say in a ratio of once in a month). But then some time shadow will fail. I cannot tell for certain. I'll keep checking.


do it good first, it will be faster than do it twice the saint wink

Offline

Board footer

Powered by FluxBB