Error in system log

HI all,
this is not a security query, but I need help in this regard.
Following error msg i showing in system log. I'm getting this error whenever i'm trying to read the Job in SM37. And in some cases I'm unable to see the spool list which is generated by the bg jobs. what coul be the reason?
<b>> Error reading job log JOBLGX15165600X64603
Error 2 for write/read access to a file. File = /usr/sap/PRD/SYS/global/999JOBLG/0001X15165600X64603
BP_JOBLOG_SHOW: Failed to display jobs. Reason:</b>

Thanks Jose
Porblem is solved.
/sapmnt/PRD/global and profile are not mounted on that server.
Thnak u so much for ur cooperation.
Regards,
Raja

Similar Messages

Error in system logs of the abap engine

Hello All,
I got a incident for "error in system logs of the abap engine".When i checked in SM21,
13:50:18 BTC 024 001 SETUPADMIN SM59 Q0 W
SETUPADMIN deletes RFC destination
0000000000011DECBA9958E212E09B2C
05782 Background Processor No. 024 SETUPADMIN
1 SM59 /ITSC/DSA_PERIODICAL T Transaction Problem STSK
A destination has been deleted in SM59, destination
maintenance of RFC.
Problems can occur if this destination is still used in existing
ABAP
I checked in sm37,the job /ITSAM/HEALTHCHECK which
runs under the program /ITSC/DSA_PERIODICAL with frequency
10 mins is in finished state.
Kindly help me out, why this logs is always written in sm21 even if
the job got finished .
Thanks & Regards,
Harshavardhan

i have the same error but my first select is
SELECT QMNUM QMTXT QMDAT AUFNR OBJNR QMNAM QMART BTPLN IWERK BEBER INGRP EQUNR SERIALNR MATNR
        INTO TABLE GT_VIQMEL
        FROM VIQMEL
        WHERE QMNUM IN S_QMNUM .
please tell me how to solve this error when i run 24000 raw this select dump.
ASAP
thanks
Eman elgammal.

Mcxd.app reports errors in system.log

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

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

Errors in system log?

