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.

Similar Messages

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???

Weird system.log entry

Hi,
since a few days I see appr. 5 minutes after boot thsi system.log entry:
Dec 26 17:03:52 Gullivers-Computer configd[52]: target=enable-network: disabled
Dec 26 17:08:54 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:20 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:33 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:42 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:42 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:42 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:42 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:42 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:44 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:44 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:44 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:44 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:46 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:46 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:46 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:46 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:48 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:48 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:48 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:58 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:59 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:59 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:09:59 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:10:06 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:10:07 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:10:07 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:10:07 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:10:33 Gullivers-Computer kernel[0]: disk0s5: ioctl('
Dec 26 17:18:48 Gullivers-Computer KernelEventAgent[46]: tid 00000000 received VQ_LOWDISK event (4)
Does this point to an upcoming hard disk failure? Or what else could that mean? TechTool pro does not show any errors.
Thanks in advance!

What's the S.M.A.R.T. status on the drive? You can check it on Disk Utility (click on the device, not the volume), or you can use a freeware tool such as [SMARTreporter|http://www.versiontracker.com/dyn/moreinfo/macosx/23232].
And you have probably run the regular Repair Disk/Repair Permissions/etc. routine on it, right?

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

Help decoding System.log entry

Hello,
Does anyone know what this entry in the System log means?
Jul 23 14:40:19 www fseventsd[43]: failed to make the directory /private/tmp/278/E/.fseventsd (1/Operation not permitted)
Jul 23 14:40:59 www fseventsd[43]: scan_old: bailing out because device mounted @ /private/tmp/278/E has dls 0x0 and dls->fci 0x0
Does it mean I should do anything ... ?
Thanks in advance for the help.

Probably not. fseventsd is the daemon responsible for reading filesystem events from a special device file in /dev/ (basically, from the kernel), and writing those events to log files stored in directories named .fseventsd.
Each filesystem volume that exists and has events associated with it will have a .fseventd directory at its root. For example, take a look in your / directory and you'll see one (to look inside, you'll need to be root or use sudo).
The whole reason for the daemon's existence is so that any other application on the Mac can take advantage of filesystem events without having to read directly from the kernel. Instead, they read from ordinary log files.
What that error is saying is that you have some external disk or disk image (i.e. volume) attaching itself to a directory in /private/tmp, and fseventsd is having problems setting up the proper log file directory in order to make filesystem events work for that volume. The "1/Operation not permitted" message is a standard error code, "1" being the numeric code and "operation not permitted" being the corresponding string code. This error typically means that the underlying filesystem (in this case, your mystery volume) is purposefully denying the creation of the object in a way _other than_ by permissions. For example, there could be a file flag set making the root of the filesystem immutable.
To understand more, it would be helpful to know what is attaching itself to that area in your tmp directory. Regardless, I don't think the errors are much to worry about...

Worrying system log entry

Hi guys,
I've been having a look through the system log and have have seen the following message come up a few times:
jnl: journal start/end pointers reset!
What does this mean, and should I be worried?
Thanks

Thanks for the input guys, but I think I've tracked down the cause.
It's my iPod.
I happened to have the console open when I connected my iPod, and lo and behold the following appeared in the log:
Feb 6 08:05:11 Poppy kernel[0]: jnl: journal start/end pointers reset! (jnl 0x1f78d7c; s 0x205800 e 0x205800)
Feb 6 08:05:24 Poppy kernel[0]: jnl: close: flushing the buffer cache (start 0x261000 end 0x265200)
The iPod was set to automatically sync and eject (ie. NOT enabled for disk use) These entries are for the system mounting and unmounting the iPod.
I re-enabled the iPod for disk use. After this, I noticed I had a couple of files still on the iPod from when it'd previously been used as a disk. I deleted those, unmounted the disk and then set it back to auto-sync in iTunes, and now the journal start/end pointers entry doesn't appear in the console.
Hopefully this will come in handy for someone else.
Thanks for your interest
Darren

RV325 System Log Entries - Kernel - kernel: wrong ip[0],not_list[0]

Hello,
I have a RV325 Router. Entries in the System Log are mysterious to me and all my search results and reading are not relevant.
The Event-Type is - "Kernel", and the Message is "kernel: wrong ip[0],not_list[0]"
The Log entries occur every few minutes.
Does anyone know what this log entry signifies?
Also, does anyone know how to get an answer to any question from Cisco?
Thanks,
Michael Downs

Hello
yes, there are several existing discussions about same syslog message, like here, here or here, but neither of discussions points to solution.
If you device is still under warranty I would suggest you to open service request to Cisco Small Business Support Center to make this issue fixed permanently.

RV325 System Log Entries - Kernel - kernel: The MAC table overflow. (Neighbour table overflow.)

