Strange repetitive entry in system log

8/7/11 7:06:10.000 PM kernel: macx_swapon SUCCESS
8/7/11 7:06:11.000 PM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/7/11 7:06:11.000 PM kernel: macx_swapoff SUCCESS
8/7/11 7:06:44.000 PM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/7/11 7:06:44.000 PM kernel: macx_swapoff FAILED - 2
8/7/11 7:07:17.000 PM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/7/11 7:07:17.000 PM kernel: macx_swapoff FAILED - 2
8/7/11 7:07:50.000 PM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/7/11 7:07:50.000 PM kernel: macx_swapoff FAILED - 2
Many more identical entries.
Anyone know what it means?
Dan Sokol

I am running Lion on a Late 2008, 15-Inch MacBook Pro.
Software Mac OS X Lion 10.7 (11A511)
Memory 4 GB 1067 MHz DDR3
Processor 2.4 GHz Intel Core 2 Duo
I have a 500GB disk partitioned and the main startup partition has 47GB free out of 200GB.
I get similar reports to Dan every minute:
8/11/11 11:11:23.000 AM kernel: macx_swapoff FAILED - 2
8/11/11 11:11:56.000 AM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/11/11 11:11:56.000 AM kernel: macx_swapoff FAILED - 2
8/11/11 11:12:29.000 AM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/11/11 11:12:29.000 AM kernel: macx_swapoff FAILED - 2
8/11/11 11:13:02.000 AM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/11/11 11:13:02.000 AM kernel: macx_swapoff FAILED - 2
8/11/11 11:13:36.000 AM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/11/11 11:13:36.000 AM kernel: macx_swapoff FAILED - 2
8/11/11 11:14:09.000 AM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/11/11 11:14:09.000 AM kernel: macx_swapoff FAILED - 2
8/11/11 11:14:42.000 AM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/11/11 11:14:42.000 AM kernel: macx_swapoff FAILED - 2
8/11/11 11:15:15.000 AM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/11/11 11:15:15.000 AM kernel: macx_swapoff FAILED - 2
8/11/11 11:15:48.000 AM kernel: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
8/11/11 11:15:48.000 AM kernel: macx_swapoff FAILED - 2
This appears when no memory hog programmes are running (only Safari, Activity Monitor and console) with more than 1.5GB of the 4GB memory being reported free in Activity Monitor. I see 725mb of Swap being used - before Lion, swap was always zero for me. Not sure whether this is something I need to worry about - other than the fact that it is cluttering up the logfiles.
Aruna

Similar Messages

Mysterious repeated entries in System Log

I just noticed this tonight, as DejaVu was performing the daily backup, but have never seen it before. In the System Log, beginning at 2:15 this afternoon and every minute thereafter is the entry:
+May 11 20:49:22 mike-harrisons-power-mac-g4 launchd: org.postfix.master: 9 more failures without living at least 60 seconds will cause job removal+
I've noticed nothing out of the ordinary; I probably would never have known had I not had Console displaying the System Log. But what could this mean? I don't like seeing the word 'failure' anywhere in anything having to do with the System.
Thanks.

Thanks, guys...
It sure does look like something related to mail delivery. But when I looked at the System Log again this morning, that entry no longer appears. It's one of those strange mysteries... like finding yourself in bumper-to-bumper traffic on a freeway and then, after what seems like an eternity, things start moving again but you never find out what the cause of the tie-up was.
Thanks again.

No Name Available / No Reverse DNS Entry in System Log

