Xserve deliver filling up system.log

Just checked my system.log after a hard crash and it seems to be constantly filling up with the following:
Dec 18 15:33:23 xserve deliver[24559]: connect(/var/imap/socket/lmtp) failed: No such file or directory
Dec 18 15:33:23 xserve deliver[24560]: connect(/var/imap/socket/lmtp) failed: No such file or directory
Dec 18 15:33:23 xserve deliver[24561]: connect(/var/imap/socket/lmtp) failed: No such file or directory
Dec 18 15:33:23 xserve deliver[24562]: connect(/var/imap/socket/lmtp) failed: No such file or directory
Dec 18 15:33:23 xserve deliver[24563]: connect(/var/imap/socket/lmtp) failed: No such file or directory
Dec 18 15:33:23 xserve deliver[24564]: connect(/var/imap/socket/lmtp) failed: No such file or directory
Dec 18 15:33:23 xserve deliver[24565]: connect(/var/imap/socket/lmtp) failed: No such file or directory
Dec 18 15:33:23 xserve deliver[24566]: connect(/var/imap/socket/lmtp) failed: No such file or directory
Dec 18 15:33:23 xserve deliver[24567]: connect(/var/imap/socket/lmtp) failed: No such file or directory
Dec 18 15:33:23 xserve deliver[24569]: connect(/var/imap/socket/lmtp) failed: No such file or directory
Since I see the words 'deliver' and 'imap' in there I assume it's mailserver related, however we do not have our xserve's mailserver activated.
Any ideas on what's causing these logs? Ordinarily I wouldn't worry, but it seems to be writing many many lines per second so surely something's not right.
Thanks in advance
Si