Hello,
I have a RV325 Router. Entries in the System Log are repeated over and over.
The messages are:
2015-01-20, 04:11:59
Kernel
kernel: The MAC table overflow. (Neighbour table overflow.)
2015-01-20, 04:11:59
Kernel
last message repeated 8 times
2015-01-20, 05:52:19
Kernel
kernel: The MAC table overflow. (Neighbour table overflow.)
Packet traces point to thousands of ARP packets coming from the ISP to my WAN port. Most of the ARP packet sources/destinations are not even close to my ISP DHCP assigned IP.

Hi, Mark.
I'm not an Apache guru, but you may have two different issues here, depending on when the
kernel[0]: file: table is full
message is time-stamped relative to when you issue the
sudo apachectl start command.
1. Looking at the results of this Google search and some others tends to indicate that common causes for httpd could not be started are errors in the /etc/httpd/httpd.conf file.
You might also want to take a look at some of these other Discussions threads and in these "Networking and the Web" Discussion threads.
2. One explanation I've found for kernel[0]: file: table is full is here.
Hope these ideas help.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X

What does these Apple System Log entries mean?

I have been reading the Apple System Log and the following entries have caught my attention. Can someone tell me what they mean?
2011-08-31 12:55:07 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 12:55:08 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 12:55:09 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 12:58:39 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 12:58:54 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 12:59:03 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 12:59:11 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 12:59:21 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 12:59:30 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 12:59:52 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:01:08 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:01:24 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:06:24 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:06:43 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:07:12 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:07:32 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:07:36 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:07:39 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:08:09 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:08:17 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:08:25 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:08:33 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:08:50 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:08:56 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:09:04 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:10:21 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:10:22 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:10:22 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:11:11 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:11:12 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:11:13 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:11:13 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:12:03 -0400 kernel[0]: IOSurface: buffer allocation size is zero
2011-08-31 13:12:07 -0400 kernel[0]: IOSurface: buffer allocation size is zero

I find:
kernel: IOSurface: buffer allocation size is zero
appears a lot when I can barely get control of my iMac 27, with constant whirring disk sounds and also often with Pref Sync Client (even if no sync taking place) and Safari Web Content also frequently.
Other alerts include:
kernel: IOSurface: buffer allocation size is zero
[0x0-0xda0da].com.apple.Safari: DVFreeThread - CFMachPortCreateWithPort hack = 0x182080, fPowerNotifyPort= 0x181910
Imran

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

System log entry

Hey, can anyone tell me if these users have logged into my server and relayed spam mail??
Aug 3 21:57:12 server postfix/smtpd[18064]: warning: 143.244.212.66.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=143.244.212.66.relays.ordb.org type=A: Host not found, try again
Aug 3 21:57:17 server postfix/smtpd[18064]: warning: 174.42.22.216.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=174.42.22.216.relays.ordb.org type=A: Host not found, try again
Aug 3 21:57:29 server postfix/smtpd[18064]: warning: 196.244.32.72.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=196.244.32.72.relays.ordb.org type=A: Host not found, try again
Aug 3 22:04:16 server postfix/smtpd[18251]: warning: 143.244.212.66.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=143.244.212.66.relays.ordb.org type=A: Host not found, try again
Aug 3 22:05:21 server postfix/smtpd[18251]: warning: 142.22.51.72.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=142.22.51.72.relays.ordb.org type=A: Host not found, try again
Aug 3 22:08:00 server postfix/smtpd[18367]: warning: 150.246.54.65.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=150.246.54.65.relays.ordb.org type=A: Host not found, try again
Aug 3 22:08:50 server postfix/smtpd[18367]: warning: 174.21.236.61.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=174.21.236.61.relays.ordb.org type=A: Host not found, try again
Aug 3 22:11:00 server postfix/smtpd[18367]: warning: 244.28.33.81.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=244.28.33.81.relays.ordb.org type=A: Host not found, try again
Aug 3 22:11:51 server postfix/smtpd[18367]: warning: 121.35.53.37: hostname 37.53.35.121.broad.sz.gd.dynamic.163data.com.cn verification failed: Host not found
Aug 3 22:11:52 server postfix/smtpd[18367]: warning: 37.53.35.121.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=37.53.35.121.relays.ordb.org type=A: Host not found, try again
Aug 3 22:16:02 server postfix/smtpd[18579]: warning: 137.106.141.219.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=137.106.141.219.relays.ordb.org type=A: Host not found, try again
Aug 3 22:20:07 server postfix/smtpd[18696]: warning: 136.195.41.211.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=136.195.41.211.relays.ordb.org type=A: Host not found, try again
Aug 3 22:20:19 server postfix/smtpd[18696]: warning: 104.79.74.216.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=104.79.74.216.relays.ordb.org type=A: Host not found, try again
Aug 3 22:21:23 server postfix/smtpd[18696]: warning: 52.73.18.116.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=52.73.18.116.relays.ordb.org type=A: Host not found, try again
Aug 3 22:24:01 server postfix/smtpd[18813]: warning: 179.203.216.63.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=179.203.216.63.relays.ordb.org type=A: Host not found, try again
Aug 3 22:24:26 server postfix/smtpd[18813]: warning: 216.219.30.69.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=216.219.30.69.relays.ordb.org type=A: Host not found, try again
Aug 3 22:28:31 server postfix/smtpd[18949]: warning: 158.22.51.72.relays.ordb.org: RBL lookup error: Host or domain name not found. Name service error for name=158.22.51.72.relays.ordb.org type=A: Host not found, try again