OK, so I'm relatively new to Mac OS X, but that's on the back of some 20 years of working with UNIX, so I'm well placed to handle Mac OS X.... or so I thought!
In fact, compared to generic UNIX systems, there's so much added to Mac OS X that it might as well be a totally different system.
Anyway, I've got this iMac G5 (iSight) 2.1 GHz, which came with 10.4.2 installed, and which I've fully updated (using Software Update) to 10.4.3. After the update, a few glitches have revealed themselves - like the Dock will sometimes just apparently lock up - clicking back on the desktop seems to be a fairly reliable way of unfeezing the Dock, but it's annoying nonetheless.
The glitches prompted me to look further into the system, and in particular, when I look at the system log, via Console, right after rebooting, I see some messages there that may or may not be of significance:
- SystemStarter[879]: authentication service (887) did not complete successfully
- localhost kernel[0]: AppleU3: WARNING: platform-chip-fault expected, but not found
- launchd: Server 0 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[65]: exited abnormally: Hangup
I must admit, the second of those seems a bit odd to me!
But, can anyone tell me how 'bad' these errors are? Do I need to delve further into their causes, or do Aqua and Darwin handle such 'events' quite gracefully (which I'll accept is more than possible)?
Whilst I was talking with one of the AppleCare guys earlier today, I tried to ask him about these syslog messages, but the response I got was that I should consult http://www.apple.com/support/mac101 !!! Right, very helpful!
AppleCare is great, I think, for users who simply need a bit of hand-holding and instruction in how to use their Mac. That's fine, as long as everything is working as it should - but when we're more advanced as users than that, and we have a more technical issue to resolve, whereand how are we supposed to get help from even more knowledgable support personnel?
Or are these discussion forums the best bet?
Nigel

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

Errors in system.log since leopard upgrade

I have a mac mini core duo 1.83, with 2gb ram.
It was running Tiger until I upgraded it to Leopard about October 27th.
I used the archive and install installation method.
It has been running fine. The only "glitch" I have noticed is a very occasional
pause in music playing in iTunes.
While investigating the cause of that, I realised that the system.log file is very large, and there are many many instances of this error in it.
Dec 10 15:42:11 macmini Unknown[36394]: Error loading /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle/Co ntents/MacOS/IOUSBLib: dlopen(/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bu ndle/Contents/MacOS/IOUSBLib, 262): no suitable image found. Did find:\n /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle/Co ntents/MacOS/IOUSBLib: mach-o, but wrong architecture
Dec 10 15:42:11 macmini Unknown[36394]: Cannot find function pointer IOUSBLibFactory for factory 4547A8AA-9EF3-11D4-A9BD-000A27052861 in CFBundle/CFPlugIn 0x262580 </System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle> (bundle, not loaded)
The latest log file is over 500mb
-rw-r----- 1 root admin 607343865 Dec 10 15:49 system.log
Also I see these errors
Dec 10 15:50:01 macmini com.apple.launchd[1] (org.postfix.master): Throttling respawn: Will start in 9 seconds
Dec 10 15:50:10 macmini postfix/master[67855]: fatal: open lock file pid/master.pid: unable to set exclusive lock: Resource temporarily unavailable
Dec 10 15:50:11 macmini com.apple.launchd[1] (org.postfix.master[67855]): Exited with exit code: 1
Dec 10 15:50:11 macmini com.apple.launchd[1] (org.postfix.master): Throttling respawn: Will start in 9 seconds
Am I likely to see any problems other than the large log files?

Large log files are potential problems. The larger they get the greater the probability they will become corrupted. You should use some software to clear out the logs regularly by running the built-in Unix scripts. See my maintenance FAQ for helpful suggestions:
Kappy's Personal Suggestions for OS X Maintenance
For disk repairs use Disk Utility. For situations DU cannot handle the best third-party utilities are: Disk Warrior; DW only fixes problems with the disk directory, but most disk problems are caused by directory corruption; Disk Warrior 4.0 is now Intel Mac compatible. TechTool Pro provides additional repair options including file repair and recovery, system diagnostics, and disk defragmentation. TechTool Pro 4.5.2 is Intel Mac compatible; Drive Genius is similar to TechTool Pro in terms of the various repair services provided. The current version, 1.5.1, is Intel Mac compatible.
OS X performs certain maintenance functions that are scheduled to occur on a daily, weekly, or monthly period. The maintenance scripts run in the early AM only if the computer is turned on 24/7 (no sleep.) If this isn't the case, then an excellent solution is to download and install a shareware utility such as Macaroni, JAW PseudoAnacron, or Anacron that will automate the maintenance activity regardless of whether the computer is turned off or asleep.
OS X automatically defrags files less than 20 MBs in size, so unless you have a disk full of very large files there's little need for defragmenting the hard drive. As for virus protection there are few if any such animals affecting OS X. You can protect the computer easily using the freeware Open Source virus protection software ClamXAV. Personally I would avoid most commercial anti-virus software because of their potential for causing problems.
I would also recommend downloading the shareware utility TinkerTool System that you can use for periodic maintenance such as removing old logfiles and archives, clearing caches, etc.
For emergency repairs install the freeware utility Applejack. If you cannot start up in OS X, you may be able to start in single-user mode from which you can run Applejack to do a whole set of repair and maintenance routines from the commandline.
When you install any new system software or updates be sure to repair the hard drive and permissions beforehand. I also recommend booting into safe mode before doing system software updates.
Get an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
1. Retrospect Desktop (Commercial - not yet universal binary)
2. Synchronize! Pro X (Commercial)
3. Synk (Backup, Standard, or Pro)
4. Deja Vu (Shareware)
5. PsynchX 2.1.1 and RsyncX 2.1 (Freeware)
6. Carbon Copy Cloner (Freeware - 3.0 is a Universal Binary)
7. SuperDuper! (Commercial)
The following utilities can also be used for backup, but cannot create bootable clones:
1. Backup (requires a .Mac account with Apple both to get the software and to use it.)
2. Toast
3. Impression
4. arRSync
Apple's Backup is a full backup tool capable of also backing up across multiple media such as CD/DVD. However, it cannot create bootable backups. It is primarily an "archiving" utility as are the other two.
Impression and Toast are disk image based backups, only. Particularly useful if you need to backup to CD/DVD across multiple media.
Visit The XLab FAQs and read the FAQs on maintenance, optimization, virus protection, and backup and restore.
Additional suggestions will be found in Mac Maintenance Quick Assist.
Referenced software can be found at www.versiontracker.com and www.macupdate.com.
I'm only supposing, here, but I think your log errors are generated by left over elements of Tiger not removed when you installed Leopard. This is always a potential problem with upgrade installs and Archive and Install when moving to a new major OS version. I generally recommend doing an Erase and Install.

Netinfod errors in system.log

These errors appear in my system.log every 30 minutes:
Jan 8 09:18:03 bd netinfod local[54]: notify's udp binder connection to localhost[255.255.255.255]/local failed during opening (UDP) - socket_open failed
Jan 8 09:18:03 bd netinfod local[54]: notify's tcp binder connection to localhost[255.255.255.255]/local failed during opening (TCP) - socket_connect failed
Jan 8 09:18:03 bd netinfod local[54]: update 0 to localhost[255.255.255.255]/local failed during binder contacting - couldn't getregister
Anyway to fix them?
...Rene

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

Httpd spewing errors into system.log...

Hi,
I just noticed that httpd is having problems in Mountain Lion...
Jul 26 15:09:40 eagle com.apple.launchd[1] (org.apache.httpd[4576]): Exited with code: 1
Jul 26 15:09:40 eagle com.apple.launchd[1] (org.apache.httpd): Throttling respawn: Will start in 10 seconds
Jul 26 15:09:50 eagle com.apple.launchd[1] (org.apache.httpd[4577]): Exited with code: 1
Jul 26 15:09:50 eagle com.apple.launchd[1] (org.apache.httpd): Throttling respawn: Will start in 10 seconds
The system.log file is growing ;(
I am having the same problem on another machine but in addition it is continuously removing a certificate.
Nothing is appearing in the Apache logs....
Any suggestions?
Jerry

Hey. Thanks for the advice thus far but I have the same problem on 10.9 with no resolution... the above solutions don't apply. (No funny apple stuff in apache conf, no permissions problems, logfiles exist, writable, working... and most odd of all... apache is in fact running and working.)
I just don't like the errors in the console... it disturbs me. Any other ideas? TIA.
2014/09/15 7:31:10,462 PM com.apple.launchd[1]: (org.apache.httpd[74008]) Exited with code: 1
2014/09/15 7:31:10,462 PM com.apple.launchd[1]: (org.apache.httpd) Throttling respawn: Will start in 9 seconds
2014/09/15 7:31:15,828 PM 1PasswordAgent[430]: Failed to return databaseID, encryption key is not loaded
2014/09/15 7:31:23,562 PM com.apple.launchd[1]: (org.apache.httpd[74009]) Exited with code: 1
2014/09/15 7:31:23,562 PM com.apple.launchd[1]: (org.apache.httpd) Throttling respawn: Will start in 6 seconds
2014/09/15 7:31:31,613 PM com.apple.launchd[1]: (org.apache.httpd[74010]) Exited with code: 1
2014/09/15 7:31:31,613 PM com.apple.launchd[1]: (org.apache.httpd) Throttling respawn: Will start in 8 seconds
2014/09/15 7:31:42,430 PM com.apple.launchd[1]: (org.apache.httpd[74011]) Exited with code: 1
2014/09/15 7:31:42,430 PM com.apple.launchd[1]: (org.apache.httpd) Throttling respawn: Will start in 8 seconds
2014/09/15 7:31:51,435 PM com.apple.launchd[1]: (org.apache.httpd[74012]) Exited with code: 1
2014/09/15 7:31:51,435 PM com.apple.launchd[1]: (org.apache.httpd) Throttling respawn: Will start in 9 seconds
2014/09/15 7:32:04,516 PM com.apple.launchd[1]: (org.apache.httpd[74014]) Exited with code: 1
2014/09/15 7:32:04,516 PM com.apple.launchd[1]: (org.apache.httpd) Throttling respawn: Will start in 6 seconds
2014/09/15 7:32:10,611 PM com.apple.launchd[1]: (org.apache.httpd[74015]) Exited with code: 1
2014/09/15 7:32:10,611 PM com.apple.launchd[1]: (org.apache.httpd) Throttling respawn: Will start in 10 seconds
2014/09/15 7:32:21,306 PM com.apple.launchd[1]: (org.apache.httpd[74017]) Exited with code: 1
2014/09/15 7:32:21,307 PM com.apple.launchd[1]: (org.apache.httpd) Throttling respawn: Will start in 10 seconds
2014/09/15 7:32:31,397 PM com.apple.launchd[1]: (org.apache.httpd[74018]) Exited with code: 1
2014/09/15 7:32:31,397 PM com.apple.launchd[1]: (org.apache.httpd) Throttling respawn: Will start in 10 seconds

Mac Pro freezes frequently after "NVChannel" error in system.log

Hi,
Can anybody here with a 2008 Mac Pro run the Folding @ Home client without hard crashing the Mac?
I have a 2008-model Mac Pro, with the nVidia GeForce 8800 GT, which freezes frequently. As detailed in an earlier post[1], the graphics driver sees to be implicated, as just before the freezes, messages like this appear in the system log:
kernel kern 3/30/08 7:53:52 PM Debug NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x6 = Fifo: Parse Error
kernel kern 3/30/08 7:53:52 PM Debug 0000000b
If you google for "NVChannel freeze" then you will find many many Mac owners whose machines freeze with similar symptoms. Apple recently released the "Leopard Graphics Update" which fixes such problems for some users, but not others.
In my 2008 Mac Pro's case, I have found a way to trigger the freeze 100% of the time: install the freeware Folding@Home client[2], and run the demo in the Applications folder. Just opening this app causes those messages to appear in the log, and then the Mac freezes.
I work for a software company which writes Mac software, so now that I have found a reliable way to reproduce this issue, I will be filing a bug report through Apple's bug system. But for my own sanity, I would like to collect more info, if possible.
If you have a 2008 Mac Pro and want to be cool, try running the Folding @ Home client app (link below) and post in this thread:
a.) whether or not your Mac froze
b.) what video card you have
c.) how much RAM you have
Thanks!
[1]: http://discussions.apple.com/thread.jspa?messageID=6920946&#6920946
[2]: http://folding.stanford.edu/English/Download