This typically happens when the system is trying to send alert messages of some kind. It can happen if you have notifications turned on in the server monitor app, or if you have other tools trying to send system messages.
You can go into your /etc/mail/aliases file and make sure someone is configured to receive mail sent to root (uncomment the line and add the your email address in place of 'you').
Then make sure that mail service on your Xserve (where you're seeing the messages) is turned on and allows mail relay from localhost. Additionally, you can configure mail service to route all mail through your real mailserver. But you don't need to configure or allow inbound mail, since you won't need it.
MacBook Pro Mac OS X (10.4.8)

Similar Messages

Push notification service fills the system log with errors

When I have the push notification service enabled, my system logs become filled with messages such as this:
Sep 8 22:54:54 xserve jabberd/c2s[2175]: [7] [::ffff:192.168.1.100, port=50064] connect
Sep 8 22:54:54 xserve jabberd/c2s[2175]: [7] [::ffff:192.168.1.100, port=50064] disconnect jid=unbound, packets: 0
They occur at a rate of about two every second. What does that message mean and how do I stop it?

When I took a look at push notification, I noticed that it was listening to a different port than what dovecot had been configured to use.(jabberd was set to listen to 5347, while Dovecot (email) was using the standard 5222 port for that open protocol. Not sure what the ichat server is set to use.
Eventually, I did manage to get it working by updating the push notification config to listen to 5222. But it made no real difference because thunderbird and mail.app prefer imap updatings instead of push notification. So I turned it off.
Not sure if this is of any help to you.
Message was edited by: JFMezei

Safari is filling my system log

Safari 8, OS 10.10.1 on a Retina MBP, with all Safari extensions disabled.
My system log is filled with literally thousands of nsurlstoraged errors like the ones below. The problem exists in system log files going back a week, (i.e., 3 days before I updated to 10.10.1). I have reset Safari (Clear History and website data), rebooted, etc, and the problem persists.
Watching the system log in real time, via tail, shows that a burst of these nsurlstoraged errors appear every time I visit a new page in Safari. The errors stop after a second or so, until I visit a new page.
I have checked for bogus launch daemons, launch agents, etc, in /Library and ~/Library, and there are no unexpected files present there. Running out of ideas.
Nov 20 15:47:59 Jays-rMBP.local nsurlstoraged[276]: writeDBwithCachedResponse-ERROR: task-mgr=com.apple.WebKit.Networking-write (_dbWriteConnection=0x7f8372322640) insert SQL stmnt. is nil for item: http://cdn.sstatic.net/img/share-sprite-new.svg?v=7966d6d82b78[stackexchange.com ]
Nov 20 15:47:59 Jays-rMBP.local nsurlstoraged[276]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=COMMIT;, error-code=1, error-message=cannot commit - no transaction is active
Nov 20 15:47:59 Jays-rMBP.local nsurlstoraged[276]: writeDBwithCachedResponse-ERROR: task-mgr=com.apple.WebKit.Networking-write (_dbWriteConnection=0x7f8372322640) insert SQL stmnt. is nil for item: http://cdn.sstatic.net/Img/mini-hero-bg.png?v=7f269bbbdb22[stackexchange.com]
Nov 20 15:47:59 Jays-rMBP.local nsurlstoraged[276]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=COMMIT;, error-code=1, error-message=cannot commit - no transaction is active
Nov 20 15:47:59 Jays-rMBP.local nsurlstoraged[276]: writeDBwithCachedResponse-ERROR: task-mgr=com.apple.WebKit.Networking-write (_dbWriteConnection=0x7f8372322640) insert SQL stmnt. is nil for item: https://discussions.apple.com/6.0.3.0/themes/apple_0.7.0/img/bg-body.png[apple.c om]
Nov 20 15:47:59 Jays-rMBP.local nsurlstoraged[276]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=COMMIT;, error-code=1, error-message=cannot commit - no transaction is active
Nov 20 15:47:59 Jays-rMBP.local nsurlstoraged[276]: writeDBwithCachedResponse-ERROR: task-mgr=com.apple.WebKit.Networking-write (_dbWriteConnection=0x7f8372322640) insert SQL stmnt. is nil for item: https://www.apple.com/ac/globalheader/1.0/images/lang/en-US/tab_store.svg[apple. com]
Nov 20 15:47:59 Jays-rMBP.local nsurlstoraged[276]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=COMMIT;, error-code=1, error-message=cannot commit - no transaction is active
Nov 20 15:48:02 Jays-rMBP.local nsurlstoraged[276]: writeDBwithCachedResponse-ERROR: task-mgr=Safari-write (_dbWriteConnection=0x7f8372016740) insert SQL stmnt. is nil for item: https://dalk4zrp4jp3q.cloudfront.net/images/mac_YFVkNF/ustv_g.png
Nov 20 15:48:02 Jays-rMBP.local nsurlstoraged[276]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=COMMIT;, error-code=1, error-message=cannot commit - no transaction is active
Nov 20 15:48:02 Jays-rMBP.local nsurlstoraged[276]: writeDBwithCachedResponse-ERROR: task-mgr=Safari-write (_dbWriteConnection=0x7f8372016740) insert SQL stmnt. is nil for item: https://dalk4zrp4jp3q.cloudfront.net/images/mac_YFVkNF/wiki_icon_2x.png
Nov 20 15:48:02 Jays-rMBP.local nsurlstoraged[276]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=COMMIT;, error-code=1, error-message=cannot commit - no transaction is active

Thanks very much for the suggestion. I did a safe boot, followed by regular boot. As soon as I launched Safari, the log filled up with 249 nsurlstoraged errors. Here are the first few:
Nov 20 22:01:04 Jays-rMBP.local nsurlstoraged[286]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=PRAGMA auto_vacuum = 2;, error-code=11, error-message=database disk image is malformed
Nov 20 22:01:04 Jays-rMBP.local nsurlstoraged[286]: ERROR: NSURLStorageURLCacheDB _setDBSchema: _dbWriteConnection=0x7f8fe843a720 DB=/Users/jaym/Library/Caches/com.apple.Safari/Cache.db pragma auto vacuum - database disk image is malformed. ErrCode: 11.
Nov 20 22:01:04 Jays-rMBP.local storeaccountd[295]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fe674972b20> connection from pid 561 with interface <AccountServiceInterface: 0x7fe674934b50> (PID 561)
Nov 20 22:01:04 Jays-rMBP com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The _DirtyJetsamMemoryLimit key is not available on this platform.
Nov 20 22:01:05 --- last message repeated 1 time ---
Nov 20 22:01:05 Jays-rMBP.local nsurlstoraged[286]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=PRAGMA auto_vacuum = 2;, error-code=11, error-message=database disk image is malformed
Nov 20 22:01:05 --- last message repeated 1 time ---
Nov 20 22:01:05 Jays-rMBP.local nsurlstoraged[286]: ERROR: NSURLStorageURLCacheDB _setDBSchema: _dbWriteConnection=0x7f8fea205730 DB=/Users/jaym/Library/Caches/com.apple.Safari/Cache.db pragma auto vacuum - database disk image is malformed. ErrCode: 11.
Nov 20 22:01:05 Jays-rMBP.local nsurlstoraged[286]: ERROR: NSURLStorageURLCacheDB _setDBSchema: _dbWriteConnection=0x7f8fea111a30 DB=/Users/jaym/Library/Caches/com.apple.Safari/Cache.db pragma auto vacuum - database disk image is malformed. ErrCode: 11.
Nov 20 22:01:05 Jays-rMBP.local locationd[217]: Couldn't find a requirement string for masquerading client /System/Library/PrivateFrameworks/Parsec.framework
Nov 20 22:01:05 Jays-rMBP.local locationd[217]: could not get apple languages array, assuming english
Nov 20 22:01:05 Jays-rMBP com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The _DirtyJetsamMemoryLimit key is not available on this platform.
Nov 20 22:01:07 Jays-rMBP.local nsurlstoraged[286]: INIT-FAIL: _sqlInsertStmtResponse=0x0, DB=/Users/jaym/Library/Caches/com.apple.Safari/Cache.db, error-code:11.
Nov 20 22:01:07 Jays-rMBP.local nsurlstoraged[286]: writeDBwithCachedResponse-ERROR: task-mgr=Safari-write (_dbWriteConnection=0x7f8fe860aa70) insert SQL stmnt. is nil for item: https://api.smoot.apple.com/bag?locale=en-US&key=andromeda
Nov 20 22:01:07 Jays-rMBP.local nsurlstoraged[286]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=COMMIT;, error-code=1, error-message=cannot commit - no transaction is active
Nov 20 22:01:07 Jays-rMBP.local nsurlstoraged[286]: writeDBwithCachedResponse-ERROR: task-mgr=Safari-write (_dbWriteConnection=0x7f8fe860aa70) insert SQL stmnt. is nil for item: https://dalk4zrp4jp3q.cloudfront.net/images/mac_YFVkNF/movie_placeholder_2x.png
Nov 20 22:01:07 Jays-rMBP.local nsurlstoraged[286]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=COMMIT;, error-code=1, error-message=cannot commit - no transaction is active
Nov 20 22:01:07 Jays-rMBP.local nsurlstoraged[286]: writeDBwithCachedResponse-ERROR: task-mgr=Safari-write (_dbWriteConnection=0x7f8fe860aa70) insert SQL stmnt. is nil for item: https://init.itunes.apple.com/WebObjects/MZInit.woa/wa/signSapSetupCert
Nov 20 22:01:07 Jays-rMBP.local nsurlstoraged[286]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=COMMIT;, error-code=1, error-message=cannot commit - no transaction is active
Nov 20 22:01:07 Jays-rMBP.local nsurlstoraged[286]: writeDBwithCachedResponse-ERROR: task-mgr=Safari-write (_dbWriteConnection=0x7f8fe860aa70) insert SQL stmnt. is nil for item: https://dalk4zrp4jp3q.cloudfront.net/images/mac_YFVkNF/appstore_icon_small_2x.pn g
Nov 20 22:01:07 Jays-rMBP.local nsurlstoraged[286]: Error: execSQLStatement:onConnection:toCompletionWithRetry - SQL=COMMIT;, error-code=1, error-message=cannot commit - no transaction is active

Silverlight fills up system.log file

In order to watch the NBC Olympics, I had to install Silverlight. I had hesitation and now know why. While the player seems to play just fine and all, it is kicking massive error messages to the system.log file. It fills many megabytes and therefore the daily syslog rotation runs bzip2 for a long time each night.
Here is a sampling from my system.log file, using Safari 4.0.4 on OS-X 10.6.2.
Feb 22 01:33:28 KR-iMac com.apple.WebKit.PluginAgent[593]: * set a breakpoint in mallocerrorbreak to debug
Feb 22 01:33:28 KR-iMac WebKitPluginHost[1002]: WebKitPluginHost(1002,0xb071b000) malloc: * error for object 0x1980bf94: pointer being freed was not allocated\n* set a breakpoint in mallocerrorbreak to debug
Feb 22 01:33:28 KR-iMac WebKitPluginHost[1002]: WebKitPluginHost(1002,0xb071b000) malloc: * error for object 0x5ef8e14: pointer being freed was not allocated\n* set a breakpoint in mallocerrorbreak to debug
Feb 22 01:33:28 KR-iMac com.apple.WebKit.PluginAgent[593]: WebKitPluginHost(1002,0xb071b000) malloc: * error for object 0x1980bf94: pointer being freed was not allocated
Feb 22 01:33:28 KR-iMac com.apple.WebKit.PluginAgent[593]: * set a breakpoint in mallocerrorbreak to debug
Feb 22 01:33:28 KR-iMac com.apple.WebKit.PluginAgent[593]: WebKitPluginHost(1002,0xb071b000) malloc: * error for object 0x5ef8e14: pointer being freed was not allocated
Feb 22 01:33:28 KR-iMac com.apple.WebKit.PluginAgent[593]: * set a breakpoint in mallocerrorbreak to debug
Feb 22 01:33:28 KR-iMac com.apple.WebKit.PluginAgent[593]: * process 593 exceeded 500 log message per second limit - remaining messages this second discarded *
Feb 22 01:33:28 KR-iMac WebKitPluginHost[1002]: WebKitPluginHost(1002,0xb071b000) malloc: * error for object 0x1980bf94: pointer being freed was not allocated\n* set a breakpoint in mallocerrorbreak to debug
Feb 22 01:33:28 KR-iMac WebKitPluginHost[1002]: WebKitPluginHost(1002,0xb071b000) malloc: * error for object 0x5ef8e14: pointer being freed was not allocated\n* set a breakpoint in mallocerrorbreak to debug
Notice it exceeds over 500 messages a second. Anyway to mute these messages???

The problem with just deleting the file, is two fold.
First, the system needs this file to continue to post system messages. If you delete it, or just trash it, the system will just continue to add to the trashed file using the open file pointers, or simply create a new one.
Second, Silverlight will continue to generate messages, and ultimately still go into the system.log. Deleting the file is not such a good idea while the operating system is still using it.
I recommend doing the following to clear the file without deleting it:
You'll need to Enable the root user on your computer if you haven't yet. Search other threads for how to do this on your version of OS-X.
In Terminal, log in as root.
username$ sudo -i
Change to the /var/log folder.
root# cd /var/log
Use the truncate function to simply zero out the file.
root# >system.log
You'll need to do this everyday, after running Silverlight, hopefully BEFORE the daily log rotating cron scripts try to rotate the logs and perform a bzip compression of the file (which will tax your system for a few hours). You may want to find any log files ending in .bz2 and remove those. You can delete those, as they are just archives of old system log files and are not used any more.

Flashupdater filling system.log with spew

Has anyone else noticed that flashupdater is filling their system.log with spew? This is happening on systems with and without flash installed. Sign, yet another blunder...

Linc Davis wrote:
That's the Flash updater included in Mac OS 10.7.4. It doesn't work on a case-sensitive boot volume, which is what you have.
com.apple.flashupdat...: Apple Support Communities
Correct. See this post: https://discussions.apple.com/thread/3952378?tstart=0
and change your com.apple.flashupdater.plist file. That should take care of it.

System Log file filled with arp message from teamed nics

Hello,
We are running a Win2k3 server with dual nics teamed to one IP address. All of our Mac's system logs are being filled with the following message:
Mar 28 12:48:58 Son-of-Spacedog kernel[0]: arp: 192.168.200.50 moved from 00:04:23:b9:00:4a to 00:04:23:b9:00:4b on en0
This is repeated over and over. Is there any way to get the Mac's to stop generating this message? Is the fix for this on the server side or on the Mac side? From what I have seen online in other forums, this started happening with Panther.

There are actually several different types of NIC Teaming Modes:
Adapter Fault Tolerance (AFT) - provides automatic redundancy for a server's network connection. If the primary adapter fails, the secondary adapter takes over. Adapter Fault Tolerance supports two to eight adapters per team. This teaming mode works with any hub or switch, and all team members must be connected to the same device.
Switch Fault Tolerance (SFT) - provides a failover relationship between two adapters when each adapter is connected to a separate switch. Switch Fault Tolerance supports two adapters per team. This feature works with any switch. Spanning Tree Protocol (STP) must be enabled when you create a team in SFT mode.
Adaptive Load Balancing (ALB) - provides load balancing for transmission traffic and adapter fault tolerance. You can also enable or disable receive load balancing (RLB) in ALB teams. This teaming mode works with any switch.
Fast EtherChannel/Link Aggregation - provides increased transmission and reception throughput in a team of two to eight adapters. This mode also includes adapter fault tolerance and load balancing (only routed protocols). This requires a switch with Link Aggregation or FEC capability.
Gigabit EtherChannel/Link Aggregation - is the gigabit extension of the FEC/Link Aggregation/802.3ad: static mode. All team members must operate at gigabit speed.
IEEE 802.3ad: dynamic mode - creates one or more teams using dynamic Link Aggregation with same-speed or mixed-speed adapters. Like the static Link Aggregation modes, Dynamic 802.3ad teams increase transmission and reception throughput and provide fault tolerance. This mode requires a switch that fully supports the IEEE 802.3ad standard.
Now, most likely, somewhere on the network a server is configured for ALB or AFT, and these are the most common methods of NIC teaming (Sadly, the XServes do not). They also do not require any certain type of switch, but they do require STP (Spanning Tree Protocol) to be turned off to function most effectively, or you will see errors on the network like the ones you are seeing in your log. Most managed switches come with STP turned on by default, so you will need to check ALL switches (as the errors will cascade throughout the network) to see if it STP is turned on. Most people do not use STP any more (it basically allows ports on one switch to appear as on another switch), so see if you can turn it off. That should stop the error messages.
-MacBoy in SLC
PowerMac G5 Dual 2.0 GHz Mac OS X (10.4.6)

System.log 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 filling with error messages

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

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

System.log 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

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

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 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".

Cube compression filling up the system logs

Hi,
I reloaded the inventory cube with 2LIS_03_BF (init with data transfer) with 46million records (in a single request). When I try to compress the request without the marker update BX has already been compressed with the marker update) , the system logs are getting filled up and the production system is freezing up.
Is there any solution that makes the compression job take lesser time and generate less logs? At this time, we are not looking in to dropping the data and reloading in smaller chunks, cos that will take another 2days to reload the 46mil records.
Thanks for any suggestions,
Ajax.

Hi Ajax,
We had a similar issue early last yr. Compression uses a lot of temp spaces and fills up the logs . You can ask your basis team to help you by increasing the MAX_LOGS parameter temporarily to complete your compression. As a last resort you can also ask them to involve secondary logs or setting the logs to "unlimited" value and rerun the compression job .However pls note that this is limited by the filesystem size.
Hope it helps .
Thnks
Ram

System.log files filling up in 10.6?

Something is filling up my system log files, to the point that console.app will only show the last half hour of each file. It looks like something is trying to escape its sandbox, but I'm not exactly sure what... I'm getting MANY repeated messages that look like:
Feb 3 00:29:57 Brians-mini sandboxd[16]: syslogd(15) deny file-read-data /private/var/log/asl/StoreData
Feb 3 00:29:57 Brians-mini sandboxd[16]: syslogd(15) deny mach-task-name
Feb 3 00:29:59: --- last message repeated 1 time ---
Feb 3 00:29:57 Brians-mini sandboxd[16]: * process 16 exceeded 500 log message per second limit - remaining messages this second discarded *
Feb 3 00:29:57 Brians-mini sandboxd[16]: syslogd(15) deny mach-task-name
has anyone seen this? (And does this belong in a different forum?)

It sounds like someone may be trying to connect to your computer. When things are repeatedly denied, especially task-opening commands, it is usually suspected that something is trying to get in. This may be malicious, or may not be, depending on how you connect to the Internet. If you share a connection at home or even between residencies (check with your ISP if you're not sure), it can be normal. See if it still happens after you physically disconnect the network. Also, make sure to disconnect peripherals just to make sure they aren't causing any of the issues.

Huge system.log file filled with over a million messages about NSATSTypeset

Hi,
I just happened to notice the system.log file on my MacBook Pro laptop was absolutely huge - over 1.2 GBytes in just one day. Almost all of it is messages like this:
Mar 31 12:26:23 macbook quicklookd[228]: <NSATSTypesetter: 0x146b40>: Exception * table 0x1473caa0 has block 0x147b3040 rather than 0x147b4850 at index 7573 raised during typesetting layout manager <NSLayoutManager: 0x124140>\n 1 containers, text backing has 16461 characters\n selected character range {16461, 0} affinity: downstream granularity: character\n marked character range {16461, 0}\n Currentl
y holding 16461 glyphs.\n Glyph tree contents: 16461 characters, 16461 glyphs, 4 nodes, 128 node bytes, 16384 storage bytes, 16512 total bytes, 1.00 bytes per character, 1.00 bytes per glyph\n Layout tree contents: 16461 characters, 16461 glyphs, 7573 laid glyphs, 207 laid line fragments, 3 nodes, 96 node bytes, 13656 storage bytes, 13752 total bytes, 0.84 bytes per character, 0.84 bytes per glyph, 36.58 laid glyphs per laid line fragment, 66.43 bytes per laid line fragment\n, glyph range {7573 0}. Ignoring...
and there are over 1.3 million of these messages!!!! There is a tiny bit of variation in some of the numbers (but not all). That is just a little bit more than the total number of files I have on the hard drive in the laptop, so it would appear that the quicklookd is doing something to each and every file on the computer. Any idea why all of a sudden these messages appear and why so many. I only have about 7 versions of the system.log files and none of them are even close to this big, but the one one thing I did do today that I have not in a few weeks is reboot my laptop because of another problem with the laptop screen not waking this morning from being put to sleep last night (was just black but computer was running and could login to it from another computer in the LAN it is attached).
Any ideas why this is happening, or is this something that always happens on a reboot/boot rather than waking from sleep. Why would the quicklookd be printing out so many of these messages that are almost exactly alike???
I have only had this MacBook for a few weeks, so don't have a good feel for what is normal and what isn't yet.
THanks...
-Bob

Bob,
Thanks for your further thoughts and the additional information. My guess is that Quick Look does its file processing independently of whether or not or how recently the computer has been rebooted. The NSATSTypesetter messages filling up the log file are almost certainly error messages and should not occur with normal operation of Quick Look. I suspect that your reboot doesn't directly have anything to do with this problem. (It might have indirectly contributed in the sense that either whatever caused the need for the reboot or the reboot process itself corrupted a file, which in turn caused Quick Look to fail and generate all those error messages in the log file.)
In the meantime I may have a solution for this problem. This morning I rebooted in single user mode and ran AppleJack in manual mode so that I could tell it to clean up all user cache files. (I'd previously downloaded AppleJack application from http://applejack.sourceforge.net/ . To boot in single user mode hold command and s keys at startup chime. ... Run the five AppleJack maintenance tasks in order. The third task will give you the option to enter numbers of users whose cache files will be cleaned. Do this cache cleaning for all users.) In the six hours since I ran AppleJack I've seen exactly two NSATSTypesetter error messages in /var/log/system.log . This compares with hundreds of thousands in the same period yesterday. I just set an iCal alarm to remind me to report back to this discussion thread in two weeks on this issue.
Best,
Chris.
PS: Above you mention 7 log files. Are the older ones of the form system.log.0.bz2 ? If so they have been compressed. Just because they are small doesn't necessarily mean there are not a lot of nearly identical error messages. Uncompress to check. I haven't tried this because large files are very inconvenient to work with on my old iBook.

Xserve deliver filling up system.log

Similar Messages

Maybe you are looking for