System Log Not Turning Over

I use a couple of MacBooks and noticed that the system logs were getting very big (>600MB in one case) and that they had not turned over since March. Since I normally put the laptops to sleep (close them) when done for the day, they were not active for the normal daily maintenance at 00:00. I did note that other logs were turned over when I woke the machines in the morning, but not the system log. The daily log showed it running, but not which logs it processed. I did a repair permissions which found nothing and did a few manual "sudo periodic daily"s to no avail.
I finally just left the MacBooks awake overnight and sure enough the system logs were turned over. There is something that a manual "sudo periodic daily" does not catch.
Does anyone know how to force a system log turnover process (other than manually renaming it)? I would not mind setting up a cron job to do that if I knew what to do.
Thanks.

Roger, Apple changed the way the scripts run. The only way to do this is to do what you did or do what I have done. I schedule my macbook to turn on at 11:55pm in the scheduler. Then I set the machine to not shut down or sleep for thirty minutes. This rotates all the log files. The only problem I now have is that the daily out log file is growing. It is now above 335k and I cannot find out how to reset this log. The system log files are set to accumulate and turn over, over a seven day period. To flush them completely you must run the schedule for eight days straight. Also, do not close the display lid to your macbook when allowing he scripts to run.

Similar Messages

I'm from Brazil, I have an iphone 3gs that does not turn over, would you change in any app store or any authorized?I'm from Brazil, I have an iphone 3gs that does not turn over, would you change in any app store or any authorized?

I'm from Brazil, I have an iphone 3gs that does not turn over, would you change in any app store or any authorized?

Have a look at your service options here: Apple - Support - Service Answer Center
Out-of-Warranty Service
If you own an iPhone that is ineligible for warranty service but is eligible for Out-of-Warranty (OOW) Service, Apple will service your iPhone for the Out-of-Warranty Service Fee listed below.
iPhone Model
Out-of-Warranty Service
iPhone 5
R$ 649
iPhone 4S
R$ 549
iPhone 4, iPhone 3GS,
iPhone 3G
R$ 449
Prices applicable for Sao Paulo. Prices may vary by state due to local ICMS tax. All fees are in Brazilian reais and include tax.
Since your phone is out of warranty, you'll have to pay for your device being replaced.

My imac will not turn over, what should I do

my imac will not turn over, what should I do

Just FYI,
You are not addressing Apple here.
People here who help troubleshoot and attempt to correctly answer technical questions in these Apple Support Communities are Apple users just like yourself.
There are two initial things you can try.
An NVRAM reset.
Shut down your Mac.
Locate the following keys on the keyboard: Command (⌘), Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.
After resetting NVRAM or PRAM, you may need to reconfigure your settings for speaker volume, screen resolution, startup disk selection, and time zone information. The logic board battery helps retain NVRAM/PRAM settings when your computer is shut down.
IF this fails to help reboot your iMac, you could try an SMC reset.
Shut down the computer.
Unplug the computer's power cord.
Wait fifteen seconds.
Attach the computer's power cord.
Wait five seconds, then press the power button to turn on the computer.
Check back if neither one of these solves your iMac's issues.

My ipod fell in water and now will not turn over and my warranty is busted, have to pay to repair or pay or they do it?

Help me please, it will not turn on and I do not know what I do!

If it is now dry:
Try:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful that indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar
Apple will exchange your iPod for a refurbished one for this price. They do not fix yours.
Apple - iPod Repair price

Re: Satellite P200 not turn over

Good morning,
I have a problem with a P200, when I lighter, power-led illuminates, HDD flashes and then nothing, black screen, whether the power-led remains fixed, and the burner is turned on him More ...
I removed the battery, tested the SO-DIM, removed the hard drive, but nothing is ...
is the motherboard in your opinion?
ps: sorry for my English translation

Ok, a bit hard to understand, but I think your notebook is not turning on, right?
So you tested a few things already, but I can't give you an exact answer.
All you can do by now is the following:
Remove battery from your notebook and disconnect AC adaptor, wait about 30 minutes and then put battery and AC adaptor back in.

System does not turn off after halt after successful suspend-resume

