System.log fills up with bad packets errors (Multicast packet - CRC error)

Hello,
I've been trying to Google my problem but found no answers; hopefully someone can help me?
Whenever I'm online, my System.logs fills up (every second, and sometimes, multiple times each second) with the following message :
19/12/07 12:51:01 PM kernel AppleYukon2 - bad packet received. length: 60, packet status bits: Multicast packet, CRC error
19/12/07 12:51:01 PM kernel AppleYukon2 - bad packet received. length: 60, packet status bits: Multicast packet, CRC error
My DSL modem is connect directly into my iMac. It's a Speedstream 5360). I never have any problems connecting to the Internet and the speed I get is fine. When I configured my Network settings, I only added my PPPoE Service name username and âssword - everything else was automatically added (Ethernet configuration).
Is there anything I should change in the Advanced Settings?
The System.log causes me problem because it often causes the application Console to crash when I try to view it.

I should add that this problem didn't exist when I was using Tiger.
Also, when I called Apple Tech Support, I was simply told "just don't play with the Console".

Similar Messages

System.log fills up with uninstall_folder_path no 0

My system.log fills up with the following text:
Apr 10 22:09:48 Macken DelMonitor[60]: hokan
Apr 10 22:09:48 Macken DelMonitor[60]: uninstall_path no 0
Apr 10 22:09:48 Macken DelMonitor[60]: uninstall_folder_path no 0
Apr 10 22:09:50 Macken DelMonitor[60]: install_path yes
These four lines adds every other second, and just fills upp the system.log.
I habe tried to google but can not find any clues to what this is and how to make it stop!
Anyone have any suggestions?
I have a Mac Book Pro with verson 10.7.3
Regards,
Hokan

It's some third-party software that you installed, but I can't be more specific. If you can't figure it out any other way, you'll just have to start uninstalling things until the log messages stop.

System.log fills up with mDNSResponder[17]

My system.log will be filled in a 1 second intervall by the following message:
25.12.07 17:58:25 mDNSResponder[17] Failed to obtain NAT port mapping from router 192.168.0.1 external address 0.0.0.0 internal port 22 (ports are different).
Does any body have an idea what I have wrong configured. I'm using a router DGL-4300.
reagrds
wholler