I believe that sbl-xbl.spamhaus.org is being phased out and replaced with zen.spamhaus.org.
I use the following dns-blacklists (in this order - order does matter):
zen.spamhaus.org
bl.spamcop.net
dnsbl.sorbs.net
list.dsbl.org
According to my logs, in the last 2.5 days, zen has blocked 3040 (87.88%), bl has blocked 303 (8.75%), dnsbl has blocked 104 (3%), and list has blocked 12 (.34%).

System log info

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

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

SystemFlippers ? in system log

I was receiving a message in my system.log -
unknown SIGSEGV code O
so.... I followed the techNote
http://kb2.adobe.com/cps/408/kb408562.html
and used the licensing fix too.
it fixed it but left me with a new console>system.log entry when I start Illustrator ( CS4, Mac 10.5.7 intel)
Jul 29 09:56:09 G5 [0x0-0x175175].com.adobe.illustrator[9016]: SystemFlippers: didn't consume all data for DLOG ID 10033 (pBase = 0x5955a00, p = 0x5955a20, pEnd = 0x5955cc6)
( don't be confused with the G5 listed in the error, it's just name of this computer on the network, but it is a MacPro intel)
what is it and what to do?
thx.

Hello
Please implement the latest kernel for your release. See note #19466. The error will not occur with the latest kernel patch.
Regards
Mark

BP_JOB_MODIFY error at system log

Hi,
I am having this recurring log from tcode SM21 which logs hourly. It shows the error message "BP_JOB_MODIFY: Job cannot be modified. Reason: The attempt to modify a job of background processing (by means of function module BP_JOB_MODIFY) failed. The reason for this is described in more detail in a subsequent system log entry." I have also seen about no free server issue for the background processor.
Do you know what's causing the error? Can you help me out?
Thanks,
Jennah

Dear Markus,
Thanx for ur suggestion.but i m getting the next error in the SM21.its only warning or i have to rectify it.
while checking the system log sm21 sys log i m facing error but im not able to get it..plz suggest me..i m pasting here
15:16:32 UP1 005 100 PWC R6 7 > Update module: UMSETZEN_PLANAUFTRAG
15:16:47 UP1 005 100 PWC D0 1 Transaction Canceled 61 034 ( 10000023 00010 )
15:16:47 UP1 005 100 PWC R6 5 Update terminated
15:16:47 UP1 005 100 PWC R6 6 > Update key: 6BD241DDD424F13D8261001635B0CD06
15:16:47 UP1 005 100 PWC R6 7 > Update module: UMSETZEN_PLANAUFTRAG
15:16:47 UP1 005 100 PWC D0 1 Transaction Canceled 61 034 ( 10000024 00010 )
15:16:47 UP1 005 100 PWC R6 5 Update terminated
15:16:47 UP1 005 100 PWC R6 6 > Update key: 6BD241DDD424F1418261001635B0CD06
15:16:47 UP1 005 100 PWC R6 7 > Update module: UMSETZEN_PLANAUFTRAG
15:16:47 UP1 005 100 PWC D0 1 Transaction Canceled 61 034 ( 10000025 00010 )
15:16:47 UP1 005 100 PWC R6 5 Update terminated
15:16:47 UP1 005 100 PWC R6 6 > Update key: 6BD241DDD424F1428261001635B0CD06
15:16:47 UP1 005 100 PWC R6 7 > Update module: UMSETZEN_PLANAUFTRAG
15:16:47 UP1 005 100 PWC D0 1 Transaction Canceled 61 034 ( 10000026 00010 )
15:16:47 UP1 005 100 PWC R6 5 Update terminated
15:16:47 UP1 005 100 PWC R6 6 > Update key: 6BD241DDD424F1438261001635B0CD06
Regard's

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

Repetitive System log entry

Similar Messages

Maybe you are looking for