Prev: iMac manual
Next: Tiger Apache installation
From: bbcda on 17 Mar 2010 22:39
Hey, JR!

On 2010-03-16 22:35:03 -0400, Jolly Roger said:
>
>
> I see nothing in that log indicating shutdown.
>
> Take a look at the console log (/Applications/Utilities/Console) and see
> if anything shows up indicating shutdown there. It seems like if this is
> an automated event, it should be logged in either the system log of
> console log!

How are You today?
Hm, "bad" news: I couldn't find any hints with respect to the
shutdown-problem... the system has shut down twice today, once, I
think, was really due to a power failure (I used my MacBook last
evening until the battery was really empty, then I closed the lid and
left it "sleeping" over night - and in the morning, the system had to
reboot... I thought it would automatically go into "safe sleep"
(hibernate) when the battery drowns - but it seems that that's not
really the case... However, the first entry in the file Your Apple
Script created was from the time I booted the system newly in the
morning. Is that what You would expect from Your script?
Anyways, I don't think that looking at this first event is what will
likely help me. However, in the afternoon (not over lunch...), I got an
interrupted shut-down again - according to Your script at 15:40:38.
Now, here's what the console log says around that time (again, I copy a
bit more, since I don't see anything much in it - except for a hell of
a lot of different error messages... all my apps seem to love to chat a
lot... maybe a bit like myself .-D ):



XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
BEGIN OF CONSOLE LOG:

17.03.10 15:12:46 com.apple.backupd[3955] Failed to resolve network
service using name = XXXXX XXXXXXs Time Capsule type = _afpovertcp._tcp
domain = local.
17.03.10
15:12:46 com.apple.launchd[1] (com.apple.netauth.sysagent[3956]) Exited
with exit code: 255
17.03.10 15:12:51 com.apple.backupd[3955] Backup failed with error: 19
17.03.10 15:13:31 kernel Auth result for: 00:XX:XX:XX:79:b0 MAC AUTH succeeded
17.03.10 15:15:28 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
15:15:28 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 15:18:30 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:55822 from 155.246.1.21:53
17.03.10 15:18:30 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:55577 from 155.246.1.21:53
17.03.10 15:19:01 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:53418 from 155.246.1.21:53
17.03.10 15:20:34 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
15:20:34 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 15:24:28 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:50946 from 155.246.1.21:53
17.03.10 15:25:40 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
15:25:40 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 15:29:58 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:56070 from 155.246.1.21:53
17.03.10 15:30:02 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:56999 from 155.246.1.21:53
17.03.10 15:30:46 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
15:30:46 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 15:35:28 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:54100 from 155.246.1.21:53
17.03.10 15:35:29 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:60288 from 155.246.1.21:53
17.03.10 15:35:52 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
15:35:52 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 15:37:59 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:64717 from 155.246.1.21:53
17.03.10 15:40:31 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:53271 from 155.246.1.21:53
17.03.10 15:40:58 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
15:40:58 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 15:44:28 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:54174 from 155.246.1.21:53
17.03.10 15:45:32 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:63180 from 155.246.1.21:53
17.03.10 15:46:06 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
15:46:06 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 15:48:31 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:54790 from 155.246.1.21:53
17.03.10 15:50:59 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:62829 from 155.246.1.21:53
17.03.10 15:51:12 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
15:51:12 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 15:53:31 kernel Auth result for: 00:XX:XX:XX:79:b0 MAC AUTH succeeded
17.03.10 15:55:25 mDNSResponder[28] ERROR: mDNSPlatformReadTCP - SSLRead: -9806
17.03.10 15:55:25 mDNSResponder[28] ERROR: tcpCallback - attempt to
read message length failed (-1)
17.03.10 15:55:32 mDNSResponder[28] ERROR: mDNSPlatformReadTCP - SSLRead: -9806
17.03.10 15:55:32 mDNSResponder[28] ERROR: tcpCallback - attempt to
read message length failed (-1)
17.03.10 15:56:01 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:59185 from 155.246.1.21:53
17.03.10 15:56:18 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
15:56:18 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 15:57:28 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:53667 from 155.246.1.21:53
17.03.10 16:01:24 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
16:01:24 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 16:01:28 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:54093 from 155.246.1.21:53
17.03.10 16:03:58 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:60273 from 155.246.1.21:53
17.03.10 16:06:30 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:64967 from 155.246.1.21:53
17.03.10 16:06:30 [0x0-0x3b03b].com.vmware.fusion[290] 2010-03-17
16:06:30 CUPS config timestamp change detected but old config retrieved
via interface!
17.03.10 16:06:58 Firewall[59] Stealth Mode connection attempt to UDP
155.246.236.32:62576 from 155.246.1.21:53
17.03.10 16:11:15 com.apple.backupd[4516] Starting standard backup