On our network, we have two Macs running different versions of OSX Server software. Our "main" server is a G5 dual 2GHz (2.5 Gb RAM) running Leopard Server 10.5.6, and it runs most of our major services such as Open Directory (it’s designated an OD Master), Mail, Web, FTP and DNS. Our "secondary" server is an XServe dual 2.3GHz (G5) (2 Gb RAM) running Tiger Server 10.4.11. It only runs the AFP service and exists solely as our company’s fileserver. Both of its ethernet ports are connected to our company’s 10/100 switch, and the ports are configured as follows: Built-in Ethernet 2 (BSD Device Name en1) IP addr. 10.1.10.154; Built-in Ethernet 1 (BSD Device Name en0) IP addr. 10.1.10.152. In the Network control panel’s Network Port Configurations, Built-in Ethernet 2 (IP address 10.1.154) is moved to the top of the configuration window and as a result, Network Status indicates that that XServe "is connected to the Internet via Built-in Ethernet 2."
That said, I see the following every 30 minutes in the System log:
Apr 20 11:01:51 NAGXServe2 servermgrd: servermgr_dns: no name available via DNS for 10.1.10.154
Apr 20 11:01:51 NAGXServe2 servermgrd: servermgr_dns: no reverse DNS entry for server, various services may not function properly
This doesn’t cause any apparent problems in daily operation but if it’s something I could fix myself, I’d be willing to try. In the TCP/IP configuration for both ports, the DNS Server entry points to our "main" G5 server (which has a static IP address) and the Search Domain entry is that "main" G5 server’s domain name.
In the DNS setup on the "main" G5 server, its domain name is entered in the "Primary Zone" field and its static IP address is entered in the Reverse Zone field; Whois lookups work successfully both forward and backward. But there is no mention of our "secondary" server anywhere in the "main" G5 server’s DNS setup.
Thanks for any help!

I am going to assume that the IP addresses you have given are REAL.
You have to add an entry for NAGXServe2 in the DNS server's (NAGXServe1?) configs.
First, what you need to enter are hostnames. The zone/domainname (example.com) should resolve to one representative server (your main server) for www service's sake, but otherwise, even your main server should have its own hostname (hostname.example.com).
Let's say you already have an entry for your domain, example.com. This zone should already have one (or even two) A record, nagxserve1.example.com (and maybe example.com, without any hostname). You need to add another A record for nagxserve2.example.com with the IP address 10.1.10.154.
You do this buy selecting "Computer (A) record" from the "Add record" dropdown button. A new A record called "newMachine" should appear under the zone record. If you can't see it, try clicking on the little triangle next to the zone/domain name.

Strange endless errors in system log

I've noticed my system (PMac G5 Quad Core) keeps seizing up occasionally for 4-5 seconds at a time, so I looked at the system log, and it's filled with an endless series of the same error—like a dozen entries per second. Can anyone tell me what this means and how I might fix it? The error reads:
com.apple.SystemStarter[31]: Break on _THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___Y OU_MUST_EXEC_() to debug.

Hi--
I think this is related to the Quicktime 7.2 update. This thread has a bunch of posts (over 390 as I type!) discussing this. Some people even have the same log errors as you. Read down toward the bottom of the thread for an in-depth discussion of possible causes and cures.
As for a cure, MacFixit has posted a version of the cure that was proposed in that thread, if you want to try it first and not bother sorting out the wheat from the chaff in that the other discussion.
charlie

No entries in System Log

Hi All,
One of my systems is on Windows NT,Oracle 8.1.7.4.1 with SAP version 4.6C.In the system log in SM21 we never get any logs we just get a line for an Operation Mode switch,no other thing is logged in the system Log.
Any sought of help would be appreciated.
Regards
Bharathwaj V

Hi
Can you see SLOG* from OS level ?
\usr\sap\SID\DVEB**\log\SLOG00.LOG ..
THanks
Prince Jose

System.log flood by strange messages

Hi all, I've see this strange messages on my system.log it is a real flood:
Feb 27 00:50:58 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:58: --- last message repeated 2 times ---
Feb 27 00:50:58 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:58 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:58: --- last message repeated 2 times ---
Feb 27 00:50:58 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:51:00 Melchior-1 kernel[0]: m71482545 0
anyone known which process is doing that ?

Yup. Same issue here. It's quite disconcerting.

Word 2008 & System Log Entries

Whenever I open Word 2008 there is a flood of never ending entries in System Log as long as Word 2008 is open. This is an example:
*Feb 20 14:40:10 Macintosh Microsoft Word[728]: CGBitmapContextGetData: invalid context*
*Feb 20 14:40:40: --- last message repeated 276 times ---*
Are others with Word 2008 and my Mac configuration receiving similar System Log entries?
If so, any suggestions for a solution?

