Xserve - Auto Reboot after power loss

I have an Xserve (All updated) in a server farm. Recently the farm lost power, someone screwed something up. The net result was the server lost power. When the power was restored shortly thereafter the Xserve DID NOT reboot automatically, as I expected it would. Once the power button was pressed, everything booted fine.
SYSTEM PREFERENCES/ ENERGY SAVER/ are set to RESTART AUTOMATICALLY AFTER A POWER FAILURE.
Why did this not reboot when the power was restored?
Is there another, more reliable way to ensure this works properly, Firmware Settings?
TIA

I am thinking maybe the power was still off when the Xserve wanted to restart?

Similar Messages

  • Broadband does not auto reconnect after power loss

    I have a D-Link DSL-302G ADSL modem and Netgear AC1900 on an  Eaton Powerware 5110 UPS. When there is power loss or brown out in our neighbourhood , our internet goes off and  does not reconnect automatically. I then have to physically turn off the Netgear Router and turn back on to get the Green LED  Internet light back on.  The modem seems unaffected, but it is bridged so my router controls the connection process. Now this is what has me puzzled - my devices never lose power because of the UPS, and the router connection mode is set to "always on" , and Internet IP address is set to "Get Dynamically from ISP" Is it the local Telstra exchange dropping all connections when swithcing to battery backup, and then disrupting the normal connection process for the Router upon power resume ? Can you confirm what happens, or are there some tests I can do? This is very inconvenient as I run a terminal server, and not in the office all the time to reboot the router.    

    Hi Melior,
    Normally, if there was a loss of power at your premises but not at the exchange then once the power was restored your modem should automatically reconnect (In this instance, a UPS should keep the modem powered up and connected).  If there was a loss of power at the exchange your modem should connect automatically once the exchange is powered back up.  
    So given the information that you have provided, I would suggest that you check your equipment.
    - Ben 

  • Reboot after Power loss doesn't work

    The situation:
    I bought a APC Back-UPS 350 and a mac mini for an exhibition.
    The Power ist turned off by the stuff from time to time.
    The UPS turns off the mac after 1 minute (10.4.7 works fine, 10.4.10 doesn't react at all but
    thats not the problem)
    The problem:
    the mac doesn't restart after turning the power back on. I checked the "Power loss restart"-option
    in the panel. I cleared the PRAM, did a reset on the SMC, … has anyone an idea or better: a solution? Thanks.

    Hi happyappleusersofar-
    Greetings and welcome to the Apple boards.
    Any chance the UPS is not putting out any power for some reason? Have you tried this with the mini plugged directly into the wall?
    Luck-
    -DaddyPaycheck

  • WLC 4402 - APs last reboot reason power loss

    st1\:*{behavior:url(#ieooui) }
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Normale Tabelle";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman";
    mso-ansi-language:#0400;
    mso-fareast-language:#0400;
    mso-bidi-language:#0400;}
    Hi,
    we have a Wireless LAN Controller WLC 4402, Software Version 4.1.192.22M (Mesh).
    At the moment there are 6 Access Points in one house, one of them is the root AP. The others are only connected via electrical socket.
    AP’s are: AIR-LAP1131AG-E-K9 / Boot Version 12.3.8.0 / IOS Version 12.4(3g)JMC1
    I think the configuration worked fine over a period of 2 years.
    Now the problem is that the number of access points connected to the controller is changing nearly every minute. At times there is only one AP connected to the controller. So it is impossible for the clients to build up a steady connection. They have to log in via the guest user web interface at short intervals or they can’t see the wireless lan.
    First we thought it would be a problem of one or two “defect” access points. But we replaced 4 of the 6 access points and the problem is still there.
    An example, yesterday:
    13:17 o’clock – 2 AP’s
    13:19 o’clock – 4 AP’s
    13:21 o’clock – 5 AP’s
    13:23 o’clock – 4 AP’s
    13:25 o’clock – 5 AP’s
    13:25 o’clock – 4 AP’s
    13:26 o’clock – 5 AP’s
    13:26 o’clock – 6 AP’s
    13:28 o’clock – 4 AP’s
    13:28 o’clock – 2 AP’s
    Eye-catching is the following message of the log, which appears often: “52       Mon May 16 13:21:56 2011        AP 'AP001d.e557.6fd8', MAC: 00:1d:70:01:bc:20 disassociated previously due to AP Reset. Last reboot reason: power loss
    Also eye-catching is the AP up time. The Root AP is up for over 80 days. But all the other access points show an up time of a few minutes until some hours…but not more.
    Does anybody know what the problem could be?? I read some similar threads but no solution.
    In the following an abstract of the log:
    21        Mon May 16 13:25:43 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
    22        Mon May 16 13:25:30 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:b5:a0
    23        Mon May 16 13:25:30 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
    24        Mon May 16 13:25:30 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
    25        Mon May 16 13:25:05 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
    26        Mon May 16 13:24:10 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
    27        Mon May 16 13:24:10 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
    28        Mon May 16 13:24:10 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
    29        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
    30        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
    31        Mon May 16 13:23:59 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
    32        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
    33        Mon May 16 13:23:58 2011        AP 'AP001d.45d8.4ea6', MAC: 00:1d:71:e1:b2:20 disassociated previously due to AP Reset. Last reboot reason: power loss
    34        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
    35        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
    36        Mon May 16 13:23:31 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
    37        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
    38        Mon May 16 13:23:30 2011        AP 'AP001d.e557.6f0c', MAC: 00:1d:70:01:b5:a0 disassociated previously due to AP Reset. Last reboot reason: power loss
    39        Mon May 16 13:23:13 2011        Client Association: Client MAC:00:1d:71:e1:b2:2f Base Radio MAC :00:1d:70:01:bc:20 Slot: 1 User Name:c1130-001D45D84EA6
    40        Mon May 16 13:23:13 2011        Mesh child node '00:1d:71:e1:b2:2f' has changed its parent to mesh node '00:1d:70:01:bc:20' from mesh node '00:1f:ca:cc:b7:40'.
    41        Mon May 16 13:23:04 2011        Mesh child node '00:1d:70:01:b5:af' has changed its parent to mesh node '00:23:5e:49:9d:e0' from mesh node '00:1f:ca:cc:b7:40'.
    42        Mon May 16 13:22:57 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
    43        Mon May 16 13:22:39 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
    44        Mon May 16 13:22:39 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
    45        Mon May 16 13:22:39 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
    46        Mon May 16 13:22:39 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
    47        Mon May 16 13:22:17 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1d:70:01:bc:20' from mesh node '00:1f:ca:cc:b7:40'.
    48        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
    49        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
    50        Mon May 16 13:21:57 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
    51        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
    52        Mon May 16 13:21:56 2011        AP 'AP001d.e557.6fd8', MAC: 00:1d:70:01:bc:20 disassociated previously due to AP Reset. Last reboot reason: power loss
    53        Mon May 16 13:21:39 2011        Client Association: Client MAC:00:23:5e:49:9d:ef Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-0021D847FFCA
    54        Mon May 16 13:21:32 2011        Client Association: Client MAC:00:23:5e:49:9d:ef Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-0021D847FFCA
    55        Mon May 16 13:21:12 2011        Mesh child node '00:1d:71:e1:b2:2f' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:b5:a0'.
    56        Mon May 16 13:21:05 2011        Client Association: Client MAC:00:1d:70:01:bc:2f Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-001DE5576FD8
    57        Mon May 16 13:20:32 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
    58        Mon May 16 13:20:11 2011        Mesh child node '00:1d:70:01:bc:2f' is no longer associated with mesh node '00:1f:ca:cc:b7:40'.
    59        Mon May 16 13:20:06 2011        Mesh child node '00:1d:70:01:b5:af' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
    60        Mon May 16 13:19:57 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:b5:a0
    61        Mon May 16 13:19:57 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
    62        Mon May 16 13:19:57 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
    63        Mon May 16 13:19:49 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:bc:20
    64        Mon May 16 13:19:49 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Heartbeat Timeout
    65        Mon May 16 13:19:49 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Heartbeat Timeout
    66        Mon May 16 13:19:39 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
    67        Mon May 16 13:19:39 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=Heartbeat Timeout
    68        Mon May 16 13:19:39 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=Heartbeat Timeout
    69        Mon May 16 13:19:36 2011        AP Disassociated. Base Radio MAC:00:1d:71:e1:b2:20
    70        Mon May 16 13:19:36 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Heartbeat Timeout
    71        Mon May 16 13:19:36 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Heartbeat Timeout
    Greetings Lydia

    st1\:*{behavior:url(#ieooui) }
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Normale Tabelle";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman";
    mso-ansi-language:#0400;
    mso-fareast-language:#0400;
    mso-bidi-language:#0400;}
    Hey,
    last week I tried to upgrade the controller step-by-step.
    Under the software 4.1.192.35M the problem was still there… access points were often disassociated from the controller.
    There were problems with Software 4.2.207.54M too. The access points couldn’t reach the download-status. The log of the access point said that it could not open the tar-file.
    So I went back to 4.1.192.35M. Of course the controller lost some of its configuration. I configured it new with the same settings as before.
    After it the wireless connection seemed to be a little bit more robust. I asked the users to test the connection at the weekend and this is the answer:
    “so we tested the WLAN during the weekend. The situation definitely improved with respect to before. Authetication is much faster and the connection (when active) is sensibly faster.
    However the connection is still very unstable and it is necessary every five-ten minutes to reconnect (especially for intense network traffic like when watching a streaming content or using VOIP applications. Actually switching off and on again the WLAN card (Airport) often a new authentication is not required. However, without doing so the connection would not resume alone to a working state.
    So what to say? Better than before (thanks) but far from being fixed. From last September to January we did not experience any problem, so it must be something that chronologically happened at the beginning of the year, it is not a systemic problem.
    But there were no changes or anything else at the beginning of the year.
    Do you mean it makes sense to resume upgrading? I’m a little bit afraid of more problems like under 4.2.207.54M
    Greetings Lydia

  • 8.02 POA crashes w/ntdll.dll fault after power loss

    Hi,
    Running GW 8.0.2 on Windows 2003 server (POA, MTA and GWIA). After power loss on Friday, POA will not stay up for long - crashes with:
    "Faulting application gwpoa.exe, version 8.0.2.10840, faulting module ntdll.dll version 5.2.3790.4455" error.
    MTA and GWIA are not crashing.
    I thought maybe it could be a corrupt message but the only messages in the queues are dated today and not Friday (\PO\wpcsout\ofs\4 - wpcsin queues are empty). I am currently running gwcheck.exe against the message databases but that is going to take a couple hours. Any thoughts? Thanks.

    Originally Posted by DJMUGI
    Hi, I'm reaching out to DJHess (and other forum members) - we are having nearly exactly the same issue (same version of GW, gwpoa.exe and ntdll.dll), POA does not stay up long (crashes after just a few hours) - but we did not have a power loss (that I am aware of). Was a solution ever determined for this issue? Did gwcheck.exe help (it does not for us)?
    I am having the exact same problem. Below are the specs of my GroupWise servers:
    GroupWise 8.0.2 (POA and MTA)
    Server OS: 2008 R2 x64
    The POA will randomly shut down with an ntdll.dll error fault. I have migrated this server to new hardware and a new OS (user to be on a 2003 R2 SP2 server and half the RAM). Same issue. Anyone have a fix for this?

  • Option that SAP starts automaticly after power loss

    I am using an windows/sql ECC 6.0 server. I would like option that SAP starts automaticly after power loss. Is it possible and how?

    Hi
    I think this not possible.
    Thanks
    Pankaj Kumar

  • RVL200 won't auto-reconnect to Internet after power loss (PPPoE)

    My RVL200 firmware 1.1.7 is configured for PPPoE. The connection to the Internet is via an ATT (SBC) DSL line using a Siemens Slipstream 4100 modem. The 4100 is configured to allow the PPPoE connection to be managed by the router. The RVL200's PPPoE fails to automatically reconnect to the Internet after a power loss (or if I click Disconnect on the RVL200's web page). This is true for both the Connect on Demand and Keep Alive PPPoE alternatives. In either case, I have to go to the router's web screen and manually click "Connect" to force a reconnection. The LAN is populated by Win XP SP2 systems.
    Is there some special configuration needed on the LAN, in the RVL200's routing table, or in the modem to allow automatic reconnection to occur? Obviously it is undersirable to have to give out the RVL200 password to everyone who might need to force a reconnect after a power loss.
    Neither the RVL200 Admin Guide not the Users Guide has any useful information on this issue.

    I have to manually reconnect it. This issue came up when testing what would happen with an RVL200 in a power failure - whether it would automatically reconnect. I don't expect a lot of power failures, but I do want the network to reconnect automatically rather than have to count on someone knowing how to do it and having the apssword.
    Am I correct that it is supposed to automatically re-establish the PPPoE connection?
    What triggers the reconnection?

  • T400: auto reboot after poweroff

    A confused problem occurs on my T400.  
    It automatic reboots after my t400 power off whatever I shut down by winos or I keep pressing the power button for a few seconds. I have updated BIOS to new latest version. I look up many web pages, but I couldn’t find out a way to fix it. Maybe my t400’s motherboard has damaged. Someone can tell me what problem has occurred on my t400.
    moderator note: type added to subject line for clarity.
    Solved!
    Go to Solution.

    Currently i have no new ideas what it could be, but i'll check, if i can find something. another thing about the "reboot" i mentioned before: it may be the automatic reboot from windows, because i find the thinkpad t400 sometimes looks like it is shutdown, although it's rebooting, just had the experience that i wanted to reboot and just thought for a few seconds "ok, is it now shutdown or rebooting?!?", because ALL status leds were off, just as you mentioned, and then the lights turned on again and it did the wanted reboot... don't want to offend, but i think it might be confusing in realizing that it's rebooting instead of "suddenly turning on again".
    Did you look into the logs of windows, if there was an error or something like that while shutting down?
    I just thought about if there's a bios option for always on on after ac power loss... i recently had some trouble with an other pc, which didn't shutdown and just went on and on again, because it seemed the bios interpreted the shut down as ac power loss... just an idea.
    greetz
    thefred

  • VPN auto startup after power cut

    Good evening
    I have set my server to auto start after a power outage. What I would like is have the vpn startup. So the server is auto logging in as a certain user, and then the user has a auto startup item. The server Admin.
    The issue is that the server admin needs to you to bring the window to the foreground in order for the vpn to startup.
    Is there another way to do this?

    Does it power back on after a power outage? auto-boot only covers the boot after the server powers on or is reset. I don't see an option in OpenBoot for auto power on after a power interruption.

  • Domain.sites" could not be opened. After power loss

    Oh sht have i got a prob.
    I'm getting this message after a power loss, iweb will just not open anything............
    The document "Domain.sites" could not be opened.
    IWEB
    Can’t open file “~/Library/Application Support/iWeb/Domain.sites.”
    I have main site posted, so need to get that back into iweb of course. But I've also been working on new part to the site. It looks like I've lost everything and of course it's on the one drive I don't back up!!!
    Can anyone help with what this could be?!?!
    Thanks
    Rob

    Sorted

  • Problems with connecting to internet after power loss w WRT54G v3

    I'm having problems connecting to the internet after a power loss with my WRT54G v3 wireless router.  I'm at the latest firmware version (4.21.1). 
    I found similar problems with the V2 version of this router. 
    After a power failure, I can access the http interface to the router,all of my settings are there (not set to factory settings),the unit is connected to my ISP provider,I can ping from the router, but none of my wired or wireless PCs can ping.
    To "fix" this condition, I have to reset to factory settings, then re-load my saved configuration.This usually works, but sometimes I have to hard reset the unit.
    Anyone having this problem? Anyone have a fix?

    Sudden loss of power for extended periods of time will 9x out of 10 will corrupt the saved configurations and can only be fixed in the way you already described.
     A solution for this is getting an UPS incase of a power failure your equipment will be on battery back up until either the battery runs out or power is restored (depending on the model changed the battery time)
    With Knowledge… Impossible means nothing.
    Credentials
    Computer experience: 11 years
    Cisco networks experience: 8 years
    Network administrator: 6 years
    N.E.T. networks experience: 6 years
    Linksys networks experience: 6 years
    Recent additions: A+ | Networks+ | Linux+ | Security+

  • Dock is drastically different and no guest login option after power loss

    Folks, forgive if this is addressed elsewhere.  I am fairly new here. 
    I am running a MacBook with 10.5.8.  I have been having some battery/power issues lately which I thought was resolved with a new battery.  Today, my machine shut down while plugged in and a purported "79% battery" left.  It has done this perhaps 2 other times in the last year or so. 
    When I got the machine to completely boot, there was no longer a "guest login" option which I remember setting months ago.  Also, my dock had large icons, many icons for programs I run everyday were missing.  All of my applications, files, etc. seem to be intact.  It is as though the machine has re-set to default settings.  Why did this happen?  Can I go back to my old settings somehow? 
    Thank you!
    Dani

    There is no prevention or network proceedure that would prevent that matter. The correct way to fix that problem after a storm will be to disconnect everything, power units down for 15 to 20sec.(router & modem), power units back up, once units come back up to normal fuction connect the modem back to router, then connect pc to router and reboot. That should establish your connection back after power outage.

  • Yosemite does not start after power loss

    I just want to report a bug related to the new OSX Yosemite.
    Here at work I have to manage around 30 iMacs, plus some MacBook Pro.
    After some initial tests, where I did not discover any particular incompatibility with our applications, I decided to upgrade my machines to Yosemite, but I had to stop the upgrade process when I realized the new OSX has this big and strange problem... now I have my machines half upgraded.
    It happened to have some power losses due to the bad weather conditions, and after each one the machines with Yosemite didn't start... you have the black screen with the apple logo and the bar freezed at almost 50%.
    You can only power OFF and ON till the computer finally starts... usually it takes 5-6 tries.
    The problem is not related with the iMac models, I have some different kind of iMac and on overyone I have the very same problem, the only thing these machines have in common is the new OSX 10.10 (10.10.1 didn't fix this problem), the others with Mavericks does no suffer this matter after the same power loss.
    Hope this report could reach some Apple developer, in any case if I have to produce some log to debug it let me know, I will be happy to help.
    Massimo

    Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.
    Feedback
    Or you can use your Apple ID to register with this site and go the Apple BugReporter. Supposedly you will get an answer if you submit feedback.
    Feedback via Apple Developer

  • Always auto reboot after update 4.3

    im Z1 user from china, after update 4.3, auto reboot once a day,and yesterday i restore factory settings,but auto reboot also....>_<,help me please!

    As per the above advice, please see a step by step guide below:
    1. Download the PC Companion software from http://www.sonymobile.com/gb/tools/pc-companion/
    and install it on your PC.
    2. Install and open PC Companion then select Support Zone.
    3. Phone Software Update.
    4. Start.
    5. Repair Phone
    6. Continue
    7. Accept data removal
    8. Next
    9. Wait for prepare
    10. Select Phone
    11. Follow the connection steps
    Don't forget to mark posts that answers the topic as Accepted Solution. 
    If you find any post helpful, press Kudos.
    What are your thoughts about this forum? Let us know by doing this short survey.
     - Official Sony Xperia Support Staff
    If you're new to our forums make sure that you have read our Discussion guidelines.
    If you want to get in touch with the local support team for your country please visit our contact page.

  • How to configure V240 auto-boot after power failure?

    Hi!
    How to configure automatic boot of V240 machine after power failure? After power gets resored, V240 remains in standby mode and one has to press button on front to power it up. It is not convinient because power failure can occur, for example, at night and the machine is not booted until the first user awakens :)

    Uhh... I've found publicly accessible document http://docs.sun.com/source/817-5481-11/variables.html :
    Looks like this variable controls auto-power-up behaviour:
    sc_powerstatememory
    The sc_powerstatememory variable enables you to specify the state of the host server as false (keep the host server off) or true (return the server to the state it was in when the power was removed). This is useful in the event of a power failure, or if you physically move the server to a different location.
    For example, if the host server is running when power is lost and the sc_powerstatememory variable is set to false, the host server remains off when power is restored. If the sc_powerstatememory variable is set to true, the host server restarts when the power is restored.
    The values for this variable are as follows.
    true - "Remembers" the state of the host server when power was removed and returns the server to that state when power is reapplied.
    false - Keeps the server off when power is applied.

Maybe you are looking for