Yup… this is a memory fault and you should firstly try reseating the RAM and memory Risers (even change the slots they are in - depending on your configuration of course). The can often remove these issues.
Failing that, I would contact the RAM vendor and discuss it with them. Depending on how they sell things it might be simpler to send a kit, as in two DIMMs, back for replacement rather than a single DIMM that is part of a kit. Also, unless they specifically match your original DIMMs then you'd be better of returning both.

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

Applepushserviced errors on system log?

Hi,
My macbook pro (mid-2009) hasn't been able to go to sleep with Lion (10.7.4) for a while with the "idle timer" (i.e. automatically after a time period). I started to investigate this with no luck so far, but found something like this in my system.log:
Aug 1 12:42:40 macbook sandboxd[478] ([69]): applepushservice(69) deny file-read-data /Library/Preferences/com.apple.security.revocation.plist
Aug 1 12:42:40 macbook applepushserviced[69]: Unable to get entitlements for client task. Error: The operation couldn’t be completed. (Mach error 100005 - (operating system/?) unknown subsystem error)
Aug 1 12:42:40 macbook applepushserviced[69]: Failed entitlement check 'com.apple.private.aps-connection-initiate' for 'imagent' (359)
Aug 1 12:42:40 macbook applepushserviced[69]: Entitlement com.apple.private.aps-connection-initiate required to use _APSCreateConnection
This repeats every 30 seconds or so.... any idea what causes this and howto solve the issue?
Could this prevent my macbook to sleep? Sleep works fine when closing the lid or selecting sleep from the Apple-menu.
-Pasi-