I have that same problem lookin in my console.. can anybody help us out here???

Mcxd.app reports errors in system.log

Hello!
On every startup of my mac os x server I get the following entries in system.log from mcxd.app.
Oct 9 20:34:45 sebastian /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetLocallyHostedNodeNames(): dsFindDirNode() == -14008
Oct 9 20:34:45 sebastian /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetSearchPath(): DSGetLocallyHostedNodeNames() == -14956
Oct 9 20:34:45 sebastian /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetCurrentConfigInfo(): DSGetSearchPath() == -14956
Oct 9 20:34:45 sebastian /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSGetCacheInfo(): DSGetCurrentConfigInfo() == -14956
Oct 9 20:34:45 sebastian /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: * MCXD.getComputerInfo: Couldn't get cache info -14956
How can I get rid off them? Any hints?
Thanx in advance
Gerhard

Nigel,
While the error messages you are seeing might not be anything to worry about (you will see some of these even in the best of circumstances, but I cannot speak to yours, specifically), you shouldn't be seeing any "wonky" behavior. The fact that you are indicates that something might, indeed, be wrong.
My best advice to you would be to start with a clean slate. I just received a new machine, myself (this beautiful new 17" Powerbook), and I spent the past day doing just that: starting "clean."
What I mean by this is formatting the drive right out of the box, then reinstalling. And, not just any format, but a "zeroing" of the entire drive. This took about 45 minutes on my PB, but the process will "map out"any potential bad blocks on the drive, thereby reducing the possibility of encountering disk errors for the near future. Another good reason to reinstall yourself, even if you don't "zero" the drive, is that Apple often ends up installing the wrong version of an OS to a given machine, especially if that machine has just been released. We see many cases where a user will find, by reinstalling from the disks that come with new Mac models, that the OS is slightly different than the one that was originally installed, and that the disk-installed version works without problems. Hmmm.
Unless and until you do this yourself, you will not have a firm foundation from which to troubleshoot any problems you might be having. If, after having done this, you find that you still have problems, the next thing to look for is a bad RAM module. If you rule out a bad RAM module, only then should you consider the possibility that something is wrong with the machine, itself.
Scott

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

Flood on system.log kernel[0]: m71482545 0

Hi all, I've see this strange messages on my system.log it is a real flood:
Feb 27 00:50:58 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:58: --- last message repeated 2 times ---
Feb 27 00:50:58 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:58 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:58: --- last message repeated 2 times ---
Feb 27 00:50:58 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:51:00 Melchior-1 kernel[0]: m71482545 0
anyone known which process is doing that ? After two months i have still this problem... Anyone have the same ? Please check your system.log with a grep Best regards

Having the same problem here, and it is slowing down the machine:
Aug 25 03:16:11 kroll kernel[0]: m407168d8
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m407168d8
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m407168d8
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
The last time I tried, a reboot cured the problem, but only for so long.

Strange Entries in System and Console Logs

I have some strange entries in my system and console logs. In the system log, I regularly see these entries:
Feb 24 21:07:29 joseph-youngs-computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: owner of process not logged in on console - exiting.
Feb 24 21:20:32 joseph-youngs-computer kernel[0]: (82: coreservicesd)tfp: failed on 0:
In my console log, I regularly find these entries:
2006-02-25 09:23:24 -0600
2006-02-24 21:07:30.530 loginwindow[803] FSResolveAliasWithMountFlags returned err = -43
On occasion, I find something like this in my console log:
Assert failed: /Users/dave/dev/flash/player/FlashPlayer/platform/mac/plugins/../../../core/spl ay.cpp:7105
I admit to being something of a novice with the Mac, so I am not sure what to make of these entries, though I never noticed anything like this on my eMac, or on my prior iMac. Also, on the entry above, there are no users named dave on my Mac.
Has anyone else noticed this, and can anyone shed any light on what these messages mean?

Resolved with a clean install.

Repetitive System log entry

Hi
Looking at my system log in Console I see this entry repeating every 30 seconds:
launchd: getty repeating too quickly on port /dev/fax, sleeping
Appreciate any help understanding its origin and how I can stop this process from recurring.
thanks

Thanks.
While Google didn't directly help, as I read various posts I realized checking "receive faxes on this computer" in System Preferences>Print & Fax panel was creating the repetitive message. Unchecking it stopped the message in the System Log.
Aloha from Big Island.

Solution manager system log - strange entries

Hi Everyone,
the problem we are facing in Solution Manager system log every five minutes appears a new error message:
2 Database error -30082 at CON
0 > SQL30082N Security processing failed with reason "24"
0 > ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
First of all the landscape: ECC, BI, CRM, PI and Solman. Each system is DEV, QUA, PRD - except Solution Manager.
Result of going to see the logs within work directory:
Connect to %_DCR_XXXXX as db2dcr with DB6_DB_NAME=DCR;DB6_DB_HOST=xxxxxx;DB6_DB_SCHEMA=SAPSR3;DB6_DB_SVCENAME=5912
C *** ERROR in DB6Connect[dbdb6.c, 1727] CON = 1 (BEGIN)
C &+***      DbSlConnectDB6( SQLDriverConnect ): [IBM][CLI Driver] SQL30082N Security processing failed with reason "24" ("USE
C &+***      RNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
C &+***
C &+***
C &+***      ABAP location info 'CL_SQL_CONNECTION=============CP', 337
C &+***
C *** ERROR in DB6Connect[dbdb6.c, 1727] (END)
C *** ERROR => DbSlConnect to 'DCR' as 'db2dcr' failed
[dbdb6.c      1732]
Some of the systems are being connected successfully and the error messages in SM21 are not related to those systems. But some of the systems like DCR cannot be reached. And this fact causing the error messages.
I haven't configured Solution Manager because I have joined the project later. I would like to know what job is trying to access the satellite system and for what purpose.
On solution manager side I have checked all the scheduled background jobs - all of them have been executed successfully.
There some of them are scheduled but it is hard understand what is purpose of the job.
I have checked and corrected system landscape through SMSY and have maintained all the RFCs. They all OK now.
What else could force to make a connection to satellite system? And where is the place where it is hardcoded local(satellite) db2 connection entry?
Like I said before, some of the systems are being connected but some not. The one which has not been connected - there was recently changed SAP master password. I believe this is the key to resolve the problem. But the system itself operating 100% correctly.
Perhaps it could be CCMS that makes some extra connections to collect the data from the monitored systems. But I have checked all the RFC's in SM59 and they were OK.
Any ideas or suggestions would be appreciated.
Thanks in advance,
Kind regards,
Artjom.

Kaustubh Krishna,
thank you for respond.
It was dbacockpit. The connection was maintained with old db2sid password. And it was causing problematic log entries.
Problem was solved.
Points awarded.
Thanks,
kind regards,
Artyom

Strange system.log entries. Have I been compromised? Related to ARD

Every two minutes my system.log posts a new entry that I am having a UDP WritePacket error 65 and it looks as if its trying to connect to a range of IP's that are hosted by pacbell. I do not have any systems outside my network on my ARD so not sure what the heck is going on. Here is a copy of the messages:
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.33
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.64
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.95
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.174
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.27
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.161
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.98
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.126
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.61
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.130
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.67
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.51
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.92
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.74
Mar 24 15:06:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.57
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.179
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.45
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.90
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.14
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.48
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.88
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.229
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.69
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.37
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.54
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.84
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.23
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.79
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.173
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.149
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.80
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.53
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.21
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.86
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.111
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.168
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.44
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.40
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.124
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.29
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.166
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.133
Mar 24 15:07:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.56
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.33
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.64
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.95
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.174
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.27
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.161
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.98
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.126
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.61
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.130
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.67
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.51
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.92
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.74
Mar 24 15:08:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.57
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.179
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.45
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.90
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.14
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.48
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.88
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.229
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.69
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.37
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.54
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.84
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.23
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.79
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.173
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.149
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.80
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.53
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.21
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.86
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.111
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.168
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.44
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.40
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.124
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.29
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.166
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.133
Mar 24 15:09:00 Kyle ARDAgent [222]: UDPWritePacket error 65 No route to host for -64.168.10.56

There is another post about this about a couple of months ago. The poster figured out that the first number -64 actually could be translated into 192. etc.
and that the computers were not online at the time (laptops etc).
Here is the link..
http://discussions.apple.com/thread.jspa?messageID=2608312&#2608312

Strange System Log Entry

The following sequence keeps repeating every few seconds in the System Log. Does anyone have any ideas as to what it is all about? It appears to be referring to a Python script, but we have not "knowingly" executed any.
Dec 13 13:15:06 host1 com.apple.wikid[28950]: Traceback (most recent call last):
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/bin/twistd", line 21, in <module>
Dec 13 13:15:06 host1 com.apple.wikid[28950]: run()
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/scripts/twistd.py", line 27, in run
Dec 13 13:15:06 host1 com.apple.wikid[28950]: app.run(runApp, ServerOptions)
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/application/app.py", line 379, in run
Dec 13 13:15:06 host1 com.apple.wikid[28950]: runApp(config)
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/scripts/twistd.py", line 23, in runApp
Dec 13 13:15:06 host1 com.apple.wikid[28950]: _SomeApplicationRunner(config).run()
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/application/app.py", line 156, in run
Dec 13 13:15:06 host1 com.apple.wikid[28950]: self.preApplication()
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/scripts/twistdunix.py", line 203, in preApplication
Dec 13 13:15:06 host1 com.apple.wikid[28950]: self.config['prefix'], self.config['nodaemon'])
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/scripts/twistdunix.py", line 113, in startLogging
Dec 13 13:15:06 host1 com.apple.wikid[28950]: logFile = app.getLogFile(logfilename or 'twistd.log')
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/application/app.py", line 410, in getLogFile
Dec 13 13:15:06 host1 com.apple.wikid[28950]: os.path.dirname(logPath))
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/python/logfile.py", line 113, in _init_
Dec 13 13:15:06 host1 com.apple.wikid[28950]: BaseLogFile._init_(self, name, directory, defaultMode)
Dec 13 13:15:06 host1 com.apple.wikid[28950]: File "/usr/share/caldavd/lib/python/twisted/python/logfile.py", line 26, in _init_
Dec 13 13:15:06 host1 com.apple.wikid[28950]: assert os.path.isdir(self.directory)
Dec 13 13:15:06 host1 com.apple.wikid[28950]: AssertionError
Dec 13 13:15:06 host1 com.apple.launchd[1] (com.apple.wikid[28950]): Exited with exit code: 1
Dec 13 13:15:06 host1 com.apple.launchd[1] (com.apple.wikid): Throttling respawn: Will start in 8 seconds

