Mac Mini Server & OS X Lion

Can I wipe off the Snow Leopard server version running on a 2.53 Ghz Core 2 Duo Server and install the "normal" OS X lion on it...? I do not want the server version... If so, what are the steps I should follow.. Thanks in advance.

The Lion installer will detect that you have Snow Leopard Server and prompt you to purchase the Lion Server add-on.  In order to install "just Lion desktop", you need to be running the non-server version of Snow Leopard.  SL desktop is not supported on a Mini Server so you will want to Google on how to do that.
Alternatively, you may want to Google on how to create a bootable USB flash drive with the Lion installer.  This will allow you to "clean install"Lion without having to have Snow Leopard preinstalled.  This is also unsupported, but arguably easier than trying to install SL desktop on the Mini Server.

Similar Messages

  • Mac Mini Server 2011, with lion, sleeps every day

    My new Mac Mini Server 2011, with lion, sleeps every day! Server not responding.
    All services are down, smb, vnc, ssh too. And it not should be happen because this is a server, right?
    Please, I need help with this problem!
    How to fix it?

    1.  Go to System Preferences.
    2.  Select Engery Saver
    3.  Slide the setting for Computer sleep to never.
    4.  Slide the setting for Display sleep to never (though I believe the display should be able to sleep without much issue.
    5.  Make sure the following are not selected:
    a.  Put the hard disk(s) to sleep when possible.
    b.  Allow power button to put the computer to sleep.
    6.  Make sure the following are selected:
    a.  Wake for network access
    b.  Start up automatically after a power failure
    c.  Restart automatically if the computer freezes.
    Good luck!

  • MAC MINI SERVER WITH Mountian lion....

    I purchased a mac mini "server" after Mountian lion came out I did the upgrade in OS only to find out my "Server" function will not work on Mountian Lion.... what's up apple....I've been a fan for 6 computers and didn't expect this.

    Restore your previous installation or purchase Server 2.0.
    The "server" part of te system has been broken out into
    a seperate add-on application instead of being tightly integrated
    as a seperate version of OSX.

  • Hello, I just wanted to know when an update would be available for my mac mini server os x lion to resolve the issues regarding my m-audio fastrack pro usb audio interface (no midi messages recognized)

    Hello, I just wanted to know when an update would be available for my mac mini server os x lion to resolve the issues regarding my m-audio fastrack pro usb audio interface (no midi messages recognized)

    Have you reported your problems to Apple?
    BugReporter
    <http://bugreporter.apple.com>
    Free ADC (Apple Developer Connection) account needed for BugReporter.
    Anyone can get a free account at:
    <http://developer.apple.com/programs/register/>
    And/Or
    Mac OS X Feedback<http://www.apple.com/feedback/macosx.html>

  • How to install OSX 10.6 client in Mac Mini Server 10.7 Lion Server

    I am ordering a Mac Mini Server with Lion Server 10.7, with 256GB SSD and 750GB HD.  I want to use Snow Leopard (client/workstation) instead.  Previously I have already purchased retailed version of 10.5 clients and 10.6 client upgrade.  Please advise the best approach from the followings (or more suggestions from you guys...). 
    (A) The boot disk (likely to be the SSD) will be re-formatted and re-installed by "clean" installation of 10.6 client.  But I am not sure whether all hardware drivers for the new Mac Mini (2011) are available in the 10.6 client disk.  Also, it seems to me that installation disk of 10.7 server will not be provided.  So I shall not be able to re-install server version again if I want to change this Mac to a server sometimes afterwards.  Of course I would like to keep this server software for investment protection, no matter I use it or not.  If 10.6 client can be installed, I shall use bootcamp to install Windows 7 also.  So there will be 2 partitions to be usable aparently.
    (B) The factory-installed OSX 10.7 server is kept, and one more partition is created (with Disk Utilties).  Snow Leopard workstation 10.6 will be installed at this new partition.  If 10.6 client can be installed, I shall use bootcamp to install Windows 7 also.  So there will be 4 partitions, including 10.7 server, 10.6 client, 10.7 recovery drive and bootcamp for Windows 7.  Since I want to put all OS software at the SSD (faster boot-up and better performance), the drawback is that each partition is with less space.
    Do you guys have other ideas or suggestions?
    [Background]
    In fact I want to make use of its strongest computing power (amongst available Mac Mini computers in store), quad-core CPU & dual disks,  to run music applications (DAWs).  Operating systems are put at SSD, and data is put at traditional harddisk.  As some music applications (e.g. Calkwalk Dimension) only support 10.6 currently, I need to down-grade from Lion server to Snow Leopard workstation.  Also I think applications can run faster in a hardware with  workstation OS (rather than server version). Please correct me if this belief is wrong. 
    Thanks / Howard.

    If you completely wipe the original Mac mini boot drive you will wipe the Server.app software an dlose it. You should make a backup first, perhaps by saving the entire boot drive as a Disk Image file on to another drive.
    In terms of install 10.6, the 10.6 DVD will not boot on the new Mac mini even if you connect a DVD drive. You need to put the Mac mini in to FireWire Target Disk Mode and connect it to an older Mac that will allow booting from that DVD, then install on to the Mac mini (over FireWire), you then need to upgrade it using the 10.6.8 Combo Updater this will add the drivers needed for the new Mac mini.

  • Mac mini Server with normal Lion install?

    Can i install on the Mac Mini Server (Mid 2011) a normal Lion OSX?
    I don't want to use Server features, i only need the hardware power.
    Is the Server pre-installed?

    The 'proper' way is to have the Mac Mini Server running the version of OSX that's written for it, the hardware IS different hence there's (subtle yet real) differences to the software installed on each. I can't confirm if it would Boot from an external drive with the normal 10.7 softwarre as I've never tried that ...
    If you don't need the Server applications then run Server, turn the services off and uncheck:

  • Adding a redundancy to Mac Mini Server using Mt. Lion

    Currently we are using a mac mini with MT lion server. Everything is working great, but i want to create redundancy backup with an additional Mac mini. What is the best way to proceed? We know about target disk mode. Do we need additional Raid software? Any advice would be greatly appreciated.
    "Take one Mac mini server configure as you like and enable its boot drive as a RAID member. Boot the other Mac mini server into Target Disk Mode. Connect them with a FW-800 cable (or ThunderBolt cable if the equipment supports it). Add the TDM mini to the mirror that the boot drive is in."
    Is the above solution acceptable?
    Thanks!

    download SuperDuper

  • Can the Late 2012 Mac Mini Server run on Lion, instead of Mountain Lion?

    Since I plan to use this (USB 2) device http://plugable.com/products/UGA-2K-A
    on a (yet to be ordered) Late 2012 Mac Mini Server, I am wondering:
    could that box run on Lion, instead of Mountain Lion ? (the usb 2 device has some M.L. issues still)
    I would not really need the server-part (only want the box because of the 2 disk drives), maybe that influences things.
    Would there be any possibility to order it from Apple with Lion instead of Mountain Lion pre-installed ?
    Could the latest hardware in the box not-function under Lion, thereby necessitating Mountain Lion ?
    Thanks to all for thinking with me!
    Best,
    Arie

    It's simple: you cannot use a version of OS X older than the version that the Mac shipped with.  At the very least, this is because the hardware may not be supported.

  • Mac mini server mid 2011 lion mouse pointer disappears after sleep

    Hi,
    I bought a mid 2011 mac mini server (quad core) running OSX Lion (10.7.2), and I use it with the magic trackpad. Sometimes (not every time) when I wake the computer from sleep (I let it sleep via the menu at night), the mouse pointer is not visible. I can use the trackpad, and move the mouse and click, only I cannot see where I click because the mouse pointer is not visible.
    The batteries in the trackpad are OK.
    When I plug in a USB mouse, I can move and click that too, but the mouse pointer is still invivible.
    So it seems to be OSX related
    The only thing that seems to help is to restart the system. After reboot the mouse is back as normal. Still this is very annoying as it makes sleep quite useless.
    Anyone else suffering from this? Any solutions? Thanks.
    Thanks,
    Gino

    I also have this issue intermittantly but fairly often.
    But sometimes the cursor comes back but the screen stays black except where the cursor has moved across, revealing the screen, a bit like using the spraycan tool in MacPaint years ago.
    And to top it off I have a problem with sleep making all the open apps try to quit, but one is always unable to, and it seems to lock everthing up until I wake up the mac, and then all the apps that were open do resume, but in the meantime any TV programs that should have recorded (by waking up mac to record) using my Elgato EyeTV have been missed ...

  • Mac Mini Server upgrading from Lion 10.7.1 to Lion 10.7.2 Freezes in upgrade install reboot. What's wrong?

    After downloading and installing Lion upgrade 10.7.1, my Mac Mini (2010 model)) server will reboot to the Apple logo, but no spinning dial - freezes - requiring re-installation of the 10.7.1 version (which runs well.) Two upgrades are included in the update - Lion Recovery Update and Mac OSX Update. Should these be installed separately of together as they are downloaded? Am I doing something wrong? The machine has been continuously updated since OSX Lion came out so I am not lacking currency in the OS prior to this update.

    @the hatter: First of all: thanks for your assistance !
    What I have is: the MacPro 1.1 (2006)  and a MacBookPro (2009).
    Inside the MacPro:
    (1) Start Disc
    (2) 2nd Startdisk backed up by SuperDuper from (1) (without Parallels disk)
    (3) Media (backup on TimeCapsule)
    (4) TM backup of (1) without Parallels
    (5): USB-Cradle with my last SnowLeo system-hard disk.
    All tests to boot failed with: disk (1) Recovery HD (it is there!) , disk (2), external disk (5), Lion Install DVD , Recovery HD from a USB-Stick (created on my MBP).
    All tests ended with a grey blank screen :-(
    I'm German, so my English has limits.  What do you mean with:
    1. "Pull the bump system drive " ? Should I open my mac and put the old start disk aside ?
    (by the way: I have a backup-drive inside the MacPro from this start disk.)
    2. "Do a clean install of OS". On which disk ? A new one ?
    3. "Put the old working system in FW case". ? FW case ? FW=FireWire ? case? I'm sorry, I do not understand what you mean.
    4. "Update and install". What has to be updated ? The new installed Lion ?
    5. "Import / Migrate with Setup Assistant or Migration Assistant" ? Can't I migrate from "2nd StartDisk" ?
    6. "I am sure there is an uninstaller for Parallels 7 though not whether it can run from another system." I cannot use the uninstaller, as I am not able to boot the Mac :-(
    7. The first OS on the MacPro was 10.4.6 (Tiger) I had Leo, SnowLeo and now Lion. So I believe it will be the moment to build a new clean Lion system.

  • Mac mini server to regular Lion by the Lion USB thumb drive directly?

    Hi,
    I would like to know can Mac mini OSX SL Server change to install regular Lion by the Lion USB thumb drive directly?
    Thank You!!

    Have you reported your problems to Apple?
    BugReporter
    <http://bugreporter.apple.com>
    Free ADC (Apple Developer Connection) account needed for BugReporter.
    Anyone can get a free account at:
    <http://developer.apple.com/programs/register/>
    And/Or
    Mac OS X Feedback<http://www.apple.com/feedback/macosx.html>

  • New Mac Mini server/OS X Lion, no Internet access

    I set up new Mini server on home network, I can access all internal network resources (other computers, airport express, NAS, etc) but cannot get to connect to external/internet sites (apple.com, google.com, iTunes Store, Mac Updates, Mail, etc).  All other Mac hardware on network can access internet (MBP,iPads). What am I missing?

    Double check your DNS settings.  DNS is what translates the web names to IP addresses.  I would double check this.

  • Where is the clear documentation to setup a Mac Mini server OS X Lion?

    We have 3 option to setup a server:
    1-Private
    2-Privat with VPN
    3-Public
    Wher is the step by step information?

    Step by step information for what?
    There is no one-size-fits-all model for Mac OS X Server. It can do about three million and seven different things and there's no way Apple (or anyone else) know in advance what it is you want to do.
    For most people it's a matter of running the initial, basic setup of up the server (IP address, admin accounts, etc.) and then you're on your own to enable/configure any services you want, and that's how the documentation is arranged - a number of chapters/documents based around each service - user administration, file sharing, web serving, etc., etc. It's up to you to decide which services you want, and therefore which documents are relevant to your needs. What am I missing?

  • Error starting wiki server in Mac Mini server with Mountain Lion 10.8.3

    Hi, i've got a problem with my wiki server.
    The service doesn't start!
    It does an error while i try to start the wiki!
    The service can't read the service impostation!
    How can i solve it??
    Anyone with the same problem??
    Thanks!

    here the /var/log/apache2/error_log
    [Fri Jun 28 10:35:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:35:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:51 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:35:51 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:35:56 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:35:56 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:01 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:01 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:06 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:06 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:11 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:11 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:16 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:16 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:21 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:21 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:28 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 10:36:31 2013] [notice] FastCGI: process manager initialized (pid 145)
    [Fri Jun 28 10:36:31 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:32 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:32 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:33 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 10:36:33 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 10:36:36 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 10:36:39 2013] [notice] FastCGI: process manager initialized (pid 196)
    [Fri Jun 28 10:36:39 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 10:37:25 2013] [notice] caught SIGTERM, shutting down
    [Fri Jun 28 10:37:38 2013] [crit] (17)File exists: mod_rewrite: Parent could not create RewriteLock file /var/log/apache2/rewrite.lock
    Configuration Failed
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 10:37:48 2013] [notice] FastCGI: process manager initialized (pid 432)
    [Fri Jun 28 10:37:48 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:28:22 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:28:26 2013] [notice] FastCGI: process manager initialized (pid 31415)
    [Fri Jun 28 16:28:26 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:26 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:28:26 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:27 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:28:27 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:28:30 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:28:33 2013] [notice] FastCGI: process manager initialized (pid 31466)
    [Fri Jun 28 16:28:33 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:43:46 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:43:49 2013] [notice] FastCGI: process manager initialized (pid 33283)
    [Fri Jun 28 16:43:49 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:43:51 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:43:55 2013] [notice] FastCGI: process manager initialized (pid 33322)
    [Fri Jun 28 16:43:55 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:44:41 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:44:44 2013] [notice] FastCGI: process manager initialized (pid 33499)
    [Fri Jun 28 16:44:44 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:45 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:44:45 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8090 (localhost) failed
    [Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8091 (localhost) failed
    [Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8092 (localhost) failed
    [Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:46 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to [fe80::1]:8093 (localhost) failed
    [Fri Jun 28 16:44:46 2013] [error] ap_proxy_connect_backend disabling worker for (localhost)
    [Fri Jun 28 16:44:49 2013] [notice] caught SIGTERM, shutting down
    httpd: Could not reliably determine the server's fully qualified domain name, using server.local for ServerName
    [Fri Jun 28 16:44:52 2013] [notice] FastCGI: process manager initialized (pid 33579)
    [Fri Jun 28 16:44:52 2013] [notice] Apache/2.2.22 (Unix) DAV/2 mod_fastcgi/2.4.6 mod_ssl/2.2.22 OpenSSL/0.9.8r configured -- resuming normal operations

  • Is it possible to install Lion client on to a Mac mini server?

    After seeing benchmark tests on the new Mac mini, the Mac mini server with the i7 processor is obviously much faster. But would there be any issue prohibiting the Lion client from installing on the Mac mini server instead of Lion server?

    I'm afraid it's not possible. Or at least not easily. I've spent the last few days trying to do exactly that, as Lion Server doesn't seem to be able to sleep automatically unlike the client. I've followed all the Apple advice on how to 'remove' the Server components, but it's clear looking at a process list that there's still a huge amount of server stuff still there.
    If you try to install a retail copy of Lion on the new hardware including 2011 Mini, it will refuse to boot from it - this is a deliberate and in my book completely unnecessary and unreasonable restriction by Apple.
    And if you try to re-install Lion using Apple's internet recovery it gives you no choice which you get - it uses your machine details to decide unilaterally that it will reinstall Lion Server as that's what came with the machine.
    The only final thing that MIGHT work - and I haven't tried yet - is to find a mate with a new 2011 Mini or Air, use that to do an internet recovery clean install to an external disk drive, then clone that clean install onto the Mini server. If that works, great, but why oh why did an otherwise excellent company like Apple make this so much harder than it was on ANY of their older hardware? It makes no sense at all. Someone should be fired for this nonsense.

Maybe you are looking for