Sure. This is what I gleaned from a mere 2 seconds with the Berkley packet monitor. I don't know if it is very usable, but at least you can see how bad my router was getting spammed:
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(I0''
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(K<'
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49773
Byte count: 396
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
123
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:DeletePortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPCon</div>
nection:1"></u:DeletePortMappingResponse></s:Body></s:Envelope>
0
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49774
Byte count: 390
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
11d
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnec</div>
tion:1"></u:AddPortMappingResponse></s:Body></s:Envelope>
0
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(5A''
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49776
Byte count: 390
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
11d
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnec</div>
tion:1"></u:AddPortMappingResponse></s:Body></s:Envelope>
0
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E( ''
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49778
Byte count: 385
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
11d
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnec</div>
tion:1"></u:AddPortMappingResponse></s:Body></s:Envelope>
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(''
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49780
Byte count: 385
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
11d
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnec</div>
tion:1"></u:AddPortMappingResponse></s:Body></s:Envelope>
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49779
Byte count: 98
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
0
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: TCP
Source IP: 192.168.0.145
Source Port: 49781
Destination IP: 192.168.0.1
Destination Port: 4444
Byte count: 919
Raw Data:
4CPOST /wipconn HTTP/1.1
Content-Type: text/xml; charset="utf-8"
SOAPAction: "urn:schemas-upnp-org:service:WANIPConnection:1#DeletePortMappin
g"
User-Agent: Mozilla/4.0 (compatible; UPnP/1.0; Windows 9x)
Host: 192.168.0.1:4444
Content-Length: 604
Connection: close
Pragma: no-cache
<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-E
NV:Body><m:DeletePortMapping xmlns:m="urn:schemas-upnp-org:service:WANIPConn
ection:1"><NewRemoteHost xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:d
t="string"></NewRemoteHost><NewExternalPort xmlns:dt="urn:schemas-microsoft-
com:datatypes" dt:dt="ui2">9999</NewExternalPort><NewProtocol xmlns:dt="urn:
schemas-microsoft-com:datatypes" dt:dt="string">TCP</NewProtocol></m:DeleteP
ortMapping></SOAP-ENV:Body></SOAP-ENV:Envelope>
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(#''
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: TCP
Source IP: 192.168.0.145
Source Port: 49784
Destination IP: 192.168.0.1
Destination Port: 4444
Byte count: 1432
Raw Data:
4EPOST /wipconn HTTP/1.1
Content-Type: text/xml; charset="utf-8"
SOAPAction: "urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping"
User-Agent: Mozilla/4.0 (compatible; UPnP/1.0; Windows 9x)
Host: 192.168.0.1:4444
Content-Length: 1119
Connection: close
Pragma: no-cache
<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-E
NV:Body><m:AddPortMapping xmlns:m="urn:schemas-upnp-org:service:WANIPConnect
ion:1"><NewRemoteHost xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="
string"></NewRemoteHost><NewExternalPort xmlns:dt="urn:schemas-microsoft-com
:datatypes" dt:dt="ui2">9999</NewExternalPort><NewProtocol xmlns:dt="urn:sch
emas-microsoft-com:datatypes" dt:dt="string">TCP</NewProtocol><NewInternalPo
rt xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="ui2">9999</NewInter
nalPort><NewInternalClient xmlns:dt="urn:schemas-microsoft-com:datatypes" dt
:dt="string">192.168.0.145</NewInternalClient><NewEnabled xmlns:dt="urn:sche
mas-microsoft-com:datatypes" dt:dt="boolean">1</NewEnabled><NewPortMappingDe
scription xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="string">iC99
99</NewPortMappingDescription><NewLeaseDuration xmlns:dt="urn:schemas-micros
oft-com:datatypes" dt:dt="ui4">0</NewLeaseDuration></m:AddPortMapping></SOAP
-ENV:Body></SOAP-ENV:Envelope>
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49784
Byte count: 385
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
11d
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnec</div>
tion:1"></u:AddPortMappingResponse></s:Body></s:Envelope>
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(T.''
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(1''
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49785
Byte count: 396
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
123
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:DeletePortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPCon</div>
nection:1"></u:DeletePortMappingResponse></s:Body></s:Envelope>
0
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(,''
Start Time: 23:27:16
Last Hit: 23:27:16
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(P(z''
Start Time: 23:27:16
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49787
Byte count: 396
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
123
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:DeletePortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPCon</div>
nection:1"></u:DeletePortMappingResponse></s:Body></s:Envelope>
0
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(7$''
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(|J''
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49789
Byte count: 93
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49790
Byte count: 390
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
11d
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnec</div>
tion:1"></u:AddPortMappingResponse></s:Body></s:Envelope>
0
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(t''
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.145
Source Port: 49791
Destination IP: 192.168.0.1
Destination Port: 4444
Byte count: 919
Raw Data:
4JPOST /wipconn HTTP/1.1
Content-Type: text/xml; charset="utf-8"
SOAPAction: "urn:schemas-upnp-org:service:WANIPConnection:1#DeletePortMappin
g"
User-Agent: Mozilla/4.0 (compatible; UPnP/1.0; Windows 9x)
Host: 192.168.0.1:4444
Content-Length: 604
Connection: close
Pragma: no-cache
<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-E
NV:Body><m:DeletePortMapping xmlns:m="urn:schemas-upnp-org:service:WANIPConn
ection:1"><NewRemoteHost xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:d
t="string"></NewRemoteHost><NewExternalPort xmlns:dt="urn:schemas-microsoft-
com:datatypes" dt:dt="ui2">9999</NewExternalPort><NewProtocol xmlns:dt="urn:
schemas-microsoft-com:datatypes" dt:dt="string">TCP</NewProtocol></m:DeleteP
ortMapping></SOAP-ENV:Body></SOAP-ENV:Envelope>
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49792
Byte count: 390
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
11d
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnec</div>
tion:1"></u:AddPortMappingResponse></s:Body></s:Envelope>
0
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49793
Byte count: 391
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
123
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:DeletePortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPCon</div>
nection:1"></u:DeletePortMappingResponse></s:Body></s:Envelope>
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49794
Byte count: 98
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
0
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(p''
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49796
Byte count: 385
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
11d
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnec</div>
tion:1"></u:AddPortMappingResponse></s:Body></s:Envelope>
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49797
Byte count: 391
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
123
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:DeletePortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPCon</div>
nection:1"></u:DeletePortMappingResponse></s:Body></s:Envelope>
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49798
Byte count: 390
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
11d
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:AddPortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnec</div>
tion:1"></u:AddPortMappingResponse></s:Body></s:Envelope>
0
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E( 3''
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: TCP
Source IP: 192.168.0.1
Source Port: 4444
Destination IP: 192.168.0.145
Destination Port: 49799
Byte count: 396
Raw Data:
HTTP/1.1 200 OK
SERVER: ipOS/6.8 UPnP/1.0 IGD/1.0
EXT:
Transfer-Encoding: Chunked
123
<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/en
velope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body
<div class="jive-quote"><u:DeletePortMappingResponse xmlns:u="urn:schemas-upnp-org:service:WANIPCon</div>
nection:1"></u:DeletePortMappingResponse></s:Body></s:Envelope>
0
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: ICMP
Source IP: 192.168.0.1
Source Port: 0
Destination IP: 192.168.0.145
Destination Port: 0
Byte count: 48
Raw Data:
E(#''
Start Time: 23:27:17
Last Hit: 23:27:17
Protocol: UDP
Source IP: 192.168.0.145
Source Port: 5353
Destination IP: 192.168.0.1
Destination Port: 5351
Byte count: 12
Raw Data:
-----------------------------------------------------------------------

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 filling up with: mbp kernel[0]: dp events: 0x04

Dec 21 17:09:52 mbp kernel[0]: dp events: 0x04
This line seems to repeat 5 or 6 times per minute, filling system.log.
Looks like it started Dec 19th. I don't see any obvious unusual thing I did at that time.
Any ideas?
Thanks, jeff

Although Apple has not fixed this yet, I have learned some interesting things. While on the phone with Apple, they had me run a Data Capture program to collect info about my system to send back to them.
While running the application, I had Console open so I could look at the system log. To my surprise, after running this application, the repeating dp events: 0x04 completely stopped and the mouse cursor behaved normally. The mouse continued to behave normally until I put the computer to sleep and woke it up again.
In summary:
1) The dp events: 0x04 messages are present when the mouse skips and not present when it doesn't. This seems like proof that the muliple writes to the system log are what make the cursor skip.
2) Running Capture Data.app (from the Apple tech) runs a handful of scripts that not only capture data, but also kills the dp events for some reason.
I have verified this four different times and reported my findings to the Apple tech I was speaking to.
Can anyone else who receive the data capture program from Apple give this a shot? Just have Console open and look at your system log before, during, and after running the program. Perhaps you'll see as I did that the dp events go away and your mouse works right (at least until sleep).

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.

Log filling up with crlcache.db errors

I posted an earlier question where my log was filling up with errors from Adobe Air.
I corrected that issue by clearing the adobe keychain.
My logs are still filling, however, with the following:
8/2/11 3:42:46.057 PM sandboxd: ([390]) WebProcess(390) deny file-read-data /private/var/db/crls/crlcache.db
This only happens when I'm running safari.
I've tried recreating an empty /private/var/db/crls folder but it immediately started happening again.
Thoughts?

I believe its fixed.
open Keychain Access then select Keychain Access -> Keychain First Aid
Run a repair
Select the crlcache.db keychain and right click -> delete files and associations
Run a repair
I had to do the set twice until crlcache.db was no longer in my keychain. After it was removed, the logs no longer posted when I used safari.

SATA driver flooding System.log, filling up startup disk

My system.log seems to be filling up with SATA error messages, about 10 per second. The log is now so large that I can't even get the Console app to open it (only in Open Quick, which seems to show little snippets of the log only).
This seems to have started when I installed an Initio 1623 SATA controller as part of a GraniteDigital drive upgrade. The controller worked, the drives worked. I've since pulled the controller card, but it seems the driver continues to flood the log file!
The drivers for the controller are apparently built in to OSX (at least in 10.4.7...) so there is no way to update the driver separately.
Restarting the machine hasn't helped. For now, I have to keep moving files to other disks to keep this G5 functioning.
How can I A) delete the log file to gain some time?
B) make this error stop?
Thanks.

Well - maybe it isn't a SATA driver system.log. I can't read the system.log because it keeps refreshing so the data in on the screen for less than a second before it refreshes. AND there is so much disk thashing that the system is barely responsive.
The only visible log entries are:
Jul 19 04:28:10 Platinum kernel[0]: Inic1622: SATA - Int no command active (repeated about ten times)
Jul 19 04:28:10 Platinum kernel[0]: and active
and repeat....
The log file is showing a size of 4.5 GB

Time Machine will not complete a system backup and terminates with "Unable to complete backup. An error occurred while copying files to the backup volume. This follows a problem when Time machne terminated when the volume was almost full.

On 11/1/2011, Time Machine (TM) terminated with an error message I did not record. I noted that the drive was full and decided to do a separate complete bootable system backup using Carbon Copy Clone (CCC), before clearing the TM volume and trying to start it over clean. Part way through the full system backup CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". That was about the time that TM malfunctioned, so I assumed they were related. After starting CCC over a couple of times, and getting the same error message, I let it go through to completion of the backup, which took three or four hours. I then ran tests using Disk Utility and verified that there was nothing physically wrong with both the internal hard drive and the TM volume. I also erased and reformatted the TM volume. However, every time I started Time Machine, it would record a few GB and terminate with "Unable to complete backup. An error occurred while copying files to the backup volume". I restarted the computer with no change in results. Note that prior to starting the CCC backup, I "Repaired Permissions", "zapped the PRAM" and "re-set the SMC", hoping to have a clean bootable system on the backup. I ran Techtool and no problems were found.
I'm running this on an Intel iMac under 10.5.8 and recording to a 500GB My Passport drive. My hard drive is only about half full at 246 GB. My assessment is that something happened at 16-28-16 on 11/1/2001 to screwup the Backup Directory in the file at "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". My question is, how do I fix it?
I had just completed writing everything above here, explaining the problems I had been encountering for the past 24 hours. I had the Time Machine window standing open on the desktop where I could see it, having recentlycleared it after the last termination. As I was proofing what I had written, I looked at the window and noted that the clock had started a new run for a full back up, since all prior efforts had failed and the TM volume was empty. As I watched and waited for it to fail again, as it had been doing at about 13 GB, it kept going and going until it just finished a complete backup, about 4.5 hours later, with my having done nothing. Now my question would have to be - what could possiibly have happened to make it perform this way? It will be interesting to see if it continue to operate normally, or if the problem will return, in a later backup run.

jcm21 wrote:
CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16"
You should not keep those files for long, and probably shouldn't back them up (if you need them at all -- since you do regular backups, I'm doubtful just how worthwhile that feature is).
"Unable to complete backup. An error occurred while copying files to the backup volume".
One of Apple's maddeningly incomplete messages. Most likely, there's a problem with a file (quite possibly the one CCC didn't like). See #C3 in Time Machine - Troubleshooting for details and instructions on finding and fixing it.
If you continue running the Directory Protection app, be sure to exclude your Time Machine drive from it (as it will just take up lots of room, and won't help repair your backups if there's a problem); and exclude the folders it creates from being backed-up by Time Machine (as they'll create large backups, and you probably can't use the backed-up folders anyway), per #10 in Time Machine - Frequently Asked Questions.

The system log is full with this !!!   Can you help me?

Hi gurus, please, I need your help.
Our log is fulled with an error ( I mean aroung 10 MB of logs with the same error)
Please, !! We are in SP15 EP 7.0
java.util.zip.ZipException: error in opening zip file
     at java.util.zip.ZipFile.open(Native Method)
     at java.util.zip.ZipFile.<init>(ZipFile.java:111)
     at java.util.zip.ZipFile.<init>(ZipFile.java:127)
     at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchiveInfo(AbstractLog.java:328)
     at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchives(AbstractLog.java:455)
     at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchives(AbstractLog.java:478)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.getAttribute(DefaultMBeanInvoker.java:129)
     at javax.management.StandardMBean.getAttribute(StandardMBean.java:229)
     at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1296)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
     at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
     at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)
     at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
     at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
     at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfo(LogControllerFacade.java:227)
     at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfosWithPattern(LogControllerFacade.java:193)
     at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfos(LogControllerFacade.java:174)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.getAttribute(DefaultMBeanInvoker.java:129)
     at javax.management.StandardMBean.getAttribute(StandardMBean.java:229)
     at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1296)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
     at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
     at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)
     at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
     at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.tc.logviewer.mbean.LocalLVMBeanServer.invoke(LocalLVMBeanServer.java:73)
     at $Proxy165.getAttribute(Unknown Source)
     at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getAttribute(AbstractLogDepot.java:236)
     at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getLogDescriptors(AbstractLogDepot.java:84)
     at com.sap.tc.logviewer.mbean.ServerModelLogDepot.getLogDescriptors(ServerModelLogDepot.java:79)
     at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup$GetLogDescriptorsTask.run(ServerModelLogDepotGroup.java:60)
     at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup.execute(ServerModelLogDepotGroup.java:173)
     at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup.getLogDescriptors(ServerModelLogDepotGroup.java:119)
     at com.sap.tc.logviewer.mbean.LogviewerServer.getLogs(LogviewerServer.java:137)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at javax.management.StandardMBean.invoke(StandardMBean.java:286)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.tc.logviewer.client.j2ee.J2EELogviewerServerInvoker.invoke(J2EELogviewerServerInvoker.java:111)
     at com.sap.tc.logviewer.client.j2ee.J2EELogviewerServerProxy.getLogs(J2EELogviewerServerProxy.java:105)
     at com.sap.tc.logviewer.client.base.LogviewerClientImpl.getLogs(LogviewerClientImpl.java:114)
     at com.sap.lm.webadmin.logviewer.impl.LV_View.getLogs(LV_View.java:865)
     at com.sap.lm.webadmin.logviewer.impl.LV_View.fetchLogs(LV_View.java:834)
     at com.sap.lm.webadmin.logviewer.impl.LV_View.fetchView(LV_View.java:516)
     at com.sap.lm.webadmin.logviewer.impl.LV_View.fetchView(LV_View.java:496)
     at com.sap.lm.webadmin.logviewer.impl.LV_View.fetchView(LV_View.java:492)
     at com.sap.lm.webadmin.logviewer.impl.LVUI.openView(LVUI.java:609)
     at com.sap.lm.webadmin.logviewer.impl.LVUI.openView(LVUI.java:577)
     at com.sap.lm.webadmin.logviewer.impl.LVUI.openView(LVUI.java:573)
     at com.sap.lm.webadmin.logviewer.LVView.onActionOpenSingleView(LVView.java:1648)
     at com.sap.lm.webadmin.logviewer.wdp.InternalLVView.wdInvokeEventHandler(InternalLVView.java:1560)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Thanks in advance

Hi,
have you take a look at SAP Note 701330 ?
One thread looking like your problem :
Re: error in opening zip file after Patch 4 HF6 install
Fabien.

[workaround] log filling up with "ACPI group/action undefined"

I use Arch with a HP 510 notebook and my /var/log/messages.log is filled up with:
Aug 19 14:15:36 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:15:36 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:15:36 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:15:36 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:15:36 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:15:36 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:16:06 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:16:06 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:16:06 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:16:06 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:16:06 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:16:06 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:16:06 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:16:07 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:16:07 hp510 logger: ACPI group/action undefined: video / C054
Aug 19 14:16:07 hp510 logger: ACPI group/action undefined: video / C054
Any suggestions?
Last edited by fijam (2009-08-20 22:35:10)

Turns out that the message is triggered when the laptop's lid is closed for more than a few seconds. I have no idea if that's a bug but I worked it around in handler.sh before the catch-all condition like that:
video)
case "$2" in
C054) : ;;
*) logger "ACPI video action undefined: $2" ;;
esac
It's probably the Wrong Way but I am quite sleepy and it appears to be working.
Thanks for suggestions.

Accounting Log filling up with useless data

I am getting my ACS Accounting logs filled with useless data from about 12 devices. I think I have found the cause - I just don't know how to fix it.
The accounting data has a username we have not used for months, and I stumbled upon this by looking at various show commands on the devices that are causing the problem.
When I do a "sh aaa sessions", I see this:
CE-WIN-IDF16-3750-Stack1#sh aaa session
Total sessions since last reload: 189
Session Id: 1
   Unique Id: 127
   User Name: *not available*
   IP Address: 0.0.0.0
   Idle Time: 0
   CT Call Handle: 0
Session Id: 354
   Unique Id: 263
   User Name: cenetmgmt
   IP Address: 10.62.7.15
   Idle Time: 0
   CT Call Handle: 0
Session Id: 626
   Unique Id: 410
   User Name: leehoyle
   IP Address: 10.62.7.15
   Idle Time: 0
   CT Call Handle: 0
I would LOVE to get rid of that Session ID: 354 if I could. I can't seem to find a suitable "clear" command. Any help out there?
Thansk in advance!
Lee Hoyle

I am not trying to access anything I keep getting the message that my cloud is full than go to it to find that is is full of things from my computer and pictures from the Sims game spent 3 hours yesterday as it kept telling me that Verizon was not available. Why is my cloud not backing up my phone but randomly backing up my computer which I do not need. This is using the desktop Icon. I have not even opened it on my desktop until I tried to delete the stuff on it it did this on its own.

System Log Filling Up - Why?

What is causing this to be written to the System log and how do I stop it?
10/31/07 4:15:46 PM com.apple.launchd[1] (com.mozy.backup660) ...
Thanks for any help.

Yes, I used Mozy very briefly, but I deleted the application (I think) and canceled the Mozy account. What I want to know is how do I stop launchd from trying to launch a backup, failing and logging this message.

Log filling up with kadmind: no such file or directory while initializing

My log files are being spammed with
"kadmind; No such file or directory while initializing, aborting"
followed by edu.mit.kadmind exiting and respawning and then 4x:
"krb5kdc: cannot initialize realm My-FQDM.NET - see log file for details"
Not surprisingly, Kerberos logins do not work, for instance from iCal I get:
"Cannot contact any KDC for requested realm"
This is a brand new iMac with a brand new install of OS X Leopard, using "Standard" configuration. I'm a complete network admin newb and acknowledge that; I could really use some help getting Kerberos working, and failing that, getting it to stop respawning and spamming the error logs.
Edit: Sorry, wrong forum, reposted here:
http://discussions.apple.com/thread.jspa?threadID=1934679&tstart=0
Message was edited by: Derek Jones3

Hm, I definitely have a reverse PTR. But there's also definitely a problem with Kerberos. In the Directory, I click Edit for a user and get a GSSAPI Error (cannot find ticket for requested realm) followed by a "if you haven't dismissed the Kerberos authentication dialog by clicking 'Cancel', chances are there is a problem with Kerberos." Interestingly, there's never a dialog presented to me.
In case it's relevant, as mentioned, this is a new iMac. It will not boot from the OS X Server Install DVD - I have to start out with the client version of OS X and run the installer from the disc, and then reboot sans install DVD. If I try to boot from the DVD it restarts over and over again. Enterprise support said this is "normal" since the install DVD comes with 10.5.4 - it won't boot from a machine that came with 10.5.6 client.
Is it possible that something that the client version does with Kerberos (standalone machine?) doesn't get corrected in the Server install, preventing it from working? I'm postulizing this theory as I see in my error log shortly after boot:
com.apple.KerberosAutoConfig[3244] Couldn't find KerberosClient config record

System logs filling up ALOT of disk space!

My syslogs are filling up my entire hdd space.
I checked top and it is constantly running at around 25% CPU.
These are the 3 offending logs being written:
everything.log
kernel.log
messages.log
I did a tail -f on all 3 files, and these are repeatedly loop, seems like a kernel issue: -> tail -f output: http://pastebin.com/m43e12d7e
Any idea how I can remedy this?
Thanks!

apparently this is something to do with cx88, which appears to be a tv tuner driver. don't know why it's logging so verbosely though, looks like interrupt requests or something. anyway i guess one thing to do is make sure you have the right options for the card in /etc/modprobe.d/. I think there are some good v4l wikis out there that explain how to do this

System.log fills up with bad packets errors (Multicast packet - CRC error)

Similar Messages

Maybe you are looking for