System log fillling with dns related messages

Hi,
My system.log is filling up with lots of this error message below. ("spenser" is hostname).
Anyone seen this before? Know how to stop it?
Thanks in advance for any help.
Rowan.
Dec 2 10:26:34 spenser mDNSResponder[16]: DNS Message too short
Dec 2 10:27:04: --- last message repeated 4 times ---
Dec 2 10:27:04 spenser mDNSResponder[16]: DNS Message too short
Dec 2 10:27:34: --- last message repeated 4 times ---
Dec 2 10:27:34 spenser mDNSResponder[16]: DNS Message too short
Dec 2 10:28:04: --- last message repeated 4 times ---

Bonjour is itself a DNS (technically, a component of DNS Service Discovery that uses multicast DNS) though it is not user-configurable in the sense that, say, BIND is.
The error message Bonjour is receiving is "DNS message too short." While I understand this may have little to do with a queryable DNS like BIND (though Bonjour is in fact a queryable DNS in an entirely different sense), Bonjour has everything to do with DNS.
That said, I will be the first to admit that my ignorance on this topic is vast.

Similar Messages

  • System log full with udisks-daemon messages after systemd switch

    I'm just wondering if this behavior is normal. I'm not seeing any real issues so far but I've been using systemd only for a few hours.
    messages.log:
    Nov 10 17:53:20 larch dbus-daemon[394]: dbus[394]: [system] Activating via systemd: service name='org.freedesktop.UDisks' unit='udisks.service'
    Nov 10 17:53:20 larch dbus[394]: [system] Activating via systemd: service name='org.freedesktop.UDisks' unit='udisks.service'
    Nov 10 17:53:20 larch systemd[1]: Starting UDisks...
    Nov 10 17:53:20 larch udisks-daemon[560]: (process:560): GLib-WARNING **: goption.c:2175: ignoring no-arg, optional-arg or filename flags (16) on option of arg-type 1 in entry (null):helper-dir
    Nov 10 17:53:20 larch dbus-daemon[394]: dbus[394]: [system] Successfully activated service 'org.freedesktop.UDisks'
    Nov 10 17:53:20 larch dbus[394]: [system] Successfully activated service 'org.freedesktop.UDisks'
    Nov 10 17:53:20 larch systemd[1]: Started UDisks.
    Nov 10 17:53:20 larch udisks-daemon[560]: (udisks-daemon:560): udisks-daemon-WARNING **: No /proc/mdstat file: No such file or directory
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:00.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:00.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:01.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:01.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:16.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:16.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1a.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1a.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0
    Nov 10 17:53:20 larch kernel: [ 10.530610] EXT4-fs (sda3): re-mounted. Opts: discard,commit=0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:01.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:01.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:04.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:04.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:04.0/0000:06:00.0
    Nov 10 17:53:20 larch kernel: [ 10.532812] EXT4-fs (sda1): re-mounted. Opts: discard,commit=0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:04.0/0000:06:00.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:04.0/0000:06:00.0/0000:07:01.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:04.0/0000:06:00.0/0000:07:01.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:05.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:05.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:06.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:06.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:07.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:07.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:08.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:08.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:08.0/0000:0b:00.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:08.0/0000:0b:00.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:09.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1c.7/0000:03:00.0/0000:04:09.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1d.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1d.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1f.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1f.0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1f.2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1f.2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci ADDING /sys/devices/pci0000:00/0000:00:1f.3
    Nov 10 17:53:20 larch udisks-daemon[560]: **** pci IGNORING ADD /sys/devices/pci0000:00/0000:00:1f.3
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/scsi_host/host0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/scsi_host/host0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/scsi_host/host1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/scsi_host/host1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/scsi_host/host2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/scsi_host/host2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/scsi_host/host3
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/scsi_host/host3
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/scsi_host/host4
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/scsi_host/host4
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata6/host5/scsi_host/host5
    Nov 10 17:53:20 larch udisks-daemon[560]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:1f.2/ata6/host5/scsi_host/host5
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
    Nov 10 17:53:20 larch udisks-daemon[560]: helper(pid 577): launched job udisks-helper-ata-smart-collect on /dev/sda
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda5
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda5
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda5
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb
    Nov 10 17:53:20 larch udisks-daemon[560]: helper(pid 580): launched job udisks-helper-ata-smart-collect on /dev/sdb
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb/sdb1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb/sdb1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb/sdb1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
    Nov 10 17:53:20 larch udisks-daemon[560]: helper(pid 582): launched job udisks-helper-ata-smart-collect on /dev/sdc
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDING /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** ADDED /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda5
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda5
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda5
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGING /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb/sdb1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** UPDATING /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb/sdb1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** CHANGED /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb/sdb1
    Nov 10 17:53:20 larch udisks-daemon[560]: **** /proc/self/mountinfo changed
    Nov 10 17:53:20 larch udisks-daemon[560]: helper(pid 580): completed with exit code 0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb
    Nov 10 17:53:20 larch udisks-daemon[560]: helper(pid 577): completed with exit code 0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
    Nov 10 17:53:20 larch udisks-daemon[560]: **** /proc/self/mountinfo changed
    Nov 10 17:53:20 larch kernel: [ 10.750406] EXT4-fs (sda5): re-mounted. Opts: discard,commit=0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** /proc/self/mountinfo changed
    Nov 10 17:53:20 larch udisks-daemon[560]: **** /proc/self/mountinfo changed
    Nov 10 17:53:20 larch kernel: [ 10.759450] EXT4-fs (sda6): re-mounted. Opts: discard,commit=0
    Nov 10 17:53:20 larch kernel: [ 10.760413] EXT4-fs (sdb1): re-mounted. Opts: commit=0
    Nov 10 17:53:20 larch kernel: [ 10.761270] EXT4-fs (sdc1): re-mounted. Opts: commit=0
    Nov 10 17:53:20 larch udisks-daemon[560]: **** /proc/self/mountinfo changed
    Nov 10 17:53:21 larch udisks-daemon[560]: helper(pid 582): completed with exit code 0
    Nov 10 17:53:21 larch udisks-daemon[560]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
    Nov 10 18:08:09 larch systemd[1]: Starting Cleanup of Temporary Directories...
    Nov 10 18:08:09 larch systemd[1]: Started Cleanup of Temporary Directories.
    Nov 10 18:23:20 larch udisks-daemon[560]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
    Nov 10 18:23:20 larch udisks-daemon[560]: helper(pid 1202): launched job udisks-helper-ata-smart-collect on /dev/sda
    Nov 10 18:23:20 larch udisks-daemon[560]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
    Nov 10 18:23:20 larch udisks-daemon[560]: helper(pid 1203): launched job udisks-helper-ata-smart-collect on /dev/sdc
    Nov 10 18:23:20 larch udisks-daemon[560]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb
    Nov 10 18:23:20 larch udisks-daemon[560]: helper(pid 1204): launched job udisks-helper-ata-smart-collect on /dev/sdb
    Nov 10 18:23:20 larch udisks-daemon[560]: helper(pid 1202): completed with exit code 0
    Nov 10 18:23:20 larch udisks-daemon[560]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
    Nov 10 18:23:21 larch udisks-daemon[560]: helper(pid 1204): completed with exit code 0
    Nov 10 18:23:21 larch udisks-daemon[560]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb
    Nov 10 18:23:21 larch udisks-daemon[560]: helper(pid 1203): completed with exit code 0
    Nov 10 18:23:21 larch udisks-daemon[560]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc
    Thanks in advance.

    I am getting this too:
    Nov 11 10:34:01 desktop udisks-daemon[584]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
    Nov 11 11:04:01 desktop udisks-daemon[584]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/
    Nov 11 11:04:01 desktop udisks-daemon[584]: helper(pid 2004): launched job udisks-helper-ata-smart-collect on /dev/sda
    Nov 11 11:04:01 desktop udisks-daemon[584]: helper(pid 2004): completed with exit code 0
    Repeating every 30 minutes. I don't see why the smart data needs updating so often. What could be triggering it?

  • System.log filling with error messages

    After SL update my system.log if filling with error messages.
    Does any process delete the system.log periodically?
    What's causing this error? Getting thousands of them.
    9/30/09 12:08:13 PM [0x0-0x12012].com.nowsoftware.nowxagent[181] at now.swing.NProgressBar.fixAppleAnimationBug(null:-1)

    JHF45 wrote:
    After SL update my system.log if filling with error messages.
    Does any process delete the system.log periodically?
    Yes. There are three automatic jobs that run daily, weekly, and monthly doing this sort of thing. They run in the early hours of the morning if your Mac is awake, or shortly after it wakes up if it was sleeping. In Leopard, if it was powered-off, they won't run; I don't know if it's the same in Snow.

  • System.log errors with slapd and password service

    i'm CONSTANTLY getting the following in my system.log file.
    Sep 23 23:50:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:50:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:51:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:51:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:52:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:52:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:53:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:53:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:54:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:54:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:55:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:55:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:56:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:56:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:57:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:57:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:58:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:58:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:59:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 23 23:59:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 24 00:00:06 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 24 00:00:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 24 00:01:05 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 24 00:01:36 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 24 00:02:05 campus /usr/sbin/PasswordService: incorrect digest response
    Sep 24 00:02:23 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:23 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:23 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    Sep 24 00:02:26 campus slapd[23777]: could not load the replica file.
    and i'm having all kinds of authentication issues with this server to begin with...during the day it will just stop authenticating and I have to restart!

    Re: incorrect digest response
    I just saw that log entry being spewed out constantly for the first time. Looking in Password Server log, I found entries that roughly correlated - a user authentication failing with SASL error -13 (password incorrect). The user was on a system we had just reimaged for Tiger. The console log on that system showed entries from the LDAP plugin with constant attempts to authenticate using a cleartext password. The client system seemed to be OK, though, and was mounting its network home correctly. I could not find anything that would be legitimately trying to connect.
    Long story short, I deleted and recreated the LDAP server entries in Directory Access. Problem solved. Hope this helps.

  • System.log flooded with kernel[0]: On Board Mode Message

    The Kernel keeps sending this message, apparently at a rather brisk pace.  It's been going on for over a month apparently*.  It's ogooglebar, also.  Any thoughts on what it is?  I'm not observing anything wrong on the system, but it's annoying when I need to rummage through the logs for whatever reason.
    Mar 31 11:29:50 McMacMac kernel[0]: *** kernel exceeded 500 log message per second limit  -  remaining messages this second discarded ***
    Mar 31 11:29:51 McMacMac kernel[0]: On Board Mode
    Mar 31 11:29:51 --- last message repeated 498 times ---
    Mar 31 11:29:51 McMacMac kernel[0]: *** kernel exceeded 500 log message per second limit  -  remaining messages this second discarded ***
    Mar 31 11:29:52 McMacMac kernel[0]: On Board Mode
    Mar 31 11:30:13 --- last message repeated 1015 times ---
    Mar 31 11:30:13 McMacMac kernel[0]: *** kernel exceeded 500 log message per second limit  -  remaining messages this second discarded ***
    Mar 31 11:30:14 McMacMac kernel[0]: On Board Mode

    Triple-click anywhere in the line below to select it:
    kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}'
    Copy the selected text to the Clipboard (command-C).
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V).
    Post any lines of output that appear below what you entered — the text, please, not a screenshot.

  • Random freezes with INSERT-HANG-DETECTED in system log

    Hi,
    Since a few months I am experiencing random freezes on my early 2011 MacBook Pro 15". Sometimes they occur every few minutes and sometimes they can be away for hours. During the freeze the system is not responding and often a spinning beachball is shown. After the freeze the system resumes to work as normal.
    In the system log (/var/log/system.log) I noticed the following messages which seem to have a timestamp corresponding to the freeze:
    WebProcess[151]: INSERT-HANG-DETECTED: Tx time:28.505937, # of Inserts: 1, # of bytes written: 4875, Did shrink: NO
    Does anyone know what these messages mean?
    It doesn't seem to be related to the application that is in use during the freeze. Most of the time I only use Mail, Safari, Calendar, Terminal and Preview. My system (10.6.8) is fully up-to-date. The Activity Monitor does not show exceptional CPU or Memory usage.
    What could also be relevant is that the freezes started to appear a week after I replaced a defective Hitachi HDD with a Crucial M4 SDD.
    Does anyone have had the same issues with this SSD?
    Thanks in advance for any help.
    Maarten

    This is an update to the question above.
    I put in the original HDD and had the same issues. At one time it didn't even boot anymore. Then I sent in my MBP for repair. They first replaced the HDD with no success. Then they replaced the logic board and all issues dissapeared.
    Maarten

  • RADIUS messages in system.log, all day long

    My 10.6 server's system log is full of RADIUS messages, every few seconds, making me think that something isn't as it should be. We have an airport extreme base station as our router and RADIUS access point. I configured the airport base station from the server, thru server manager.
    Feb 3 17:50:32 192.168.2.1 ffasnyc 80211: Authenticating station 00:19:e3:00:f7:89 to RADIUS.
    Feb 3 17:51:54 192.168.2.1 ffasnyc 80211: Deauthenticating with station 00:19:e3:00:f7:89 (reserved 2).
    Feb 3 17:51:54 192.168.2.1 ffasnyc 80211: Disassociated with station 00:19:e3:00:f7:89
    Feb 3 17:51:54 192.168.2.1 ffasnyc 80211: Associated with station 00:19:e3:00:f7:89
    Feb 3 17:51:54 192.168.2.1 ffasnyc 80211: Authenticating station 00:19:e3:00:f7:89 to RADIUS.
    Feb 3 17:53:16 192.168.2.1 ffasnyc 80211: Deauthenticating with station 00:19:e3:00:f7:89 (reserved 2).
    Feb 3 17:53:16 192.168.2.1 ffasnyc 80211: Disassociated with station 00:19:e3:00:f7:89
    Feb 3 17:53:16 192.168.2.1 ffasnyc 80211: Associated with station 00:19:e3:00:f7:89
    Feb 3 17:53:16 192.168.2.1 ffasnyc 80211: Authenticating station 00:19:e3:00:f7:89 to RADIUS.
    Feb 3 17:54:38 192.168.2.1 ffasnyc 80211: Deauthenticating with station 00:19:e3:00:f7:89 (reserved 2).
    Feb 3 17:54:38 192.168.2.1 ffasnyc 80211: Disassociated with station 00:19:e3:00:f7:89
    Feb 3 17:54:38 192.168.2.1 ffasnyc 80211: Associated with station 00:19:e3:00:f7:89
    Feb 3 17:54:38 192.168.2.1 ffasnyc 80211: Authenticating station 00:19:e3:00:f7:89 to RADIUS.
    Feb 3 17:56:00 192.168.2.1 ffasnyc 80211: Deauthenticating with station 00:19:e3:00:f7:89 (reserved 2).
    Feb 3 17:56:00 192.168.2.1 ffasnyc 80211: Disassociated with station 00:19:e3:00:f7:89
    Feb 3 17:56:21 192.168.2.1 ffasnyc 80211: Associated with station 00:19:e3:00:f7:89
    Feb 3 17:56:21 192.168.2.1 ffasnyc 80211: Authenticating station 00:19:e3:00:f7:89 to RADIUS.
    Feb 3 17:57:43 192.168.2.1 ffasnyc 80211: Deauthenticating with station 00:19:e3:00:f7:89 (reserved 2).
    Feb 3 17:57:43 192.168.2.1 ffasnyc 80211: Disassociated with station 00:19:e3:00:f7:89
    Feb 3 17:57:43 192.168.2.1 ffasnyc 80211: Associated with station 00:19:e3:00:f7:89
    Feb 3 17:57:43 192.168.2.1 ffasnyc 80211: Authenticating station 00:19:e3:00:f7:89 to RADIUS.
    Feb 3 17:58:53 192.168.2.1 ffasnyc 80211: Associated with station 00:19:e3:00:f7:89
    Feb 3 17:59:04 192.168.2.1 ffasnyc 80211: Deauthenticating with station 00:19:e3:00:f7:89 (reserved 2).
    Feb 3 17:59:04 192.168.2.1 ffasnyc 80211: Disassociated with station 00:19:e3:00:f7:89
    Feb 3 17:59:04 192.168.2.1 ffasnyc 80211: Associated with station 00:19:e3:00:f7:89
    Feb 3 17:59:04 192.168.2.1 ffasnyc 80211: Authenticating station 00:19:e3:00:f7:89 to RADIUS.
    Feb 3 17:59:07 192.168.2.1 ffasnyc 80211: Disassociated with station 00:19:e3:00:f7:89
    Fe

    Also NOW I suddenly have two 256 cards that are not showing up so I have lost half of my RAM! I have less than 12% space left on my hard drive. Two of the cards look the same and two others look alike ( I have four 256 cards) Two years ago the repair shop put in two used cards so I would have all the same. I tried re seating them but it didn't work and I still get repeating messages in my systems log.

  • HELP!!!!!!  CRASHES and understand SYSTEM.LOG messages

    My G5 have problems (hangs, freeze an kernel panics) with Panther and now with Tiger the same problems after install and erase HD, and I supose that MY PROBLEM IS HARDWARE, NOT SOFT. I disconect the second HD and unplug the RAM and test and work on my G5.
    In System.log I can see this messages after a few time (2 - 5 hours of several works in Photoshop):
    Dec 5 15:48:30 pabloG5-HD ntpd[184]: time set -1.043889 s
    Dec 5 18:54:34 pabloG5-HD kernel[0]: USBF: 27598.319 AppleUSBOHCI[0x1f37000]::Found a transaction which hasn't moved in 5 seconds on bus 43, timing out!
    WHAT IS THIS???, IS THIS THE CAUSE OF MY PROBLEMS????
    Thanks in advance and Sorry for my bad english!
    ; P
    G5 1.8 DP • 4,5 Gb RAM • 160x2 SATA HD   Mac OS X (10.4.3)  

    Thanks Bmer!!! for your fast reply
    The only USB are (mouse and keyboard), and UPS SAI ellipse MGE, and a Wacom tablet intiuos3 plug in the USB monitor port Apple cinema 20''.
    Its possible that I obtain the same message if USB ports monitor Apple Cinema are empty and this ports are damaged?
    Thanks in advance

  • Repeating messages in System log: com.apple.wikid.mailinglists[######]: mail:status = "list-updated"

    Hello
    I have an OSX 10.6.8 server and recently noticed the System log keeps repating the same message after 10 mins:
    com.apple.wikid.mailinglists[#####]: mail:status = "list-updated"
    [#####] = number that changes every event
    The server is bound to Active Directory and the only active services are AFP and SMB
    Is there a location/way I can check to stop/fix these messages?
    Many thanks for your help
    Ciao
    Carlo

    This is part of the wiki server's setup. If you don't want the messages, turn off the wiki (or 'collaboration services' in the web server setup.
    Beyond that, there's no harm in the messages. Why do they concern you?

  • System Log - Stop Workproc

    Dear all,
    We are running SAP ECC 6.0 with Oracle 11g on AIX 5.1.
    The system log (SM21) have entries like 'Stop Workproc 5, PID 2760756'  every now and then for different users.
    The details of the entry are as follows :
    Task...... Process         User...... Terminal Session TCode        Program                        Cl Problem cl      Package
    27607      Dialog work process No. 005 TESTUSER    terminal06       1 START_REPORT GP47VTF200KGK52BL7PWMWOGWT1100 S  Operation Trace STSK
    Module nam Line Error text         Caller.... Reason/cal
    dpuxtool   269# Workproc 5 2760756 wp_halt    WPStop
    Documentation for system log message Q0 2 :
    The specified process has been stopped
    File Offset RecFm System log type             Grp N variable message data
      12 913140 m     Error (Function,Module,Row) Q0  2 Workproc 5 2760756                    wp_haltWPStop dpuxtool269#
    The previous and succeeding log entries in SM21 are for different users.
    Are these issue due to any disconnection due to network inconsistency or so.
    The entry in SM50 trace display at this time is as follows:
    Tue Oct 18 10:17:42 2011
      User requested cancel of current SQL on connection 0
      db_sqlbreak() = 0
      program canceled
        reason   = soft cancel
        user     = TESTUSER
        client   = 100
        terminal = terminal06
        report   = GP47VTF2FDMDRK3KO41KRL8KU8L710
    Thanks in Advance !
    Regards,
    Kiran

    I would say that someone executes a transaction, it takes too long and he cancells the transaction through GUI.
    I would trry to find out, who's user "TESTUSER" and ask what is going on.
    Markus

  • System log info

    Hi,
    In which table system log entries stored?
    like abap dumps =SNAP
    Is there any way to restrict the system log messages to some number for example to 200?
    I am running housekeeping job RSSNAPDEL for a period of two weeks reguraly I want to read the dump of 3 days before.Is it possible?
    Thanks,
    Sagar.

    Hi Raghu,
    T-cde RZ11
    The System Log
    The SAP System logs all system errors, warnings, user locks due to failed logon attempts from known users, and process messages in the system log. There are to two different types of logs created by the system log:
    ｷ Local Logs
    ｷ Central Logs
    Use transaction SM21 to access the system log output screen. With this transaction, you can read any of the messages that are contained in the system logs. You can modify the view to meet your needs.
    Local Logs
    Each SAP System application server has a local log that receives all the messages output by this server. The system log records these messages in a circular file on the server. When this log file reaches the maximum permissible length, the system log overwrites it, starting over from the beginning. (The location of the local log is specified in the rslg/local/file profile parameter.)
    Central Logs
    We recommend that you also maintain a central log file on a selected application server. Each individual application server then sends its local log messages to this server. The server that you designate to maintain the central log collects the messages from the other application servers and writes these messages to the central log.
    The central log consists of two files: the active file and the old file. (The location of the active file is specified in the rslg/central/fileprofile parameter; the location of the old file is specified in the rslg/central/old_file.)
    The active file contains the current log. When it reaches the maximum size, the system performs a "log file switch". It deletes the old log file, makes the previously active file the “old” file, and creates a new active file. The switch occurs when the size of the active log file is half the value as specified in the rslg/max_diskspace/central parameter. (Note: the SAP System does not support the saving of old system log files. If you want to save old logs, then you must archive them yourself.)
    If you use Windows NT or AS/400, then note the following:
    Central logging is not available on the Windows NT and AS/400 platforms.
    Per default, the profile parameter rslg/collect_daemon/host should be set correctly. However, if you receive warnings, then make sure that this parameter is set to NONE.
    For these platforms, you can use the All remote syslogs function from transaction SM21 to read the data of all the instances in your SAP System. In the alert monitor, if you receive an alert, you can use the Remote syslog function to analyze the affected instance.
    Profile Parameters and File Locations
    The table below shows some of the profile parameters for the system log along with their standard values:
    Profile Parameters and File Locations for the System Log
    rslg/local/file
    Specifies the location of the local log on the application server.
    /usr/sap/<SID>/D20/
    log/SLOG<SAP-instance_number>
    rslg/collect_daemon/host
    Specifies the application server that maintains the central log.
    <hostname of main instance>
    rslg/central/file
    Specifies the location of the active file for the central log on the application server.
    /usr/sap/<SID>/SYS/
    global/SLOGJ
    rslg/central/old_file
    Specifies the location of the old file for the central log on the application server.
    /usr/sap/<SID>/SYS/
    global/SLOGJO
    rslg/max_diskspace_local
    Specifies the maximum length of the local log.
    500,000 bytes
    rslg/max_diskspace_central
    Specifies the maximum length of the central log.
    2,000,000 bytes
    Any operations on the Database would be recorded in the attribute log of the db and it would be a file on the system - usually the attribute logs are set to a particular size and if that size limit is eached , the system will hang - ask the DBA to take a back up of the log and clear the current log file and you should be good to go.
    Hope this helps,
    Regards
    CSM Reddy

  • Job to clean up system logs

    How do we make a job that will clean up all the system logs except the current day.
    so that when we log transaction sm21 the logs of current day will be displayed.

    Dear Subhram Singh,
    Post basis related queries in basis forums. This forum is for business process expert related queries.
    Have you looked at all the profile parameters available for system logs in transaction RZ11 / RZ10. Profile paramters related to system log begins with "rslg".
    Other profile parameters:
    rslg/max_diskspace_local - maximum length of the local log
    rslg/max_diskspace_central - maximum length of the central log
    Regards,
    Naveen

  • Understanding system.log

    This keeps logging every few minutes. Any idea what an invalid colorscape type can be?
    Mar 12 17:27:41 Computer /System/Library/Frameworks/ScreenSaver.framework/Resources/ScreenSaverEngine.ap p/Contents/MacOS/ScreenSaverEngine: CMSCreateDataProviderOrGetInfo : Invalid colorspace type

    hi i'm having a similar problem. my stems from the game world of warcraft. in game, the symptoms manifest as such:
    1) choppy audio for a couple seconds
    2) game freezes for a couple seconds
    3) game resumes but drops from 30 frames per second to 5 frames per second (sometimes this is accompanied by a loss of internet connectivity which cannot be re-established until restarting the macbook pro)
    4) Normal FPS is established after 5-8 minutes
    5) Cycle repeats at 5-8 minute intervals
    The system.log associated with this is as follows:
    Description: System events log
    Size: 8.58 KB
    Last Modified: 4/19/09 7:34 PM
    Location: /var/log/system.log
    Recent Contents: ...
    Apr 19 12:57:47 administrators-computer /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/Current/Apple MobileDeviceHelper.app/Contents/Resources/MDCrashReportTool: 4825:2684407808|CrashReportCopierAFC.m:-[CrashReportCopierAFC connectToCrashReportCopyTarget]| ERROR: AMDeviceStartService for root
    Apr 19 14:56:36 administrators-computer /usr/sbin/ocspd: starting
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:40:39 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 16:45:35 administrators-computer kernel[0]: IOAudioStream[0x52de400]::clipIfNecessary() - Error: attempting to clip to a position more than one buffer ahead of last clip position (341,281e)->(342,37f0).
    Apr 19 16:45:35 administrators-computer kernel[0]: IOAudioStream[0x52de400]::clipIfNecessary() - adjusting clipped position to (342,281e)
    Apr 19 17:16:55 administrators-computer /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/Current/Apple MobileDeviceHelper.app/Contents/Resources/MDCrashReportTool: 5057:2684407808|CrashReportCopierAFC.m:-[CrashReportCopierAFC connectToCrashReportCopyTarget]| ERROR: AMDeviceStartService for root
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type
    Apr 19 19:34:20 administrators-computer /Applications/World of Warcraft/World of Warcraft Launcher.app/Contents/MacOS/Launcher: CMSCreateDataProviderOrGetInfo : Invalid colorspace type

  • System.log filling up with enqueueData rtn message

    I'm seeing the following log entry in system.log 7-9 times a second:
    Oct 22 11:00:00 pbair-paulywalnutz-com kernel[0]: ttyioss9000003: enqueueData rtn (e00002d8)
    I've tried googling and checked discussions here but can't find anything that seems to be related.
    I don't think it's affecting my PB all that much but it is definitely not right and I would like to fix it.
    Please let me know any information I might post that would help diagnose, etc...
    Thanks,
    Paul

    I contacted technical support for Software-Systeme (what the company is not called Bresink as I posted earlier).
    They replied promptly with what seems to be the answer…
    Hardware Monitor Support wrote:
    The error message indicates that you have configured Hardware Monitor
    to send its current readings to an external LCD display box. However,
    this box appears to have a technical problem or you have no such device
    connected. To switch this off, open "Preferences > LCD Module", select
    the USB device and set "Configure for display type" to "No display".
    This works for me and stops the logs filling with the messages. I'm not sure when I set the LCD display settings, but I imagine it was when I was learning what the settings do.
    Just select the items in the top 'lcd module settings' table and set them to no display.
    Drew

  • System log query is flooded with the message.. WindowServer[]: WSSetTrackingAreaEnabled : Invalid tracking area

    Hello apple community (: quick question
    my system log query is flooded with the message..
    "8/29/14 12:10:12.258 PM WindowServer[176]: WSSetTrackingAreaEnabled : Invalid tracking area 0x61000089f220"
    it has shown me after i run Mavericks Cache Cleaner to clean my computer. in my Activity Log, WindowServer[176] is taking up anywhere from 5 - 20 cpu at a time. (maybe more haven't watched it for too long)
    what do i do fix this? i recently updated to OS X and i haven't payed attention to the errors until now (i'm an idiot i know..) so i don't exactly know when it all started happening. sorry all just hoping someone will have an idea.
    -Ali

    What functional problem do you have, if any? Log messages are not a problem in themselves.

Maybe you are looking for