I have the following problem: when I try to shut down my laptop after it resumed from suspend to ram. It seems to shut down normally until, at the very end, it reaches the system halted part (which you wouldn't even be able to read if the system would actually halt). I'm running an updated system, no testing, on an Dell Latitude E6400. The system shuts down normally if I don't suspend it.
Any ideas? What additional information do you need?

karol wrote:
iamsmrt wrote:It wouldn't accept keyboard input afterwards, not even magic keys.
I meant: turn off via 'sudo init 0' instead of 'sudo halt', not after.
Ok, wasn't sure. Isn't "sudo halt" effectively the same thing? How are they different?

When exporting to html, audio files placed in system do not turn off.

When I place a audio file into keynote and play the presentation via an html export, the audio files don't stop playing. If put the keynote.html on the web the only way i can turn off the audio is to refresh the page. I want the audio to stop playing when I advance to the next slide. Any solutions?

This is how sound works in an html export at the moment, maybe it will be improved in a future update.

Rotate system.log

I noticed today that launchd is not rotating my system.log since I installed Snow Leopard. This may be due to wrong settings (I previously used Anacron and may not have uninstalled it properly). How could I fix it?

Usually log files turned over @ midnight & you should put your 'puter to sleep rather than shut down. Also, don't let your 'puter sleep but only the display in Energy Saver settings.
Best - KM.

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

System won't turn off, restart, hibernate or sleep after Windows 8.1 upgrade

Help, please!!
Two days ago in windows 8 store popped up an update to windows 8.1 for my pc. I am an owner of two notebook PC-s, both Lenovo, G580(which upgraded successfully without any issues, also it has intel inside) and G585(which upgraded without any issues, untill
the set up completed and it booted up, it has AMD)
So the AMD one, Lenovo G585, refuses to shut down, restart, sleep or hibernate, the only way to shut it down is to force it to turn off, meaning i have to press the power button for a couple of seconds. Along with other issues this is the only one i wasn't
able to resolve. I have contacted my Lenovo support and they said there is nothing they can do and that i can only wait for an update... and in the meantime am i supposed to let this windows 8.1 upgrade
mess up my new notebook?
Ok, so i was stupid enough not to run windows 8 backup before i started this update, silly me, thinking what could go wrong, it's not like M$ described this upgrade as something like evolution of the century,
but enough about that, i have tried every possible solution, updated my drivers, run admin cmd and typed powercfg -devicequery wake_armed - it displayed NONE, typed powercfg -lastwake - it displayed wake history count - 0, i tried entering BIOS and checking
if there is anything in there i could possibly change, found nothing, tried disabling hibernate, still nothing, and each time i try putting my pc in one of those states the screen turns off, and it all seems like the pc will any moment and yet nothing it just
stays on for countless hours unless i once again force it to shut down, also when in sleep mode no keys work for waking it up, mouse and keyboard are meaningless, the only button that works is the power button which turns it off completely and then i can turn
it on all the way from the begining, so far at least that makes me happy, but continuing like this i will mess up my PC.
PC specs:
OS - Windows 8.1 x64, came preinstalled Windows 8 x64
Processor: AMD E-300 APU with Radeon HD Graphics 1.30GHz
RAM: 4GB
Microsoft, any solutions to this one?

Last week I put a new hard drive in and loaded Windows 8 instead of Windows 7 (which I was previously using), it is a legit copy I had purchased and downloaded from Microsoft when Windows 8 first came out. I had problems with activation, called Microsoft
and they remotely connected fixing the problem. Sleep Mode worked until it did the 8.1 upgrade.Now the System will not turn off, Sleep or Hibernate. If I go to Sleep or Hibernate, the monitor turns off, hard drive turns off, but the fans are still
running. Try to wake up with mouse and nothing happens, have to hit the restart button. If I try to shut down, it does the same thing, I can only shut down by holding the button. I have tried everything suggested here, nothing has worked.
I would reload, but don't want to have to go through the problem of activating again. The system32>sfc /scannow found nothing wrong, network adapter is not allowed to wake the computer, sharing turned off, and disabled the hybrid-shutdown-feature.
Computer has been scanned and re-scanned, not infections. Video driver was re-installed. I have checked all settings in BIOS.
I was hoping that someone has found a solution to this problem.
Intel Pentium D CPU 3.73GHz
8.00GB RAM
NVIDA GeForce 9800 GT x 2 (SLI)
64-bit Windows 8.1 Pro with Media Center
No pen or touch input

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.

USB pen drive mounts not seen in system.log. Why?

Any idea why USB pen drive mounts are not loogged in system.log? A WD Paasport drive mount shows up in system.log. Any idea why this is the case and how it can tracked/logged?
It would be nice to have a record of any externals that are being mounted on an OS X client by a user.
MacMini Mac OS X (10.4.9)

Ok, that's it. I read a few posts in the "...SuperDrive won't accept my CD.." section. and it seems some people are just swapping optical drives like mad, ready to accept that the kit is crap, and "...oh, well, I sure hope this one works better...".
But one guy had the brains to have a look inside. Turns out dust had accumulated in the drive and on the connectors, and when he cleaned them, and unplugged and replugged them, it worked fine. So that's what I did. Took it out and put it back in. Amazing the stuff I cleared out! I also un- and re-plugged the power cable and the data ribbon at the mutha board and bingo!. We have disk, and I can breathe again.
Recommend to others they pretend they've bought a new drive, do a remove and reinstall and be very fastidious. You may not need a new one after all. I just love it that stuff can still be FIXED!
Thanks to Lou and all of you who share your experiences. It's like my brain is suddenly soooo huge...

Mds: (Error) Import over and over in system.log?

I am currently watching my system.log file fill up with stuff like this:
Feb 26 09:43:54 Zeus mds[47]: (Error) Import: importer:0x861800 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Feb 26 09:44:24: --- last message repeated 7 times ---
Feb 26 09:44:26 Zeus mds[47]: (Error) Import: importer:0x861800 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Feb 26 09:44:56: --- last message repeated 7 times ---
Feb 26 09:44:58 Zeus mds[47]: (Error) Import: importer:0x861800 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Feb 26 09:45:28: --- last message repeated 7 times ---
As you can see from the time intervals, it's happening a lot, over and over. I found some references to an error like this supposedly being caused by Time Machine, but I have Time Machine turned off. (Don't like it.)
Anyone know what this is? Looking back through the log, I'm seeing that it has happened multiple times in the past, for anywhere from 15 minutes at a time to over an hour.

