System log message Missing: TSL1TE - Undocumented message CQ9
Hello experts,
Maybe a silly question but does anyone know what the following syslog messages (SM21), which appear at system startup, mean?
Missng:TSL1TE,CQ9):BAPIPAREX_HELP<óܪ##
Missng:TSL1TE,CQ9):BAPIPAREX_HELP
Missng:TSL1TE,CQ9):CUEXp#
Missng:TSL1TE,CQ9):CUEX<óܪ##
Missng:TSL1TE,CQ9):CUKNp#
Missng:TSL1TE,CQ9):CUKN<óܪ##
Missng:TSL1TE,CQ9):CURSCODp#
Missng:TSL1TE,CQ9):CURSCOD<óܪ##
Missng:TSL1TE,CQ9):EDID2p#
Missng:TSL1TE,CQ9):EDID2<óܪ##
Missng:TSL1TE,CQ9):EDID4p#
Missng:TSL1TE,CQ9):EDID4<óܪ##
Missng:TSL1TE,CQ9):EDIDD_OLD<óܪ##
Missng:TSL1TE,CQ9):EDIDD_OLDp#
Missng:TSL1TE,CQ9):T52C5à#
Missng:TSL1TE,CQ9):T52C5<óܪ##
Missng:TSL1TE,CQ9):TPRI_PAR
Missng:TSL1TE,CQ9):TPRI_PAR
Interestingly enough, in our system, T100 only contains messages CQ0 - CQ5.
Thanks!
Judith
Hi Judith,
The language-dependent table TSL1T contains system log messages. These
messages may occur if the syslog message does not exist in the logon
language.
There can be several reasons for missing text: (note 46062.)
- The language import did not run correctly.
- The text was not yet translated.
- A kernel is used whose release is younger than the R/3 System (downward-compatible kernel) and this kernel generates Syslog messages that are not yet in the corresponding R/3 release. Example: R/3 Release 4.6B with kernel 4.6D. If the Release 4.6D kernel generates a Syslog message which is not yet in Release 4.6B, no entry table TSL1T is found.
Some corruption may exist in the syslog, so you should delete it as per SAP Note 45580.
Please try to make sure you have applied the latest kernel patch to remove all the known bug.
Also see SAP Notes:
#46062 Entries with TSL1T in syslog
#45580 How are syslog files deleted?
#761220 SYSLOG: Message.....Missing: TSL1Tx
regards,
Vincent
Similar Messages
-
System Log file filled with arp message from teamed nics
Hello,
We are running a Win2k3 server with dual nics teamed to one IP address. All of our Mac's system logs are being filled with the following message:
Mar 28 12:48:58 Son-of-Spacedog kernel[0]: arp: 192.168.200.50 moved from 00:04:23:b9:00:4a to 00:04:23:b9:00:4b on en0
This is repeated over and over. Is there any way to get the Mac's to stop generating this message? Is the fix for this on the server side or on the Mac side? From what I have seen online in other forums, this started happening with Panther.There are actually several different types of NIC Teaming Modes:
Adapter Fault Tolerance (AFT) - provides automatic redundancy for a server's network connection. If the primary adapter fails, the secondary adapter takes over. Adapter Fault Tolerance supports two to eight adapters per team. This teaming mode works with any hub or switch, and all team members must be connected to the same device.
Switch Fault Tolerance (SFT) - provides a failover relationship between two adapters when each adapter is connected to a separate switch. Switch Fault Tolerance supports two adapters per team. This feature works with any switch. Spanning Tree Protocol (STP) must be enabled when you create a team in SFT mode.
Adaptive Load Balancing (ALB) - provides load balancing for transmission traffic and adapter fault tolerance. You can also enable or disable receive load balancing (RLB) in ALB teams. This teaming mode works with any switch.
Fast EtherChannel/Link Aggregation - provides increased transmission and reception throughput in a team of two to eight adapters. This mode also includes adapter fault tolerance and load balancing (only routed protocols). This requires a switch with Link Aggregation or FEC capability.
Gigabit EtherChannel/Link Aggregation - is the gigabit extension of the FEC/Link Aggregation/802.3ad: static mode. All team members must operate at gigabit speed.
IEEE 802.3ad: dynamic mode - creates one or more teams using dynamic Link Aggregation with same-speed or mixed-speed adapters. Like the static Link Aggregation modes, Dynamic 802.3ad teams increase transmission and reception throughput and provide fault tolerance. This mode requires a switch that fully supports the IEEE 802.3ad standard.
Now, most likely, somewhere on the network a server is configured for ALB or AFT, and these are the most common methods of NIC teaming (Sadly, the XServes do not). They also do not require any certain type of switch, but they do require STP (Spanning Tree Protocol) to be turned off to function most effectively, or you will see errors on the network like the ones you are seeing in your log. Most managed switches come with STP turned on by default, so you will need to check ALL switches (as the errors will cascade throughout the network) to see if it STP is turned on. Most people do not use STP any more (it basically allows ports on one switch to appear as on another switch), so see if you can turn it off. That should stop the error messages.
-MacBoy in SLC
PowerMac G5 Dual 2.0 GHz Mac OS X (10.4.6) -
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. -
SXMB_MONI SAP:System element is missing in Inbound Message
Hi Experts,
In one of my Proxy to File interface, I am using Dynamic file configuration at receiver channel. I have applied every setting which is required. And it is working perfectly fine in my Development environment. I have moved the same configuration in my Quality Environment.
But there, while executing this, I noticed one of step i.e. "System" along with "DynamicConfiguration" is missing in SXMB MONI. Any one having any idea, what could be the possible reason for it?
My current SXMB Moni don't have this step right from begining (screen 1 below). While in Devlopment SXMB_Moni (Screen 2 below) i can see "System" from begining and "DynamicConfiguration" under request message mapping step.
Any help will be great.
Thanks in advance!Hi,
check with ur basis team to refresh the cache using the TR code SXI_CACHE
complete cache refresh with below url
http://host:port/CPACache/refresh?mode=full
Regards
srinivas -
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? -
Application messages are in the system log instead of the application log
Hi SAP GURUS.
The standard output is created from the outbound delivery .
All the messages are hitting the system log instead of the application log .
This is after the upgrade from 4.6c to ECC 6.0 .
Please provide the details how to move the log to the application log since the output is the standard output (SAP provided output type ).verzunof wrote:
Hello,
My system.log is filled with these messages, they repeat every second.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncReceive::waitForDMA - context not going inactive.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Do these messages indicate a problem? If so what that could be problem and the solution?
Can this contribute to the sleep/wakeup problem when iMac won't wakeup after being put to sleep manually and not sleeping according to Power Saving settings?
Thanks a lot.
verzunof wrote:
I'm not certain if those messages indicate a power issue but you can try *resetting the System Management Controller* and see if that helps. Here's how: http://support.apple.com/kb/HT1806
"The System Management Controller (SMC) is a chip on the logic board that controls all power functions for your computer. If your computer is experiencing any power issue, resetting the SMC may resolve it. The SMC controls several functions, including:
Telling the computer when to turn on, turn off, sleep, wake, idle, and so forth.
Handling system resets from various commands.
Controlling the fans."
Carolyn -
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
FeAlso 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.
-
AppleFWOHCI_Async messages in the system.log
Hello,
My system.log is filled with these messages, they repeat every second.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncReceive::waitForDMA - context not going inactive.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Do these messages indicate a problem? If so what that could be problem and the solution?
Can this contribute to the sleep/wakeup problem when iMac won't wakeup after being put to sleep manually and not sleeping according to Power Saving settings?
Thanks a lot.verzunof wrote:
Hello,
My system.log is filled with these messages, they repeat every second.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncReceive::waitForDMA - context not going inactive.
Jan 21 18:31:47 Maki-Mac kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Do these messages indicate a problem? If so what that could be problem and the solution?
Can this contribute to the sleep/wakeup problem when iMac won't wakeup after being put to sleep manually and not sleeping according to Power Saving settings?
Thanks a lot.
verzunof wrote:
I'm not certain if those messages indicate a power issue but you can try *resetting the System Management Controller* and see if that helps. Here's how: http://support.apple.com/kb/HT1806
"The System Management Controller (SMC) is a chip on the logic board that controls all power functions for your computer. If your computer is experiencing any power issue, resetting the SMC may resolve it. The SMC controls several functions, including:
Telling the computer when to turn on, turn off, sleep, wake, idle, and so forth.
Handling system resets from various commands.
Controlling the fans."
Carolyn -
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. -
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
CarloThis 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? -
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 -
Saved and sorted/filed mail messages missing
Saved and sorted/filed mail messages missing
October's messages are still there but all other messages are no longer in the folders. I have a confirmations folder with all forum and newsletter info for the last year that is empty. Where do these messages go?
I do not believe that I have it set to empty or delete itself after a certain time.
I can probably find these messages from comcast/gmail but still am wondering about this issue.
Thank you.Hi, sounds like a Save/Delete 1 month check in the box. I actually have a gmail account which gets sent a copy of every email from my other email accounts..Once each month I can Delete or Keep as I wish. Back Up....L
-
System Log Printer Directory Error
I'm attempting to resolve some error messages in my system log.
Here's one concerning my epson printer. I reinstalled the driver.
What is causing the error? I did trace the folders to /Library/Printers/EPSON/InkjetPrinter.
I can't locate a EPW/IJEPWAgent.app directory. So, is the error being cause because it can't find this 'missing' directory?
Feb 27 12:00:47 eden-maxwells-imac-3 com.apple.launchd.peruser.501[98] (com.epson.epw.agent): Bug: launchdcorelogic.c:4598 (24498):2
Feb 27 12:00:47 eden-maxwells-imac-3 com.apple.launchd.peruser.501[98] (com.epson.epw.agent): Path monitoring failed on "/Library/Printers/EPSON/InkjetPrinter/EPW/IJEPWAgent.app": No such file or directory
Thanks.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. -
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,
KiranI 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 contains mail errors for "mail cp:"
Hello,
My system log is filled with this message that occurs periodically. The server seems to work okay, but I could use your guidance on what it might be?
Jan 1 03:14:58 mail cp: error processing extended attributes: Operation not permitted
I cannot seem to find what this is referring to -- has anyone else seen this?
Mac OS X (10.4)I've noticed the same thing on my mac!
Feb 24 03:15:03 RooneysDualG5 cp: error processing extended attributes: Operation not permitted.
Judging from the time it occurs everyday (if I leave it on all night) I believe it is the system scheduled maintenance that is generating the error (apple set our systems to clean house at this default time).
Unfortunately, that is the extent of my knowledge, and I too would like to resolve this issue because I'm worried that something is preventing the system from EVER doing it's maintenance, now whether that error means nothing is getting done, or only one process is stopped up, I don't know!
I would think regular maintenance would be especially critical for your mail server, so I hope someone answers us quick!
I just found this info in my console: /var/log/daily.out –
Fri Feb 24 03:15:00 CST 2006
Removing old log files:
Removing scratch and junk files:
Removing scratch fax files
msgs: /var/msgs/bounds: No such file or directory
Backing up NetInfo data
Checking subsystem status:
disks:
Here it lists my disks, and everything gets boring after that...
But I think this means that some of the maintenance is getting done!
Maybe you are looking for
-
Can't print from new laptop with windows 8.1 to HP 2200 DTN
I can't print to 2200 DTN. have installed spftware and still has error
-
How do I view my iTunes purchases?
How do I see my purchases on iTunes???? I wish apple made this easier. I must be too left brained to understand.
-
Trouble changing APEX to serve https...
I installed 11g with Application Express 3.0.1.00.08. That is the version we are currently working with. It is serving off of 8080 at the moment, but we need it to run on on port 443. Can anyone please point to a GOOD guide on how to set this up? We
-
Questionfolder at startup, not able to repair disk
I got the questionfolder when I turned on my Macbook Air after an update. When I start it I can't find any disk at all (and yes, I've tried to install Mac OS X over again trough another Mac (from a MacBook Pro because I couldn't find any Mac OS X on
-
Hi, I am trying to change the status of Internal order from Technically completed to Release. But i am getting an error that ---Status REL is not allowed (order 4564564). We have created this order and till now zero value is used of actual budget