Test after each of the following steps that you haven’t already tried:
Step 1
 ▹ System Preferences ▹ Print & Scan ▹ Open Print Queue...
Check all printers for unfinished jobs. Deal with any you find.
Step 2
 ▹ System Preferences ▹ Energy Saver ▹ Power Adapter ▹ Wake for network access: uncheck. You may need to unlock the preference pane by clicking the lock icon in the lower left corner and entering your administrator password.
Step 3
 ▹ System Preferences ▹ Energy Saver ▹ Schedule… ▹ Start up or wake: uncheck
Step 4
Disconnect all wired peripherals except keyboard, mouse or trackball, and monitor, if applicable.
Step 5
Launch the Activity Monitor application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Activity Monitor in the page that opens.
Select All Processes from the menu in the toolbar of the Activity Monitor window, if not already selected. Enter “powerd” (without the quotes) in the "Filter" text field. Select the powerd process and click the Quit Process button in the toobar (stop-sign icon.) In the sheet that opens, click Force Quit. You’ll be prompted for your administrator password. The process will be relaunched immediately.
Step 6
Boot in safe mode and log in. The instructions provided by Apple are as follows:
Be sure your Mac is shut down.
Press the power button.
Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, you can’t boot in safe mode.
Safe mode is much slower to boot and run than normal. Don’t launch any applications at first. If sleep still doesn’t work properly, back up all data and reinstall the OS. After that, if you still have the issue, make a “Genius” appointment at an Apple Store to have the machine tested.
If sleep now works as expected, go on to the next step.
Step 7
Still in safe mode, launch the usual set of applications that are running when you have the problem, including your login items, one at a time, testing after each one. Some applications may not work; skip them. You might be able to identify the cause of the problem this way.
Step 8
If sleep is still working after you’ve launched all the usual applications, reboot as usual (not in safe mode) and test again. If sleep still works, you’re done, at least for the moment.
If you still have the sleep issue after booting out of safe mode, post again.

