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.

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.

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.

HP 8750 Printer missing since Leopard upgrade on home wireless network

My HP 8750gp is connected (ethernet not USB) to my BT Voyager 2100 wireless router and worked fine under Tiger. Since the upgrade to Leopard, it does not appear as an available printer. Tried re-installing drivers from Leopard DVD, HP installation cd and HP website but still does not appear. I saw a related topic which suggested you need to be logged in with Admin privaleges to add a printer, however on my iMac I am the only account and so am always logged in as Admin. The printer has also dissapeared from my MacMini which has also been upgraded. Since re-installing drivers, HP Printer Setup loads at start up each time but cannot find the printer.
I am assuming this to be a Leopard issue (as that was the change), but could equally be a router or printer issue I guess.
Any ideas?
Regards,
Andy

For whatever reason, my printer has just started working - one moment it was not listed, the next it was. I have no idea how this miracle happened, it just did.
Andy

(Slow Network): iSight camera not working in iChat since Leopard upgrade

I have a different type of iChat video issue. My Power Mac G4, 867 MHz, 1 GB DRAM is a supported Mac for the Leopard upgrade. I've successfully installed OS 10.5.
Also my Power Mac meets the iChat Conferencing Requirements for 1-on-1 Video Chat per the OS 10.5 system requirements and the application note here:
http://docs.info.apple.com/article.html?artnum=301050
My iSight camera is connected via Firewire to an Apple Cinema Display, which feeds back to the Power Mac G4.
1) When I boot from my 10.3.9 Carbon Copy Cloner backup my iSight works in iChat (at least locally to see myself) without any issue. Green light comes on and shows me locally on video and audio sound bars. Before the OS upgrade the iSight worked fine for live video conferences with iChat 2.1.3 under Mac OS 10.3.9
2) Running OS 10.5 when I go to iChat 4.0's preferences video pane the following message is waiting "This computer does not support video conferencing."
3) With Leopard iChat 4.0 the Connector Doctor under "capabilities" says "(Slow Network)" for 1-on-1 Video Chat and won't even show video locally or turn on the iSight's green light.

Fixed!
My Power Mac Quicksilver G4, 867 MHz. problem with (Slow Network) in the iChat Connection Doctor, no video preview or video iChat since upgrading to OS 10.5 Leopard and iChat 4.0 has been solved with the following posted towards the end of the thread below. I can finally see my video preview with iChat 4.0 and have also video chatted successfully with one other user.
Topic : Macbook - iChat says "This computer does not support video conferencing"
http://discussions.apple.com/thread.jspa?threadID=1197506
Fixed by Apple Article: http://docs.info.apple.com/article.html?artnum=307035
Products affected
Mac OS X 10.5 Leopard
iChat
PowerPC-based Mac with a 867MHz processor
Solution
Quit iChat.
Open Terminal (it's in the Utilities folder, in the Applications folder).
In Terminal type or paste this command on a single line:
defaults write com.apple.iChat newbwdup 300000
Press Return.
Quit Terminal.
Open iChat.

Quicktime files showing up as white frame since Leopard upgrade

Recently upgraded to new Mac tower running Leopard from G5 running Tiger. Did a migration copy from old to new system. Since then iWeb'08 where I had been placing my quicktime files for my podcast are not showing a thumbnail only a white frame. It publishes correctly but very annoying. Any ideas?

I'm having the same problem in 10.4.11.

Problems with browsing on Safari and Firefox since Leopard upgrade ??

Ever since I upgraded to Leopard, I am experiencing consistent problems while browsing. Both Firefox and Safari stall when I click on links or try to load pages. The browsers just appears dead and the loading icons just stall. Firefox is much worse than Safari with every 3rd or 4th click causing a stall. I have to wait about a minute before the click is recognized and the page is loaded.
I thought it might be my airport connect but I have other Windows comps on the same network and they don't have the problem.
I haven't seen any thread in the Safari discussions about this and can't find anything on the net about it either.
Anyone know what the problem might be?
Safari 3.1.1
Firefox 2.0.0.14
Leaopard 10.5.2

There were no error messages in the console for the stalling. However after I plugged the ethernet cable into the Imac, the problem seems to have gone away.
This is good but how can I fix the problem with my airport wireless connection ?

I chat problem since Leopard upgrade.

I recently upgraded to Leopard, now i chat has an issue. When I click on a buddy, a window opens with my icon and a bubble, however when I type and hit return I see nothing. In addition when my buddy responds I see his/hers icon and bubble briefly then it disappears with no text.

I've been having this same problem since I upgraded to Leopard. Also my buddy list is grey and displays all my contacts online or not. The privacy features also are not accessible and say that I can't change them because I am not logged in, but I am logged in according to the main screen. I am behind a netgear router most of the time and connect wirelessly to an airport express. My provider is Comcast. I have changed the port to 443, tried the fix listed here, tried to fix it using onyx, and I'm sure more. At this point I am using Adium because I can't get iChat to work. I want to use iChat as I really like the new features and it was one of the reasons I upgraded to Leopard in the first place.

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.

Console not logging after Leopard upgrade

Hi everyone
I've had a number of problems after the Leopard upgrade, the most serious of which is not being able to get my POP mail (separate post in the Mail and Address Book forum), but I'm also puzzled as to why Console.app isn't logging "console" anymore.
Other logs continue to add data, including the SpamSieve log and crash logs, but "console" only goes up to when I upgraded to Leopard, three days ago: it says nothing after that point, despite several restarts.
There are older "console" logs, but none newer than that date.
I'd like it working, because it's such an important part of checking and fixing things.
I have no idea why it is not logging: your suggestions are most welcome.

Clytie wrote:
I'd like it working, because it's such an important part of checking and fixing things.
It is working, but in a different way.
Everything gets written to a Log Database these days, and the messages that would previously gone to the old console.log appear there as "Console Messages" under "Log Database Queries" in Console.app.
system.log is unusual in that it still exists although everything written there also goes to the database. However I think you'll find that every console message also goes to system.log (but not vice-versa).
The only reason you have "older console logs" is because you did either an Upgrade or an Archive & Instal. I did an Erase & Instal and there are no console logs.

IPod no longer mounts since Leopard upgrade

My iPod no longer mounts since I upgraded to Leopard. I'm using a USB 2 port that's part of a third party PCI card I installed myself. Used to work fine before the Mac OS upgrade.
If I reboot with the iPod already plugged in, it mounts.
Help?

Forgot to mention that I had tried those:
Authorize your purchases from an administrator account
-> Yep, I'm the admin
Authorize using the correct account name
-> Nothing changed- I am only authorizing my devices, and only use my account on the machine. Definitely using the right account name.
Turn Off User Account Controls (Windows Vista and Windows 7 Only)
-> Did this a long, long time ago, so definitely not the issue.
Remove the SC Info folder
-> This was the only new thing that I had seen yesterday when I tried it, and went through these steps, to no avail. Still exactly the same problem. I closed iTunes, deleted the folder, rebooted and relaunched iTunes and synced the device. Same thing.
The problem is the computer IS authorized, and I can sync one device, but not the other. No problem with iPhone 4- just iPod Touch, 3rd gen. It seems to be in a weird state.
One thing would lead me to believe it's a PC/iTunes problem, but then it is only with one device and not the other. Hard to point to the root of the problem. I just don't want to lose the data on the iPod- I've done a lot of work on it.
Thanks,
Jeff

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

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

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

Errors in system.log since leopard upgrade

Similar Messages

Maybe you are looking for