This looks like a permission problem to me.
Can you execute the following commands in a terminal and post them?
(Only the actual 'ls -al xxx' lines, the rest is shell prompt and result)
Regards
Patrick
[18:31 root@pm1] ls -lad /var/tmp
drwxrwxrwt 5 root wheel 204 Feb 26 18:26 /var/tmp
[18:31 root@pm1] ls -lad /var/tmp/mds
drwxrwxrwt 6 root wheel 204 Feb 26 18:20 /var/tmp/mds
[18:31 root@pm1] ls -lad /var/tmp/mds/
502/ 65/ messages/ system/
[18:31 root@pm1] ls -lad /var/tmp/mds/502
drwx------ 2 mau wheel 170 Feb 26 18:20 /var/tmp/mds/502

JCOerror: This system does not let you log on using a password

Hi,
"JCOerror: This system does not let you log on using a password"
This is the error message I get from MII tries to connect to the Production ECC using my credentials to perform a BAPI call.
These credentials work fine interactively (using the SAP GUI) and for BAPI calls from MII on SAP Development instances.
I can interpret this message in two ways:
- My login can not log on using password (though I can interactively)
- The server does not allow logging on using password only. (It might require to pre-authorize the connecting server as well).
I guess my question can be if this error requires adding additional rights to my login for the production environment, or if this is a global SAP setup for this system? Or something else?
In either way, what is required to have this work?
Thanks.

Hi,
Kindly try the following options.
Try executing the BAPI seperately in se37, using your login credentials.
Check whether RFC is enabled for the BAPI.
Check whether the SAP server is details are furnished correctly in "SAP Server"(available under "Data Services") editor.
We can ensure this by checking the connection status link in xMII.(Link is available under "Data Services").
If connection status is "Running" then SAP server setting configuration is fine. Else it is not configured properly.
Try executing the BAPI in BLS(Business Logic Services) using JCO connector.
I believe if any one of these scenarios fail then "Proxy Error" might thrown.
Thanks
Rajesh Sivaprakasam

This system does not let you log on using a password

hi all, i am very new to sap basis. i have changed the below profile parameters in RZ10.
login/min_password_length=3
login/min_password_lowercase=1
login/min_password_uppercase=1
login/min_password_digits=2
login/min_password_specials=1
after changing values i restarted the Instance. But the problem is when i am trying to login to the system it is showing an error message : "This system does not let you log on using a password". I know why this error occurs...
but how to resolve this error? plz Help.
Thanks in advance

login/min_password_length=3
login/min_password_lowercase=1
login/min_password_uppercase=1
login/min_password_digits=2
login/min_password_specials=1
The correct parameter for Min password Lenght is login/min_password_lng.
You can change this at OS level restart and see how it goes...
Regards
Juan

System Log Not Turning Over

Similar Messages

Maybe you are looking for