Hi all,
I'm having a hard time making the new cups server broadcast method work. The avahi-daemon on my print server is not cooperating. It appears to be running, but nothing can access it. Why?
Any help most appreciated! Debugging output below...
- Mike
[root@ulmo ~]# avahi-browse -a Failed to create client object: Daemon not running
but ...
[root@ulmo ~]# systemctl status avahi-daemon.service avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled) Active: active (running) since Thu 2013-07-18 18:24:11 EDT; 17h ago Main PID: 474 (avahi-daemon) Status: "Server startup complete. Host name is ulmo.local. Local service cookie is 1758851528." CGroup: name=systemd:/system/avahi-daemon.service ├─474 avahi-daemon: running [ulmo.local] └─478 avahi-daemon: chroot helper
Jul 18 22:37:20 ulmo avahi-daemon[474]: Received response from host 192.168.0.43 with ....0' Jul 18 23:37:20 ulmo avahi-daemon[474]: Received response from host 192.168.0.43 with ....0' Jul 19 00:37:20 ulmo avahi-daemon[474]: Received response from host 192.168.0.43 with ....0' Jul 19 01:37:20 ulmo avahi-daemon[474]: Received response from host 192.168.0.43 with ....0' Jul 19 02:37:20 ulmo avahi-daemon[474]: Received response from host 192.168.0.43 with ....0' Jul 19 03:37:20 ulmo avahi-daemon[474]: Received response from host 192.168.0.43 with ....0' Jul 19 04:37:20 ulmo avahi-daemon[474]: Received response from host 192.168.0.43 with ....0' Jul 19 05:37:20 ulmo avahi-daemon[474]: Received response from host 192.168.0.43 with ....0' Jul 19 06:37:20 ulmo avahi-daemon[474]: Received response from host 192.168.0.43 with ....0' Jul 19 07:37:20 ulmo avahi-daemon[474]: Received response from host 192.168.0.43 with ....0' Jul 19 08:29:32 ulmo avahi-daemon[474]: Files changed, reloading. Jul 19 08:29:32 ulmo avahi-daemon[474]: Files changed, reloading. Jul 19 08:29:32 ulmo avahi-daemon[474]: Files changed, reloading. Jul 19 08:29:32 ulmo avahi-daemon[474]: Files changed, reloading. Jul 19 08:29:32 ulmo avahi-daemon[474]: Service group file /services/udisks.service ch...ng. Jul 19 08:29:32 ulmo avahi-daemon[474]: Service "ulmo" (/services/udisks.service) succ...ed. Jul 19 08:29:33 ulmo avahi-daemon[474]: Withdrawing address record for 192.168.0.2 on em1. Jul 19 08:29:33 ulmo avahi-daemon[474]: Leaving mDNS multicast group on interface em1.....2. Jul 19 08:29:33 ulmo avahi-daemon[474]: Interface em1.IPv4 no longer relevant for mDNS. Jul 19 08:29:33 ulmo avahi-daemon[474]: Joining mDNS multicast group on interface em1.....2. Jul 19 08:29:33 ulmo avahi-daemon[474]: New relevant interface em1.IPv4 for mDNS. Jul 19 08:29:33 ulmo avahi-daemon[474]: Registering new address record for 192.168.0.2...v4.
selinux and iptables are OK:
[root@ulmo ~]# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: permissive Policy MLS status: enabled Policy deny_unknown status: allowed Max kernel policy version: 28
[root@ulmo ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination
Chain FORWARD (policy ACCEPT) target prot opt source destination
Chain OUTPUT (policy ACCEPT) target prot opt source destination
On 7/19/2013 8:42 AM, Dr. Michael J. Chudobiak wrote:
I'm having a hard time making the new cups server broadcast method work. The avahi-daemon on my print server is not cooperating. It appears to be running, but nothing can access it. Why?
Any help most appreciated!
Two likely causes come to mind. the messagebus service is not running , try:"service messagebus start" or /var/ ran out of space.
On 07/19/2013 12:30 PM, Edward Martinez wrote:
On 7/19/2013 8:42 AM, Dr. Michael J. Chudobiak wrote:
I'm having a hard time making the new cups server broadcast method work. The avahi-daemon on my print server is not cooperating. It appears to be running, but nothing can access it. Why?
Any help most appreciated!
Two likely causes come to mind. the messagebus service is not running , try:"service
messagebus start" or /var/ ran out of space.
Hmm, both look OK:
[root@ulmo ~]# df -h /var Filesystem Size Used Avail Use% Mounted on /dev/mapper/luks-26996aa1-560a-4bdd-bf40-64ccd220d687 69G 14G 52G 21% /
[root@ulmo ~]# service messagebus status Redirecting to /bin/systemctl status messagebus.service dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; static) Active: active (running) since Thu 2013-07-18 18:24:11 EDT; 18h ago Main PID: 477 (dbus-daemon) CGroup: name=systemd:/system/dbus.service ├─477 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation └─529 /usr/sbin/modem-manager
Jul 19 12:41:26 ulmo setroubleshoot[2600]: load_plugins() plugins.qemu_file_image previously imported Jul 19 12:41:26 ulmo setroubleshoot[2600]: load_plugins() plugins.chrome previously imported Jul 19 12:41:26 ulmo setroubleshoot[2600]: load_plugins() plugins.disable_ipv6 previously imported Jul 19 12:41:26 ulmo setroubleshoot[2600]: load_plugins() plugins.allow_ftpd_use_nfs previously imported Jul 19 12:41:26 ulmo python[2600]: [120B blob data] Jul 19 12:41:36 ulmo setroubleshoot[2600]: received signal=14 Jul 19 12:41:36 ulmo setroubleshoot[2600]: KeyboardInterrupt in RunFaultServer Jul 19 12:41:36 ulmo setroubleshoot[2600]: writing database (/var/lib/setroubleshoot/setroubleshoot_databa...nt=2 Jul 19 12:41:36 ulmo dbus-daemon[477]: Dan Jul 19 12:41:36 ulmo dbus-daemon[477]: Dan
On 07/19/2013 11:42 AM, Dr. Michael J. Chudobiak wrote:
Hi all,
I'm having a hard time making the new cups server broadcast method work. The avahi-daemon on my print server is not cooperating. It appears to be running, but nothing can access it. Why?
Figured it out... avahi-daemon was pegged at 100% CPU. Probably this:
http://bugzilla.redhat.com/show_bug.cgi?id=952193
- Mike
On 19.07.2013 19:54, Dr. Michael J. Chudobiak wrote:
On 07/19/2013 11:42 AM, Dr. Michael J. Chudobiak wrote:
Hi all,
I'm having a hard time making the new cups server broadcast method work. The avahi-daemon on my print server is not cooperating. It appears to be running, but nothing can access it. Why?
Figured it out... avahi-daemon was pegged at 100% CPU. Probably this:
http://bugzilla.redhat.com/show_bug.cgi?id=952193
- Mike
That isn't happening here. Do you want to compare the configuration?
poma