SystemUIServer SQLITE_ERROR

Question

SystemUIServer SQLITE_ERROR

I am getting a problem with OS X 10.7.4 and a corrupt database for Finder operations

The symptom is very slow delete operations in the finder (3-4 sec lag) and slow autocomplete in the Terminal.

I assume that the file database is corrupt.

After reboot there is a period before the slow down occurs but it happens after about 5 min.

Not sure how to fix it but here are the console errors:

SystemUIServer: Unknown error calling sqlite3_step (11: database disk image is malformed) eu

SystemUIServer: DB Query: BEGIN EXCLUSIVE TRANSACTION;

SystemUIServer: Error calling sqlite3_step (1: SQL logic error or missing database) SQLITE_ERROR

SystemUIServer: DB Query: COMMIT TRANSACTION;

also getting this but I think it's unrelated:

mdworker: (Error) ImportPluginLoading: Couldn't load plugin 'Spotlight/LyX-Metadata.mdimporter/ -- file://localhost/Applications/LyX.app/Contents/Library/'

Thanks for your suggestions

Mac Pro, Mac OS X (10.7.4)

Posted on Apr 23, 2013 4:09 AM

Reply

Answer 1

Apr 23, 2013 8:26 AM in response to chiasmahealth

mdworker is the task that does the heavy lifting for the Spotlight index of all your files, built in the background. It may well store the index in an SQL database.

That error seems to indicate some parts are missing or the LyX.app is damaged.

The Finder does not need the Spotlight index to do its work, but you may also have Directory damage on the Boot Drive. The Directory is not a SQL database, but a very File-specific set of data structures maintained as a balanced tree-structure and several associated lists. It is checked and repaired with Disk Utility, using the ( Repair Disk ) function.

N.B. ( Repair Permissions ) function is limited to repairing some permissions issues, if they occur, and does not check or repair the basic Directory structures.

Reply

Answer 2

Linc Davis

Level 10

209,851 points

Apr 23, 2013 10:14 AM in response to chiasmahealth

Please read this whole message before doing anything.

This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, or by a peripheral device.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.

Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.

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.

Test while in safe mode. Same problem?

After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

Reply

Answer 3

Apr 23, 2013 8:27 PM in response to Grant Bennet-Alder

I have checked the disk and there are no errors nor any actions on permission repair.

I am trying to identify what causes the problem to start after boot but it is not immediatly present.

Reply

Answer 4

The hatter

Level 9

61,041 points

Apr 24, 2013 3:42 AM in response to chiasmahealth

There are few real programs that can rule out any and all errors.

** tests for a few things, it does not read or check for file integrity only directory.

Sometimes nothing beats have a clone of your system from before, and clone of your data (and keep the two on separate disk drives) along with TimeMachine (plural also).

Carbon Copy Cloner does have an advanced option to do a check sum on each and every file and of course reads and has to write every file. Use it.

And along with cloning the system, it will offer to create and copy Lion and ML Recovery partition.

So even if you boot from another disk or Recovery you can use ** Repair Disk. I would not rely on Verify Disk as a 100% test of the system. And permissions have zero to do with your issues.

You could create a new test user account and direct that to another disk drive (a small partition even of 10GB) so you are not using the old account.

And what about possible problems with all the hidden ".DS or "._DS files built by the Finder.

Reply

Answer 5

May 29, 2013 9:39 PM in response to chiasmahealth

Thanks for the suggestions,

I found the solution, it was a problem with my audio config that resulted in a pause with any audio tones (ie: a terminal bell with no matches to autocomplete) or a file deletion. Just goes to show that one shouldn't ignore the obvious!

Reply

Answer 6

Aug 20, 2013 12:34 AM in response to chiasmahealth

Coule you please elaborate on how you fixed this? I'm having the exact items being logged over and over in the console. Not sure if it's related but my audio will stop playing at random times, then lead to applications freezing up.

Thanks!

Reply

Answer 7

Aug 21, 2013 6:46 PM in response to charlesdudley

I was using a USB audio module that did not work properly, therefore any event calling sounds was delayed.

I think the Sqlite error was separate (apparently caused by previous version of istat menus 4).

I fixed by replacing the USB audio module

Reply

Answer 8

Aug 21, 2013 6:50 PM in response to chiasmahealth

I appreaciate the quick response! I think you're right about iStat, I've disabled it for now and the errors have ceased.

Reply