Debian Bug report logs - #464834
dhcdbd: lots of message handlers not found messages in syslog

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Olivier Berger <olivier.berger@it-sudparis.eu>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: dhcdbd: lots of message handlers not found messages in syslog

Date: Sat, 09 Feb 2008 10:16:47 +0100

Package: dhcdbd
Version: 3.0-2
Severity: normal

There seem to be lots of errors related to unexistant message handlers :
# grep dhcdbd /var/log/syslog
Feb  9 09:38:32 hortense dhcdbd: Started up.
Feb  9 09:39:08 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason
Feb  9 09:40:12 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason
Feb  9 09:40:15 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason
Feb  9 09:41:06 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason
Feb  9 09:41:55 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason
Feb  9 09:41:58 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason
Feb  9 09:42:11 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason
Feb  9 09:42:14 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth2 for sub-path eth2.dbus.get.reason
Feb  9 09:42:39 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
Feb  9 09:42:46 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.host_name
Feb  9 09:42:46 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.domain_name
Feb  9 09:42:46 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_domain
Feb  9 09:42:46 hortense dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_servers

I think that this at least shows inconstency between scripts and code... and maybe is a source for things not working well with networkmanager...

Hope this helps,

Best regards,


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-3-vserver-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dhcdbd depends on:
ii  dbus                          1.1.2-1    simple interprocess messaging syst
ii  dhcp3-client                  3.1.0-2    DHCP client
ii  libc6                         2.7-6      GNU C Library: Shared libraries
ii  libdbus-1-3                   1.1.2-1    simple interprocess messaging syst
ii  lsb-base                      3.1-24     Linux Standard Base 3.1 init scrip

dhcdbd recommends no packages.

-- no debconf information

Message #14 received at 464834-done@bugs.debian.org (full text, mbox, reply):

From: Marco Rodrigues <gothicx@sapo.pt>

To: 464834-done@bugs.debian.org

Subject: dhcdbd has been removed from Debian, closing #464834

Date: Mon, 11 May 2009 19:18:24 +0100

Version: 3.0-5+rm

The dhcdbd package has been removed from Debian so we are closing
the bugs that were still opened against it.

For more information about this package's removal, read
http://bugs.debian.org/527849 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

Kind regards,
--
Marco Rodrigues

Send a report that this bug log contains spam.