END OF CONSOLE LOG
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I don't really see anything there that helps me at all... I admit that
those "Stealth Mode connection attempt"s seem a bit frightening - but,
according to what I found on the internet, they are not even half as
frightening as they seem (well, at least for what I found in the Apple
forums about that search term...). Can You find anything more
interesting there? The only thing I see in the minute around the
shutdown-attempt is one of those stealth-attempts, and the annoying
omnipresent Fusion-CUPS-thing (whatever that is, exactly... but it
comes so often - it can't be connected to the cause of the problem - I
believe... or could it be the coincidence of the "stealth"-attempt and
that?)

Hm, I am getting paranoid! :-D

Oh - if I only understood this!... It starts driving me crazy :-D It
seems like a more complicated problem than what I thought...


Best wishes!!
Bj�rn

From: dorayme on 17 Mar 2010 23:08
In article <4ba19275$0$22509$607ed4bc(a)cv.net>,
bbcda <office8(a)eml.bbcda.de> wrote:

> Oh - if I only understood this!... It starts driving me crazy :-D It
> seems like a more complicated problem than what I thought...

How about logging into a clean untouched account, create one if
need be. Have no third party apps in there. And just let the
original OS defaults come into play re sleep and energy settings.

Or this:

1. Get the latest combo update with your present machine if you
have no access to another. Stick it on a USB stick.

2. Get an external HD and back up everything you have now.

3. Wipe your Macbook disk clean with Disk Utility.

4. Get your original OS software DVDs out.

5. Just load the basic OS.

6. Set almost nothing you don't have to. Say yes to only the
really necessary things like admin/user name etc. Resist all
temptation to over egg any pudding.

7. Stick the USB stick in and run the latest combo update.

8. Keep the power cable attached and login and leave for the sort
of time frame you were having problems with.

There is a zen to this. Do not be tempted to vary it or add any
further thoughts of your own to the above algorithm. <g>

--
dorayme
From: Jolly Roger on 18 Mar 2010 15:13
In article <4ba19275$0$22509$607ed4bc(a)cv.net>,
bbcda <office8(a)eml.bbcda.de> wrote:

> Hey, JR!
>
(snip)
>
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> BEGIN OF CONSOLE LOG:
>
> 17.03.10 15:12:46 com.apple.backupd[3955] Failed to resolve network
> service using name = XXXXX XXXXXXs Time Capsule type = _afpovertcp._tcp
> domain = local.
> 17.03.10
> 15:12:46 com.apple.launchd[1] (com.apple.netauth.sysagent[3956]) Exited
> with exit code: 255
> 17.03.10 15:12:51 com.apple.backupd[3955] Backup failed with error: 19
(snip)

I would be interested to know if a Time Machine backup failure happens
each time this "auto shutdown" happens. Could it be that what is
actually happening is that due to a Time Machine failure, the OS is
somehow doing a shutdown? Hmmm...

Track this for a few more days and see if you can identify a pattern of
messages in the log that is similar each time.