Okay - I also noticed this same issue as propably many others - did little study and found out the reason.
First of all - these should be standard locations, but let's make sure. I found out that wikid keeps it settings in /etc/wikid/wikid.conf - From error messages I checked source of last mention before process ended. Not pasting anything to here, I usually use PHP or C and try to stay away from python but I was able to make something out. Assert is a function that makes a test agains something, if this test's result is true (if I remember my studies right, I rarely use assert) it exits process. Why? Sometimes when programs start they need to make certain checks to avoid crashing - crashing isn't nice..
Anyway, test was for existency of directory where logfile(s) are kept. From same or another source file I also found out about location /etc/wikid, I ofcourse could had checked it from there in the first place, but I liked to follow the code a bit.. There I found file wikid.plist, opened it - a long conf file and finally there it was - logfile(s) are kept in location:
/Library/Logs/wikid
I created this directory and restarted, everything wasn't okay yet, as rights for that directory were incorrect. So I checked com.apple.wikid in LaunchDaemons and found out it runs as user _teamsserver and gid _teamsserver. So I changed rights for that uid and gid and everything was working after that.
Here's what you need to do in terminal to get it working:
#sudo mkdir /Library/Logs/wikid
#sudo chown -R teamsserver:teamsserver /Library/Logs/wikid
Then just restart wikid, there you go. This was my first post and I just created account for this.
Can be marked as SOLVED but 10.5.2 should make sure this directory gets created - either when ever it's missing and wikid is started, or just a empty dir created while upgrading to 10.5.2

Strange repetitive entry in system log

Similar Messages

Maybe you are looking for