MacBook Pro 2011 will alle 20 Minuten ausloggen / Shutdown

owowowow · 05.06.18

Liebe Apfeltalker,
da ich mir selbst bei diesem Problem nicht mehr helfen kann, wende ich mich an Euch.
Das Durchforschen dieses Forums und die Befolgung einiger Tipps führte nicht zum Erfolg, deshalb schildere ich mein Problem einmal hier aktiv.

Mein MBP zeigt nach 20 Minuten die bekannte Abfrage auf dem Monitor, die auch beim absichtlichen Abmelden / Herunterfahren gezeigt wird, allerdings OHNE, dass ich das aktiv gewählt hatte:

Wenn ich {Abbrechen} anklicke, läuft der Rechner ganz normal weiter, agiere ich nicht, loggt der MAC aus, geht also in StandBy.
Aus dem Standby kann ich den Rechner problemlos wieder über die Passworteingabe reaktivieren.

Dieses Verhalten zeigt der Rechner auch dann, wenn z.B. ein Video gerendert wird, also Hard- und Software zu 100% aktiv sind.
Arbeite ich hingegen aktiv mit der Maus und der Tastatur, will der Mac nicht ausloggen

Nun habe ich zur Analyse folgenden Test gemacht:
- Rechner kaltgestartet
- Aktivitätsanzeige gestartet
- Programme - Dienstprogramme -Konsole gestartet
- Finger vom Rechner genommen und gewartet
- bei Erscheinen der og Bildschirmmeldung {Abbrechen} geklickt
- Konsolentext kopiert und gesichert

Meine Frage: Was kann ich tun, um dieses regelmäßige ungewollte LOGOUT zu unterbinden

Der Konsolentext dieses Tests ist hier (Mittelteil weggekürzt, weil der Text laut Forumsmeldung zu lang ist):

Code:

fehler    14:00:54.470475 +0200    signpost_notificationd    0 is not a valid connection ID.
standard    14:00:54.470545 +0200    signpost_notificationd    Invalid Connection ID 0
fehler    14:00:54.470697 +0200    signpost_notificationd    0 is not a valid connection ID.
standard    14:00:54.470761 +0200    signpost_notificationd    Invalid Connection ID 0
standard    14:00:54.629412 +0200    cloudpaird    ZoneCreated read: MagicCloudPairingAccessoryEncryptionPreferences 1
standard    14:00:54.629646 +0200    cloudpaird     >>> zoneForSubscrition MagicCloudPairingCustomAccessoryZone
standard    14:00:54.634831 +0200    tccd    PID[295] is checking access for target PID[342]
standard    14:00:54.635055 +0200    tccd    Granting PID[342] access to <private> via entitlement 'com.apple.private.tcc.allow'
standard    14:00:54.640838 +0200    cloudd    [Operation 0x7fe547d71190] Initialized with context 0x7fe54923a340. Background: 0, cellular: 1, QOS: 0x19
standard    14:00:54.641408 +0200    cloudd    [Operation 0x7fe547d6d800] Initialized with context 0x7fe54923a340. Background: 0, cellular: 1, QOS: 0x19
standard    14:00:54.641490 +0200    cloudd    [Operation 0x7fe547d71190] Starting operation
standard    14:00:54.641748 +0200    cloudd    [Operation 0x7fe547d6d800] Starting operation
standard    14:00:54.644182 +0200    cloudd    [Operation 0x7fe547d71190] Operation transitioning from state 1 (cancelled=0, stop=0, error=0)
standard    14:00:54.644321 +0200    cloudd    [Operation 0x7fe547d6d800] Operation transitioning from state 1 (cancelled=0, stop=0, error=0)
standard    14:00:54.645590 +0200    cloudd    [Operation 0x7fe547d6d800] Operation is now in state 2
standard    14:00:54.646675 +0200    cloudd    [Operation 0x7fe547d72140] Initialized with context 0x7fe54923a340. Background: 0, cellular: 1, QOS: 0x19
standard    14:00:54.647187 +0200    cloudd    [Operation 0x7fe547d72140] Starting operation
standard    14:00:54.648942 +0200    cloudd    [Operation 0x7fe547d72140] Operation transitioning from state 1 (cancelled=0, stop=0, error=0)
standard    14:00:54.649412 +0200    cloudd    [Operation 0x7fe547d72140] Operation is now in state 2
standard    14:00:54.661731 +0200    cloudd    [Operation 0x7fe547d71190] Request 0x7fe549041f30 set on operation
standard    14:00:54.663463 +0200    cloudd    [Request 0x7fe549041f30] Performing
standard    14:00:54.663471 +0200    cloudd    [Operation 0x7fe547d71190] Operation is now in state 2
standard    14:00:54.664147 +0200    cloudd    [Request 0x7fe549041f30] Getting URL for the user partition
standard    14:00:54.664621 +0200    cloudd    [Request 0x7fe549041f30] Getting configuration
standard    14:00:54.665499 +0200    cloudd    [Request 0x7fe549041f30] Fetching important user IDs
standard    14:00:54.666635 +0200    cloudd    [Request 0x7fe549041f30] Getting device ID
standard    14:00:54.666712 +0200    cloudd    [Operation 0x7fe547d72140] Operation transitioning from state 2 (cancelled=0, stop=0, error=0)
standard    14:00:54.667600 +0200    cloudd    [Operation 0x7fe547d72140] Operation is now in state 4
standard    14:00:54.667959 +0200    cloudd    [Operation 0x7fe547d72140] Operation transitioning from state 4 (cancelled=0, stop=0, error=0)
standard    14:00:54.668370 +0200    cloudd    [Operation 0x7fe547d72140] Operation is now in state 5
standard    14:00:54.668837 +0200    cloudd    [Operation 0x7fe547d72140] Operation transitioning from state 5 (cancelled=0, stop=0, error=0)
standard    14:00:54.669271 +0200    cloudd    [Operation 0x7fe547d72140] Operation is now in state 6
standard    14:00:54.669621 +0200    cloudd    PCSIdentitySetCreate: BTPairing {
    kPCSSetupDSID = "<<VALUE>>";
}
standard    14:00:54.696491 +0200    cloudd    [Operation 0x7fe547d72140] Operation transitioning from state 6 (cancelled=0, stop=0, error=0)
standard    14:00:54.697013 +0200    cloudd    [Operation 0x7fe547d72140] Operation is now in state 4294967295
standard    14:00:54.698344 +0200    cloudd    [Operation 0x7fe547d6d800] Operation transitioning from state 2 (cancelled=0, stop=0, error=0)
standard    14:00:54.698984 +0200    cloudd    [Operation 0x7fe547d6d800] Request 0x7fe547d74be0 set on operation
standard    14:00:54.701418 +0200    cloudd    [Operation 0x7fe547d6d800] Operation is now in state 3
standard    14:00:54.701423 +0200    cloudd    [Request 0x7fe547d74be0] Performing
standard    14:00:54.702990 +0200    cloudd    [Request 0x7fe547d74be0] Getting URL for the user partition
standard    14:00:54.703665 +0200    cloudd    [Request 0x7fe547d74be0] Getting configuration
standard    14:00:54.704183 +0200    cloudd    [Request 0x7fe547d74be0] Fetching important user IDs
standard    14:00:54.705101 +0200    cloudd    [Request 0x7fe547d74be0] Getting device ID
standard    14:00:54.730453 +0200    FrontendAgent    TIC TCP Conn Event [2:0x7fc12d706830]: 2
standard    14:00:54.730510 +0200    FrontendAgent    TIC TCP Conn Cancel [2:0x7fc12d706830]
standard    14:00:54.731049 +0200    FrontendAgent    [2 <private> stream, pid: 336, url: https://e.crashlytics.com/spi/v2/events, tls] cancelled
    [2.1 B38328F2-A33F-4402-878F-AB36F243357A <private>.49175<-><private>]
    Connected Path: satisfied (Path is satisfied), interface: en1, ipv4, dns
    Duration: 30.934s, DNS @0.000s took 0.021s, TCP @0.022s took 0.112s, TLS took 0.298s
    bytes in/out: 6079/1893, packets in/out: 8/4, rtt: 0.111s, retransmitted packets: 0, out-of-order packets: 0
standard    14:00:54.759090 +0200    apsd    <private>: Received request from <private> to generate token for topic "<private>" and identifier ""
standard    14:00:54.761568 +0200    apsd    Failed to talk to secd after 4 attempts.
standard    14:00:54.762490 +0200    apsd    <private>: Received request to generate token for topic "<private>" and identifier "", assigned appId "0"
standard    14:00:54.767203 +0200    securityd    0x7f815fa0dd70(0x7f815fa03640) is unlocked; decoding for makeUnlocked()
standard    14:00:54.783849 +0200    cloudd    [Request 0x7fe549041f30] Getting zone gates
standard    14:00:54.783894 +0200    cloudd    [Request 0x7fe547d74be0] Getting zone gates
standard    14:00:54.794738 +0200    usbmuxd    notice    device connected: 1-fe80::1420:4d33:eb41:1b9f:0
standard    14:00:54.791877 +0200    securityd    keychain reference in server mode
standard    14:00:54.802387 +0200    apsd    <private>: Outstanding data received: <private> (length 8)
standard    14:00:54.802588 +0200    apsd    <private>: Stream processing: complete yes, invalid no, length parsed 8, parameters <private>
standard    14:00:54.802771 +0200    apsd    <private>: Received app token generate response <private>
standard    14:00:54.802864 +0200    apsd    <private>: Received response for token request for topic <private>, appId 0, new token = <private>
standard    14:00:54.803068 +0200    apsd    <private>: Received token <private> for topic <private> with identifier
standard    14:00:54.803157 +0200    apsd    <private>: Sending token <private> for topic <private> with identifier
standard    14:00:54.803276 +0200    apsd    <private>: Stream processing: complete no, invalid no, length parsed 0, parameters (null)
standard    14:00:54.803367 +0200    apsd    Dispatching low priority message: <xpc object>
standard    14:00:54.842009 +0200    trustd    cert[2]: AnchorTrusted =(leaf)[force]> 0
standard    14:00:54.857946 +0200    trustd    cert[2]: AnchorTrusted =(leaf)[force]> 0
standard    14:00:54.877351 +0200    trustd    cert[2]: AnchorTrusted =(leaf)[force]> 0
standard    14:00:54.891174 +0200    securityd    0x7f815ce28300(0x7f815fa03640) is unlocked; decoding for makeUnlocked()
standard    14:00:54.896202 +0200    trustd    cert[2]: AnchorTrusted =(leaf)[force]> 0
standard    14:00:54.905183 +0200    apsd    Looking up connection on peer: e581d610   found <private>
standard    14:00:54.905735 +0200    cloudpaird    <private> Received token <private> forTopic <private> identifier
standard    14:00:54.910103 +0200    trustd    cert[2]: AnchorTrusted =(leaf)[force]> 0
standard    14:00:54.920177 +0200    securityd    keychain reference in server mode
standard    14:00:54.927712 +0200    trustd    cert[2]: AnchorTrusted =(leaf)[force]> 0
standard    14:00:54.941658 +0200    trustd    cert[2]: AnchorTrusted =(leaf)[force]> 0
standard    14:00:54.946332 +0200    imagent    Message from client: 0x7fa60e01d2d0
standard    14:00:54.949424 +0200    imagent    Message from client: 0x7fa60e01d2d0
standard    14:00:54.955560 +0200    trustd    cert[2]: AnchorTrusted =(leaf)[force]> 0
standard    14:00:54.992232 +0200    ckkeyrolld    TIC TCP Conn Cancel [1:0x7f85ca6129b0]
standard    14:00:54.992779 +0200    ckkeyrolld    [1 <private> stream, pid: 325, url: https://configuration.apple.com/configurations/internetservices/ckkeyrolld/ckkeyrolld-1.0.plist, tls] cancelled
    [1.1 F31FEB4F-DE55-4439-9550-9F66132DC462 <private>.49179<-><private>]
    Connected Path: satisfied (Path is satisfied), interface: en1, ipv4, dns
    Duration: 30.374s, DNS @0.000s took 0.001s, TCP @0.003s took 0.088s, TLS took 0.257s
    bytes in/out: 3805/776, packets in/out: 5/3, rtt: 0.017s, retransmitted packets: 0, out-of-order packets: 0
standard    14:21:13.866689 +0200    powerd    Activity changes from 0x0 to 0x1. UseActiveState:1
standard    14:21:13.867091 +0200    powerd    hidActive:0 displayOff:0 assertionActivityValid:1 now:0x501  hid_ts:0x3d assertion_ts:0x501
standard    14:21:13.874518 +0200    dasd    Trigger: <private> is now [1]
standard    14:21:13.875076 +0200    dasd    Inactivity period does not intersect predicted
standard    14:21:13.878407 +0200    dasd    Trigger: <private> is now [1]
standard    14:21:13.949136 +0200    loginwindow    lux 35.000000, ambient 0.495714, <private>
standard    14:21:13.949194 +0200    loginwindow    setting canAdjust from 1 to 1
standard    14:21:13.949243 +0200    loginwindow    brightness 0.49571 _ambientOffset = 0.47750 final (to be capped) = 0.97321
standard    14:21:13.949287 +0200    loginwindow    PWM value = 3987 speed = 500
standard    14:21:13.951312 +0200    loginwindow    changed brightness to 0.973214. <private>
standard    14:21:16.030025 +0200    dasd    Attempting to suspend based on triggers: (     "com.apple.duetactivityscheduler.deviceactivitypolicy.inusestatus",     "com.apple.duetactivityscheduler.restartpolicy.inusestatus" )
standard    14:21:16.031748 +0200    dasd    501:com.apple.searchd.reindex:45CA9B:[
 ] sumScores:31.910000, denominator:32.010000, FinalDecision: Can Proceed FinalScore: 0.996876}
standard    14:21:16.031868 +0200    dasd    Ignoring trigger com.apple.duetactivityscheduler.deviceactivitypolicy.inusestatus because conditions are deteriorating
standard    14:21:16.031946 +0200    dasd    Ignoring trigger com.apple.duetactivityscheduler.restartpolicy.inusestatus because conditions are deteriorating
standard    14:21:16.032012 +0200    dasd    Evaluating 0 activities based on triggers
standard    14:21:16.132236 +0200    loginwindow        token = 1000419
standard    14:21:16.146616 +0200    loginwindow    -[SessionStateMonitor setLogoutState:] | ************* logout state: LogoutCanceled
standard    14:21:19.586307 +0200    identityservicesd    Beginning cleanup of outgoing message database
standard    14:21:19.586970 +0200    identityservicesd    Cleaned up 0 expired messages
standard    14:21:19.587331 +0200    identityservicesd    Beginning cleanup of outgoing message database for quickswitched messages
standard    14:21:19.587808 +0200    identityservicesd    Ending cleanup of outgoing message database for quickswitched messages
standard    14:21:19.587962 +0200    identityservicesd    Beginning cleanup of outgoing message database for messages older than 2 days past enqueue date
standard    14:21:19.588186 +0200    identityservicesd    Using Time Interval 549721279.588036
standard    14:21:19.588761 +0200    identityservicesd    Ending cleanup of 0 outgoing message database for older than 2 days past enqueue date
standard    14:21:19.588935 +0200    identityservicesd    Beginning cleanup of outgoing message database
standard    14:21:19.589879 +0200    identityservicesd    Ending cleanup of outgoing message database
standard    14:21:19.898629 +0200    loginwindow    lux 51.000000, ambient 0.623600, <private>
standard    14:21:19.898728 +0200    loginwindow    setting canAdjust from 1 to 1
standard    14:21:19.898800 +0200    loginwindow    brightness 0.62360 _ambientOffset = 0.47750 final (to be capped) = 1.10110
standard    14:21:19.898850 +0200    loginwindow    PWM value = 4091 speed = 500
standard    14:21:19.900650 +0200    loginwindow    changed brightness to 1.000000. <private>
standard    14:21:20.103693 +0200    loginwindow    lux 75.000000, ambient 0.710000, <private>
standard    14:21:20.103823 +0200    loginwindow    setting canAdjust from 1 to 1
standard    14:21:20.103937 +0200    loginwindow    brightness 0.71000 _ambientOffset = 0.47750 final (to be capped) = 1.18750
standard    14:21:20.104041 +0200    loginwindow    PWM value = 4091 speed = 500
standard    14:21:20.107381 +0200    loginwindow    changed brightness to 1.000000. <private>
standard    14:21:20.312295 +0200    loginwindow    lux 105.000000, ambient 0.758000, <private>
standard    14:21:20.312392 +0200    loginwindow    setting canAdjust from 1 to 1
standard    14:21:20.312463 +0200    loginwindow    brightness 0.75800 _ambientOffset = 0.47750 final (to be capped) = 1.23550
standard    14:21:20.312526 +0200    loginwindow    PWM value = 4091 speed = 500
standard    14:21:20.314292 +0200    loginwindow    changed brightness to 1.000000. <private>
standard    14:21:20.515317 +0200    loginwindow    lux 124.000000, ambient 0.788400, <private>
standard    14:21:20.515488 +0200    loginwindow    setting canAdjust from 1 to 1
standard    14:21:20.515657 +0200    loginwindow    brightness 0.78840 _ambientOffset = 0.47750 final (to be capped) = 1.26590
standard    14:21:20.515753 +0200    loginwindow    PWM value = 4091 speed = 500
standard    14:21:20.519037 +0200    loginwindow    changed brightness to 1.000000. <private>

Weiter dazu im nächsten Post

owowowow · 05.06.18

Weitere Infos zum vorhergehenden Post:

Der ETRECHECK ergab folgenden Report:

Code:

Report gelöscht, weil nicht zielführend

Vielen Dank an Alle, die ihre Zeit opfern um sich meines Problems anzunehmen !

Mitglied 167358 · 05.06.18

Hallo,
das klingt fast wie:

Bildschirmfoto 2018-06-05 um 22.08.58.png

Das müsstest Du aber bewusst aktiviert haben.
Das ist aber nur ein Verdacht auf die Schnelle.

owowowow · 06.06.18

Hallo Gwadro, du bist ein Lebensretter !

Dein Tipp war der VOLLTREFFER !

Warum das so gesetzt war, wer das so gesetzt hat .... Frag' mich was Leichteres. Ist jetzt auch egal, das Problem ist GELÖST !! Herzlichen Dank !!

Warum sich allerdings der MAC als "inaktiv" abmeldet während er eine intensive Rechenarbeit beim Rendering eines Videos verrichtet, das müsste mir mal ein OS-Programmierer erklären :rolleyes:

Mitglied 167358 · 06.06.18

Na sehr schön. Warum er sich allerdings abmelden will ist mir auch nicht ganz klar.

Wobei die Sache Ansicht schon interessant ist, da das System einen Shutdown machen will und nicht wie vermittelt den Nutzer abmelden will. :rolleyes:

Suche

Suche

MacBook Pro 2011 will alle 20 Minuten ausloggen / Shutdown

owowowow

Erdapfel

Anhänge

owowowow

Erdapfel

Mitglied 167358

Gast

owowowow

Erdapfel

Mitglied 167358

Gast

Wir schützen Ihre Privatsphäre

Informationen auf einem Gerät speichern und/oder abrufen

Personalisierte Anzeigen und Inhalte, Anzeigen- und Inhaltsmessungen, Erkenntnisse über Zielgruppen und Produktentwicklungen (Optionale Cookies)

Datenübermittlung an Partner in anderen Staaten (Drittanbieter-Cookies)