> I don't really see anything there that helps me at all... I admit that
> those "Stealth Mode connection attempt"s seem a bit frightening - but,
> according to what I found on the internet, they are not even half as
> frightening as they seem (well, at least for what I found in the Apple
> forums about that search term...). Can You find anything more
> interesting there? The only thing I see in the minute around the
> shutdown-attempt is one of those stealth-attempts, and the annoying
> omnipresent Fusion-CUPS-thing (whatever that is, exactly... but it
> comes so often - it can't be connected to the cause of the problem - I
> believe... or could it be the coincidence of the "stealth"-attempt and
> that?)
>
> Hm, I am getting paranoid! :-D

Nah, the stealth messages are nothing to be concerned about. The fact is
any device that is connected to the internet is constantly bombarded
with pings and brute force attempts to gain entry. Because you have
stealth mode enabled, your computer is simply logging those pings.

--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR
From: bbcda on 18 Mar 2010 15:25
Hey, JR - hey, dorayme,

thanks. Well, it seems like Time Machine might be a problem, as JR
says. I'll do the following: I'll keep an eye on it, and maybe, on the
weekend, do what dorayme suggested (leave the machine standing with a
pristine new user account), and see what happens...

If it still seems to be Time Machine, I might consider asking Apple about it.

Thank You all! I will inform You here when something new comes out of
my research... :-D

Best,
Bj�rn




On 2010-03-18 15:13:53 -0400, Jolly Roger said:

> In article <4ba19275$0$22509$607ed4bc(a)cv.net>,
> bbcda <office8(a)eml.bbcda.de> wrote:
>
>> Hey, JR!
>>
> (snip)
>>
>> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>> BEGIN OF CONSOLE LOG:
>>
>> 17.03.10 15:12:46 com.apple.backupd[3955] Failed to resolve network
>> service using name = XXXXX XXXXXXs Time Capsule type = _afpovertcp._tcp
>> domain = local.
>> 17.03.10
>> 15:12:46 com.apple.launchd[1] (com.apple.netauth.sysagent[3956]) Exited
>> with exit code: 255
>> 17.03.10 15:12:51 com.apple.backupd[3955] Backup failed with error: 19
> (snip)
>
> I would be interested to know if a Time Machine backup failure happens
> each time this "auto shutdown" happens. Could it be that what is
> actually happening is that due to a Time Machine failure, the OS is
> somehow doing a shutdown? Hmmm...
>
> Track this for a few more days and see if you can identify a pattern of
> messages in the log that is similar each time.
>
>> I don't really see anything there that helps me at all... I admit that
>> those "Stealth Mode connection attempt"s seem a bit frightening - but,
>> according to what I found on the internet, they are not even half as
>> frightening as they seem (well, at least for what I found in the Apple
>> forums about that search term...). Can You find anything more
>> interesting there? The only thing I see in the minute around the
>> shutdown-attempt is one of those stealth-attempts, and the annoying
>> omnipresent Fusion-CUPS-thing (whatever that is, exactly... but it
>> comes so often - it can't be connected to the cause of the problem - I
>> believe... or could it be the coincidence of the "stealth"-attempt and
>> that?)
>>
>> Hm, I am getting paranoid! :-D
>
> Nah, the stealth messages are nothing to be concerned about. The fact is
> any device that is connected to the internet is constantly bombarded
> with pings and brute force attempts to gain entry. Because you have
> stealth mode enabled, your computer is simply logging those pings.


From: dorayme on 18 Mar 2010 17:52
In article <4ba27d36$0$2387$a1967b79(a)news.stevens-tech.edu>,
bbcda <office8(a)eml.bbcda.de> wrote:

> Hey, JR - hey, dorayme,
>
> thanks. Well, it seems like Time Machine might be a problem, as JR
> says. I'll do the following: I'll keep an eye on it, and maybe, on the
> weekend, do what dorayme suggested (leave the machine standing with a
> pristine new user account), and see what happens...

I would suggest turning time machine completely off for the test
whether on a new account, a fresh install or just right now. Turn
off all scheduled things.

--
dorayme
 |  Next  |  Last
Pages: 1 2
Prev: iMac manual
Next: Tiger Apache installation