Lion server on Mac mini server stop responding to ssh and VNC (other services like mail, ical works well)

Lion server on Mac mini server stop responding to ssh and VNC (other services like mail, ical works well)
Version is Lion server 10.7.4
When I attach a monitor to it, I saw all the buttons and menus stopped responding too. I can only push and hold the power button on the box to shutdown.
It only started happening recently.
Anyone has any clue?
Thanks for the help in advance!!!

Found that the second hard drive is broken. I have to go to the apple store to have it replaced.
I had to press the power button to turn the server off for several times, then the broken hard drive went disappeared. After that, I had to disable the Spotlight. Then the server went back to work normally.
Now I made a CCC copy of the primary hard drive, and would like to have the server run on the external raid disk (connected through thunderbolt). Does anyone have previous experience with it? Any expectable drawback or issue with this setup?

Similar Messages

  • Lion OS on Mac Mini Server?

    I recieved a Mac mini server from my brother with Snow leapord server installed.  I have a copy of regular Lion that I would like to install as I dont need the server capabilities.  Every time I try it tells me that I need to buy the lion server part from the app store.  Some of the other posts I've found basically say you shouldn't have bought a Mini Server if thats not what you need, but thats not a solution.
    Does anyone know how to install a regular copy of Lion on a Mac Mini Server without buying the server app which I would not use anyway?  Thanks for the help.
    Ben.

    Can you wipe it and install Snow Leopard on it? That should give you an easy upgrade path to Lion. That would suck if having Snow Leopard server locked you in to only a Lion server upgrade.
    When you say you have a copy of Lion what do you mean? You have it on a flash drive? Its download only but there are ways you can burn it to DVD or install on a flash drive.

  • Removing OSX Lion Server from Mac Mini Server (Mid 2011)

    Hello, fellow apple fanboys!
    I was wondering if anybody knew the sollution to my problem. I have recently purchased the Mac Mini Server, the mid 2011 model, and I wanted to replace the server edition of Lion with the standard one. However, when I plug in my lion installation thumbdrive the system just displays a stop sign, meaning that I cannot boot from it. I was wondering if I could just wipe the Server HD and reinstall standard Lion OS on it.

    I have the 2011 Mini Server and all I did was just not enable
    any server functions.  It works just fine.  Unlike previous
    versions of OSX, the server is an add on to the OS and
    not intertwined with the OS.  So, my suggestion is don't
    bother.  Just isn't worth the time.
    As to why the thumbdrive doesn't work, it is probably a version
    that is older than what the Mini was shipped with.  This is not
    anything new as this is the way OSX has always been.

  • A lot of problems with Lion Server in Mac Mini Server

    I have a new Mac Mini Server and I have a lot of problems.
    The  server application works well for a day, then start to have problem, for example: I can not change the configuration of the share folder, I add a new user but he can not see some folders.
    Then if I login the Mac Mini with another user, he can not see the starting folder and if you open a new folder you see a lot of strange documents.
    Later, with administrator user, I can not login the server application, I put the user name and password but it refuses it (user name and passowrd are correct)
    In the end I also can not login the computer.
    I reinstalled the Lion Server 2 times but nothing change, after 2 days it doesn't work like before.
    I'm very upset, this is the first time in more then 20 year I have a problem with an Apple computer.
    What can I do?
    Please help me
    Thanks

    Turribeach, Thanks for you time.
    1. It was not a question
    3. Yes, i have read platforms, but not supported datasources. Now i see, that BI 11g support as datasource Oracle DB 9.2.0.7 or higher. I am sorry.
    4. I'm using OCI connection type
    Now i recreate Database in Physical schema and answers is showing report data for me! But only from one table, when i use columns from to tables from one datasource, i geting error:
    Error View Display Error Odbc driver returned an error (SQLExecDirectW). Error Details Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 46008] Internal error: File server/Utility/Server/DataType/SUKeyCompare.cpp, line 875. (HY000) SQL Issued: SELECT s_0, s_1, s_2 FROM ( SELECT 0 s_0, "Ora10g"."hierarchy_obj_cust_v"."sort_order" s_1, "Ora10g"."NSI_SCHEMA"."SCHEMA_NAME" s_2 FROM "Ora10g" ) djm
    Edited by: serzzzh on 03.09.2010 3:44

  • Fresh headless install of Lion (client) on Mac Mini (Server)

    All,
    I have a Mac Mini (Server) with two internal drives.  I have successfully been running Lion (client) headless (no monitor or keyboard) for some time since I had originally 10.6 installed and upgraded to 10.7 using the Mac App Store.  For backup I nightly clone my primary internal drive to the secondary drive using SuperDuper.
    I'm having a problem with my Lion install which means that I want to do a fresh install.  I'm stuck as to how to do this.  I've tried:
    1. Boot from primary disk; run Install Lion app; system reboots, freshly installs the O/S, with Screen Sharing on but doesn't wipe the disk, leaving the problem that I'm trying to get rid off.
    2. Boot from the secondary disk; format the primary disk and do a fresh install on the primary disk.  However this doesn't work as once the install is underway and it's re-booted onto the primary disk screen sharing is disabled and so I can't see what's going on.
    (I know that it's possible to use screen sharing during a server install with no username and the first eight characters of the serial number - but this doesn't work with the Lion client installs.)
    Anybody with any ideas?
    Thanks in advance - Jonathan.

    Here's what I would do. It might be handy to run a keyboard and monitor to the Mini at least during this process.
    Reboot into the Recovery partition. Once in, launch Disk Utility. Wipe your boot volume and repartion. Create single partition called 'Server HD'. Now, quit Disk Utility and select the option to reinstall Lion. Install it on your new partition.
    This should work just fine for you.

  • OSX 10.7 Lion (client) on Mac Mini Server?

    So you think OS 10.7 Lion client is going to work on a new Mac Mini Server? With all the problems with 10.6.3 Client not working with a Mac Mini server I'm wondering if 10.7 will have all the correct drivers (the SD card drive, and ethernet, and issue with DVD player app.)
    Anyway, what do you all think?

    Apple has not announced system requirements yet, so anything anyone here can say will just be a guess. My guess is that I can't image that 10.7 won't support 2010 hardware, but again, that's just a guess. We'll have to wait until Apple releases official specifications, which probably won't happen until sometime next spring. Beyond that, there's nothing more we can say.
    The workstation version of 10.6 works fine on the Server version of the Mac mini if you can get a copy of the disk that shipped with the non-server mini. Otherwise, you'll have to wait until Apple ships a newer version of the retail CD, one with 10.6.4 or later.
    Regards.

  • Help! Can't reinstall Lion Server on Mac Mini Server

    To me, the perfect computer is a Mac Mini server (the current model) with one of the HDDs replaced with an SSD. I did this with two Mac Minis three months ago and it went perfectly.
    Well. I bought a third Mac Mini and have attempted to do the following:
    Carefully opened the case, removed the top parts and memory.
    Removed the top 500 GB HDD
    Replaced it with a OCZ Vertex 3 SATA III 2.5" SSD
    Booted from a SD Card with the recovery system on it
    Formatted both SSD and the other HDD, ensured they have the GUID boot block needed for Apple booting
    What happened was...a total let down. It would start to download Mac OS Lion Server then tell me, "Could not find instalation information for this machine. Contact Applecare." If I went and re-formatted the SSD and tried it again, often it would go past this section, actually starting the download, but then I'd get "Can't download the additional components needed to install OS X."
    I verified all connections were solid. Putting the original HDD back caused the machine to boot fine and let me set up Lion Server for use (oddly, even though I'd formatted one of the two RAID drives, but whatever). I am doing the exact same thing I did before successfully, only with an OCZ drive this time instead of Other World Computing. Either Mac Minis hate working with OCZ SSDs, or I made some mistake somehow (I'm pretty sure I didn't), or else Apple has flipped a switch forbidding software restoring of Mac Minis that have been "altered" from factory state. If so this will be a huge problem for Apple. I will make sure the major Apple blogs hear of this, if this is the case.
    Can anyone suggest what else I can try to get this to install? If I can get a spare OCZ SSD so it's exactly the same as my previous successes. Otherwise I don't know what else to try.
    (I guess cloning the system from one of the Mac Minis that works would be a possibility, though I want to solve this.)

    Found that the second hard drive is broken. I have to go to the apple store to have it replaced.
    I had to press the power button to turn the server off for several times, then the broken hard drive went disappeared. After that, I had to disable the Spotlight. Then the server went back to work normally.
    Now I made a CCC copy of the primary hard drive, and would like to have the server run on the external raid disk (connected through thunderbolt). Does anyone have previous experience with it? Any expectable drawback or issue with this setup?

  • Transferring OS X Server From Mac Mini Server To Mac Pro

    Hi,
    A few months ago, I bought a Mac Mini Server for my business. We've now got a Mac Pro that we'd love to install OS X Server onto, and then install Snow Leopard onto the Mac Mini Server (thus making it, in effect, an optical drive-less Mac Mini) for a few reasons I won't go into here.
    I thought it might be as simple as to put the OS X Server disc into the Mac Pro, install and then migrate the settings across, and then format the Mac Mini Server and install Snow Leopard. But when I put the CD into the Mac Pro, I got a message saying that OS X Couldn't Be Installed On This Computer.
    Is the OS X Server disc that comes with the Mac Mini Server tied to the Mac Mini itself? Can it not be transferred? Even if we retain ownership of both machines, and have a valid license for Snow Leopard to be installed onto the Mac Mini Server? Or is this error message relating to something else?
    Thanks in advance,
    phil

    Try to put the MacPro in FireWire target disk mode and install the OS, or take the disk out and using an enclosure install. Do not clone, it will probably fail due to hardware differences. Try new installation not being plugged in the same network as the mini, setup DNS and transfer OD archive and other settings from the mini.
    Regards
    Kostas

  • 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

  • Mac Mini Server to OS X Lion

    All,
    I am trying to get my head around the steps that I would need to do in order to upgrade my Mac Mini server that is currently running OS X 10.6 to OS X 10.7 Lion.  I have already purchased the $29.99 Lion upgrade for our other machines in the house. 
    Do I have to install Lion on the Mac Mini server and then spend $49.99 to upgrade the server tools?  Will the existing server tools (that came with the old OS X 10.6 server) still work with Lion?  Just trying to decide if spending another $50.00 to upgrade the server is worth it.  I also worry about breaking things during the Lion install.  I expected that there would be a all-in-one pack to install that would take you from 10.6 server to 10.7 server.
    Thanks in advance for any info people can offer.
    Matt

    Upgrading to Lion Server is a two step process in that the server part is a separate purchase and install.  My understanding is that during the upgrade of SL Server, you run the Lion installer, then you'll be prompted for to purchase and download the Server add-on, if the installer does not already find it in your Applications folder.  I'm not sure, but I don't believe you can use the old Server Tools on Lion.  And I don't think you can "only" upgrade a SL Server to Lion without the Server add-on.
    ...I also worry about breaking things during the Lion install....
    As always, backup, backup, backup.  Clone your existing SL installation to a separate hard drive.  That way if something does go wrong, it's relatively painless to restore the cloned image.  Without a clone, "fixing" a bad upgrade can be quite painful, if not impossible.  (If you're going to rely on a Time Machine backup instead, then don't enable Time Machine in Lion until you're sure everything's working.  Or disconnect the Time Machine Drive.  That way you can ensure that you have a Snow Leopard only Time Machine backup, which you can restore with your original disks that came with the Mac.)

  • Mac mini server to non server lion upgrade

    I was just curious if I could install a copy of non-server lion on my mac mini server so i could get the new multi-touch gestures but still keep the same snow leopard server apps. I've heard mixed things about lion server's weaker performance so I was contemplating if I could do this.
    Thanks

    Here is what I'm attempting to get around that 'stall'.
    I created a Snow Leopard partition on a bootable external USB hard drive using a second Mac that supports booting from the retail SL disk.  (This is where the server version of the Mac Mini won't work.  You can't boot from a Snow Leopard retail disk).
    Now I've booted my mini (running SL server) with the external hard drive.
    I'm downloading Lion client from the Mac App Store.
    My plan is to select the first internal hard drive as the destination for the Lion install as soon as the download has completed and the Lion install program asks me where to install Lion.

  • Mac Mini Server setup with airport express

    I have had issues trying to setting up mac mini server on my network. I wonder if my current hardware is the problem? At present I have a Thomson Router plugged into an airport express which broadcasts wifi for my house. I have been connecting to my wifi with my mac mini server. Despite running server assistant and setting up a DNS server in Mac Mini server no clients are able to connect to the DNS server (i.e. dig command works on server but not on clients). I found reference somewhere on the internet to the fact that the mac mini server must be plugged into the router via ethernet for it to be setup properly.
    Could this be the cause of my problems? Is it true?

    Just to clarify this is an airport express and not airport extreme therefore I am reliant on a wireless connection between my mac mini server and the airport express.
    The model of the Airport device here is largely irrelevant.
    Currently my Thomson router serves out an address of 192.168.1.67 to airport express router.
    Do you have any control over the gateway router?
    The airport express is configured to share out a single IP address
    Double NAT (which is what you have here) will cause you problems. Get rid of one layer of NAT.
    The airport express gives out addresses in range of 10.0.1.2-10.0.1.202 with 10.0.1.1 being the address for the airport express and 10.0,1.201 being assigned via DHCP to the mac mini server (using its MAC address to reserve the address)
    Within the private blocks, the IP addressing organization is your decision.
    The DNS server is set on the airport express to 10.0.1.201 (i.e. my server).
    OK. (I usually pick smaller numbers for more important boxes, because I tend to type addresses for those boxes more than the addresses of the boxes over in DHCP-land. But again, this is your call.)
    I guess I wondered if something funky was going on with server assistant during the setup. A post I read somewhere (I've lost the link) was someone in an identical situation who had issues and said that apple had stated that he need to be directly connected to the router by ethernet cable to get things working. I wondered if this is the issue. An airport express does not have a spare ethernet port to plug into so I wonder if I need to buy a wireless router with built-in ports i.e. airport extreme (expense+) or something similar.
    I'd probably switch the box to access point, but that presumes you can get (more) control over the gateway router.
    I can access by Thomson router but I able unable to change the DNS servers that it provides (set by my ISP) from the GUI. I'm sure you could probably do it from the commandline but I think this is beyond me. I did wonder if that is what is causing problems
    Talk with the ISP. You'd prefer to have the device switched to a bridge, if that's feasible. If not, then you're going to have to work within the confines of the particular model.

  • Mac Mini (mid 2011) ram slot has failed: Any others experiencing?

    This seems similar to this problem, mentioned in a number of threads covering MacBooks, best described here: MacBook Pro loses access to 1 memory slot upon shutdown or reboot in OS X 10.8.1
    I'm having the same issue with a Mid-2011 Mac Mini (purchased June 2013).  As in that linked tread, overheating after OS upgrade (in my case , Mavericks) seems to be related.  I had constant crashes at sleep beginning about three weeks ago, and three tones at boot.  For about two weeks I could get it to reboot by unplugging and giving it some time. Until today. Cleaned. Tested both chips in both possible slots, but will always get three tones when either chip is in top slot, fine when that slot is empty. Hardware test appears to just ignore an empty slot, so really not helpful (and won't boot with filled slot).
    It appears the only real fix is a new logic board, which appears is almost as expensive as buying a new machine.
    I'm not going to get into "loosening screws" as suggested in linked discussion, but that may work for a powerbook.
    It does sounds like heat related warping. I saw early heating problems with this after 10.9.5 upgrade.  Ended up building a special vertical stand (Mini's venting is rather poor) and installed "Temperature Monitor" by Marcel Bresink Software, which I recommend, and uninstalled some things (including killing a Mac update process that was running constantly) .  This got the heat under control, but it looks like the damage was done. Now I'm running on one 8gb memory chip, which dramatically shortens the life of the machine.  It won't be a candidate for a Yosemite upgrade coming shortly.
    Must say I'm pretty disappointed in "Apple quality". Had similar experience (repeated shorts of logic board, replaced 3 times) with a MacBook c.1997, when Apple Co. was looking like it might not survive, and lots of folks were having such problems.  But at least then they would repair it for free. Given the premium price (without premium quality), I think this will be my last Mac, after having started with a Plus in the 1980s.

    Mac Mini mid 2011, installed 2x 4GB memory when first got this machine, has worked well till this year 2015 when it slowed way down and I found memory slot #2 was not working.  I swapped the cards and also reinstalled the original mac memory, still only half of the memory is detected in one slot.  It is always the same slot, not dependent on the memory card.  A mac mini which never gets moved.  Mar. 2, 2015

  • 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 has suddenly stopped seeing one or the other bluetooth devices! Batteries have been changed and they will connect to an older Mac mini. Server will now only see one or the other but not both.

    My Mac mini server has suddenly stopped seeing one or the other bluetooth devices, either the wireless keyboard or the mouse( both apple products) have tried new batteries, at first it was the mouse that stopped responding, but upon rebooting the computer now the keyboard will not respond and the mouse works. Both work fine on an older Mac mini that I hooked back up to check.

    There is absolutely no reason why they should not bothe be able to connect to your WiFi network. The easiest place to start would be to reboot your router. Unplug it for about 30 seconds and then plug it back in again. I would also restart both the iPad and the iPhone.

Maybe you are looking for