pfSense » pfSense Packages

I usage this to solve temporary the problem.

In shell console:

# mkdir -p /var/run/dbus/
# pw user add messagebus
# chown messagebus:messagebus /var/run/dbus
# dbus-daemon --system

After this I enable service in PFsense GUI

And the process start :)

Jul 5 12:41:06 pfdev check_reload_status: Syncing firewall
Jul 5 12:41:06 pfdev avahi-daemon[6826]: Found user 'avahi' (UID 558) and group 'avahi' (GID 558).
Jul 5 12:41:06 pfdev avahi-daemon[6826]: Successfully dropped root privileges.
Jul 5 12:41:06 pfdev avahi-daemon[6826]: avahi-daemon 0.6.29 starting up.
Jul 5 12:41:06 pfdev avahi-daemon[6826]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jul 5 12:41:06 pfdev avahi-daemon[6826]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jul 5 12:41:06 pfdev avahi-daemon[6826]: Loading service file /usr/pbi/avahi-amd64/etc/avahi/services/sftp-ssh.service.
Jul 5 12:41:06 pfdev avahi-daemon[6826]: Loading service file /usr/pbi/avahi-amd64/etc/avahi/services/ssh.service.
Jul 5 12:41:06 pfdev avahi-daemon[6826]: Joining mDNS multicast group on interface em0.IPv4 with address 192.168.100.1.
Jul 5 12:41:06 pfdev avahi-daemon[6826]: New relevant interface em0.IPv4 for mDNS.
Jul 5 12:41:06 pfdev avahi-daemon[6826]: Network interface enumeration completed.
Jul 5 12:41:06 pfdev avahi-daemon[6826]: Registering new address record for fe80::20c:29ff:fe83:621a on em0.*.
Jul 5 12:41:06 pfdev avahi-daemon[6826]: Registering new address record for 192.168.100.1. on em0.IPv4.
Jul 5 12:41:06 pfdev avahi-daemon[6826]: Registering HINFO record with values 'AMD64'/'FREEBSD'.
Jul 5 12:41:07 pfdev avahi-daemon[6826]: Server startup complete. Host name is pfdev.local. Local service cookie is 2798121152.
Jul 5 12:41:08 pfdev avahi-daemon[6826]: Service "pfdev" (/usr/pbi/avahi-amd64/etc/avahi/services/ssh.service) successfully established.
Jul 5 12:41:08 pfdev avahi-daemon[6826]: Service "pfdev" (/usr/pbi/avahi-amd64/etc/avahi/services/sftp-ssh.service) successfully established.


Maybe the problem is in dbus startup process

Real fix is pending - just needs pushed - should be up shortly.

Avahi process now start, but dbus service no.

Jul 5 14:27:35 pfdev check_reload_status: Syncing firewall
Jul 5 14:27:46 pfdev check_reload_status: Syncing firewall
Jul 5 14:27:47 pfdev root: /usr/pbi/avahi-amd64/etc/rc.d/dbus: WARNING: failed to start dbus
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: Found user 'avahi' (UID 558) and group 'avahi' (GID 558).
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: Successfully dropped root privileges.
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: avahi-daemon 0.6.29 starting up.
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: Loading service file /usr/pbi/avahi-amd64/etc/avahi/services/sftp-ssh.service.
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: Loading service file /usr/pbi/avahi-amd64/etc/avahi/services/ssh.service.
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: Network interface enumeration completed.
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: Registering HINFO record with values 'AMD64'/'FREEBSD'.
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: Server startup complete. Host name is pfdev.tecnomega.local. Local service cookie is 1792877340.
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: Service "pfdev" (/usr/pbi/avahi-amd64/etc/avahi/services/ssh.service) successfully established.
Jul 5 14:27:52 pfdev avahi-daemon³²⁹¹²: Service "pfdev" (/usr/pbi/avahi-amd64/etc/avahi/services/sftp-ssh.service) successfully established.

Try to run /usr/pbi/avahi-amd64/etc/rc.d/dbus onestart

See what happens there - I wiped away all traces of avahi and dbus from my vm and reinstalled and it worked fine for me.

/usr/pbi/avahi-amd64/etc/rc.d/dbus onestart

Starting dbus.
Failed to start message bus: Could not get UID and GID for username "messagebus" 
/usr/pbi/avahi-amd64/etc/rc.d/dbus: WARNING: failed to start dbus

Are you on a current snap and getting the PBI from our repo? I delete the messagebus and avahi users and then re-add the package and they come back as expected and it starts up without any special intervention.

Carlos Cesario wrote:

I usage this to solve temporary the problem.

In shell console:

[...]

This also works on this end, but the folder is deleted upon reboot of the machine. Other than that, it seems to be working as expected.

I try again, removing the avahi and messagebus users.
And install again the avahi package

Downloading http://files.pfsense.org/packages/amd64/8/All/avahi-0.6.29-amd64.pbi ...

After complete, onlye the user avahi is created.

avahi:*:558:558:User &:/home/avahi:/bin/sh

My system is not in last snap.

Update to the latest snap and try again, it is working from a bare install on a new snap here. I really don't want to have to manually add the messagebus user during the install process if I can avoid it.

Jim,

I install new VM with last snap

FreeBSD pfSense.localdomain 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #0: Thu Jul 5 03:23:23 EDT 2012 root@FreeBSD_8.3_pfSense_2.1.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64

And the avahi package works as expected.
The users avahi and messagebus are created.

But I have a bit detail. In remove process the users avahi and messagebus are not removed. Is it normal!?

Yes that's normal. Probably a side effect of how the PBI system adds the PBI users, that's a fairly new feature of the PBI tools from PC-BSD. Not really hurting anything as the users really have no privileges and no usable password or other capabilities.

Ok.

So I believe this may be considered as solved :)

Thank you ;)

Hello again, I just tried the most recent snapshot (ref: 2.1-BETA0 (amd64) built on Sat Jul 7 19:53:29 EDT 2012).

The directory /var/run/dbus isn't created upon reboot/re installation of the package. Nor is the DBUS service started. As a result, the avahi service fails to start.

I just installed it on a VM using that same snapshot. The VM did not have (nor ever had) Avahi installed, so it had no /var/run/dbus. After installing, I went to Avahi's settings, enabled, entered a domain, pressed Save, and it created /var/run/dbus and started up fine.

Do you get an error if you go to the shell and run:
/usr/local/etc/rc.d/avahi-daemon.sh restart