Strange endless errors in system log

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

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

Servermgrd error in system log

As of recently upgrading to 10.5 (specifically 10.5.6), I've been seeing this error, over and over, thousands of times, in my system.log.. any ideas?
Jan 2 05:15:26 intel servermgrd[79]: Starting idle processing
Jan 2 05:15:26 intel servermgrd[79]: Done with idle processing
Jan 2 05:15:39 intel kernel[0]: unknown SIGSEGV code 0
Jan 2 05:16:09: --- last message repeated 3 times ---
Jan 2 05:16:19 intel kernel[0]: unknown SIGSEGV code 0
I did a man servermgrd and the only thing I can think of is deleting the launchd file, but figured I'd check on here first..

Is this on Mac OS X client or Server?
Either way I think the servermgrd messages are a red herring. The time stamps in no way coincide with the kernel errors.
The actual error is a memory-related problem that was caught by the OS. Since it's reported by the kernel it's going to be tough to track down without more detail.

Error in System Log: DirectoryService[26]

Hello,
i have the following Error Masseage on one of our Server all the time: DirectoryService[26]: Failed Authentication return is being delayed due to over five recent auth failures for username: admin
The Server is bind to AD and makes rsync to two different other Servers.
Sometimes on one from the other Servers the rsync fails with this Error:
Received disconnect from xxx.xxx.xxx.xxx: 2: Too many authentication failures for admin
So, i dont know is this one Problem or two different Problems.
Can somone help me?
Thanks
Sven

What's to help?
The machine at the specified IP address is trying to login as admin but failing due to an incorrect password.
The issue is whether that IP address is known to you, and whether you expect this. If the IP address is unknown then it could be a remote attack against your computer (someone using a dictionary attack against your admin account). If it IP address is known then it's a machine on your network that's trying to log in - this could be a local user trying to gain admin privileges or something as benign as someone running a copy of Server Monitor/Server Admin but with the wrong account password.
Either way knowing the IP address is the critical step.

ORA -00054 Errors in system log

Regards
dhrish

Ho Dhrish,
You might need to increase MAXOPENCURSORS.
Check below notes based on your SAP release : SAP Notes 857423 and 988851
Hope this helps.
Regards,
Deepak Kori

Strange system log error

Hi everyone.
I'm having some trouble.
Today i saw my system log file have an error going.
its a
iMac AOSNotification[165]: [AOSNotification] XMPP session not connected - no ping sent
and it is coming all day long.
i'm sure it have something to do with MobileMe or some synchronizing thing.
Anyone have an idea of what to do ? I did try to log out and back in on MobileMe.
But it didn't help.
Thx

Hi.
Yes. it is synchronizing with my Notes, Keychains, Bookmarks and Calendar but not with a iPhone
Just the normal MobileMe on the computer. The iPhone is manually synchronized with iTunes and not with MobileMe.
But the strange part is. I even deleted all the MobileMe sync preffs such as
user/Library/Application support/Preferences/host/com.apple.AOSNotification
user/Library/Application support/Preferences/host/com.apple.DotMacSync
user/Library/Application support/Preferences/com.apple.FileSyncAgent.plist
and logged out of MobileMe preffspane in systempreffs.
And it is still giving me the same error in system log ????
Really weird now that i eint logged in ?

Error in system log

Similar Messages

Maybe you are looking for