- This topic has 4 replies, 3 voices, and was last updated 17 years, 5 months ago by
gripster.
-
AuthorPosts
-
May 27, 2009 at 6:29 pm #376305
akinspe
ParticipantHas anyone encountered the following issue? I created a 10.5.7 image using InstaDMG and discovered that Console.app has difficulty reading the ASL database. If you open up Console.app and choose the “Console Messages” or “All Messages” option in the side bar you get nothing and if you manually view /var/log/system.log you get an entry like this:
Error: status 2 returned by _asl_server_query
It appears that the /var/log/asl folder is there with .ASL files, but something isn’t jiving. This doesn’t appear to happen when you upgrade a 10.5.6 system to 10.5.7. Something that I might try is to make a 10.5.0 machine and then boot it and then apply the combo update afterwards. I.e. is it something in the 10.5.7 combo update that doesn’t do stuff properly on a different target volume.
FWIW, the resulting machine is an Intel machine. I have not tested the image on a PPC yet.
So has anyone else done 10.5.7 builds and seen this?
June 1, 2009 at 3:30 pm #376345gripster
ParticipantHi there..
We are having the same issue. After applying the 10.5.7 combo update to 4 of our Leopard Servers this weekend, all display the exact same problem as you. Console queries fail with error: “Error: status 2 returned by _asl_server_query”
We ran the combo update from another volume, to ensure a cleaner upgrade process..but this may be the cause of the problem?
I am glad we are not the only one having the issue, yet there seems to be no fix as of yet.
If we figure it out I will update this post 🙂
Mike
June 2, 2009 at 8:22 pm #376363Rusty Myers
ParticipantI’m seeing this on my builds too, non server.
RustyJune 2, 2009 at 8:47 pm #376365akinspe
ParticipantInterestingly, this does NOT happen if you use the more recent InstaDMG builds that utilize the chroot facility to jail the installers. Seems that 10.5.7 combo update is doing some not nice things if it requires that.
June 2, 2009 at 9:12 pm #376366gripster
ParticipantHi Guys…not sure if this applies to your issue..but it sort of explains our problem. Read the “Important” section in the release notes…the issue is caused by not running the combo update from the target itself. Now if only there was a quick fix without doing the combo update again..
-
AuthorPosts
- You must be logged in to reply to this topic.