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?

Similar Messages

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?

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.

Please help. Can no longer connect to my Mac Mini Server

Up until two days ago, my iMacs were connecting to my Mac Mini Server normally. All of a sudden I could no longer transfer files without being prompted to type my password. Enter password and nothing happened, then got an error message stating that I don't have permission to do that. Now, a day later, no acces to my server. Has anyone ever experienced this? Can anyone please help? I've read the Mac mini booklet but doesn't have any troubleshooting info. Thanks in advance.

Hello MrHoffman,
Thank you for the advice. I went into Terminal first and typed in your command and this is what resulted:
Last login: Fri Jan 24 22:39:08 on ttys000
serverX:~ serverx$ sudo changeip -checkhostname
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
Primary address     = 192.168.1.7
Current HostName    = serverX.private
The DNS hostname is not available, please repair DNS and re-run this tool.
dirserv:success = "success"
serverX:~ serverx$
serverX:~ serverx$
I'm not very experienced with programming or coding, but this message seems to indicate that there's a problem with DNS just like you noted. I've highlighted the note in bold...What can you make of this or the logs from console below?
Below is what I found in Console:
1/24/14 8:55:08 AM          com.apple.launchd[1]          *** launchd[1] has started up. ***
1/24/14 8:55:19 AM          com.apple.launchd[1]          (com.apple.NotificationServer[73]) Suspicious setup: User "jabber" maps to user: _jabber
1/24/14 8:55:25 AM          edu.mit.Kerberos.kadmind[58]          kadmind: starting...
1/24/14 8:55:27 AM          org.jabber.jabberd[53]          ERROR: Could not create /var/run/jabberd: Permission denied
1/24/14 8:55:27 AM          com.apple.launchd[1]          (org.jabber.jabberd[53]) Exited with exit code: 1
1/24/14 8:55:27 AM          com.apple.launchd[1]          (org.jabber.jabberd) Throttling respawn: Will start in 1 seconds
1/24/14 8:55:28 AM          org.jabber.jabberd[130]          ERROR: Could not create /var/run/jabberd: Permission denied
1/24/14 8:55:28 AM          com.apple.launchd[1]          (org.jabber.jabberd[130]) Exited with exit code: 1
1/24/14 8:55:28 AM          com.apple.launchd[1]          (org.jabber.jabberd) Throttling respawn: Will start in 10 seconds
1/24/14 8:55:28 AM          com.apple.printservice_LPR_mDNS_Plotter_Epson_7600[70]          Registering Service Plotter Epson 7600._printer._tcp port 515 TXT txtvers=1 qtotal=1 rp=Plotter_Epson_7600 pdl=application/postscript ty=$null$
1/24/14 8:55:28 AM          com.apple.printservice_LPR_mDNS_Plotter_Epson_7600[70]           8:55:28.703 Got a reply for service Plotter Epson 7600._printer._tcp.local.: Name now registered and active
1/24/14 8:55:30 AM          org.jabber.proxy65[52]          /System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python /twisted/persisted/sob.py:12: DeprecationWarning: the md5 module is deprecated; use hashlib instead
1/24/14 8:55:30 AM          org.jabber.proxy65[52]            import os, md5, sys
1/24/14 8:55:30 AM          org.jabber.proxy65[52]          /System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python /twisted/python/filepath.py:12: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
1/24/14 8:55:34 AM          com.apple.launchd.peruser.501[174]          (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/24/14 8:55:35 AM          ServerScanner[200]          Preference says we shouldn't scan
Thanks!

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

How can I create RAID 1 on Mac mini server just now from box.

I bought my Mac mini server two days ago and decided that 1Tb + 1Tb HDD are very good for RAID 1 (mirroring).
Thinking - doing ... Open Disk Utility, try to change and create RAID. Nothing. Try to reinstall OS X - recovery part are on disk all time.
Does anybody can help me to create what I want and how to do this with minimum energy. Thanks a lot.

Start from an Internet Recovery which boots you into it's own Recovery Partition. From there use Disk Utility to put your 2 drives into RAID 1. Reinstall OS X from the Internet Recovery once you have done that and install everything else as you need to.
Be aware that RAID volumes do not have their own Recovery Partition so you will need to either have an external drive with an RP to boot into else you will need to use Internet Recovery each time (which is around a 650MB download).

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.

Any help with a Time Capsule install and Mac Mini server screen share?

Installed a Time Capsule, now I can't access my mac mini server. I see the files/folders, but cannot screen share with the mini from my macbook pro. Any help? Error below when trying to use the "screen share" button in Finder. Macbook Pro and Mac Mini are using Mountain Lion 10.8.2.
Connection Failed Error: Please make sure that Screen Sharing (in the Sharing section of System Preferences) is enabled on the computer to which you are attempting to connect. Also make sure your network connection is working properly.
Please help, I'm really stuck on this one!

Try removing the TC and see if the problem disappears.
Screen Sharing has a checkered histroy looking back through the posts..
https://discussions.apple.com/message/16026896#16026896
There are many discussions about failing after changes in Lion.. I haven't seen the equivalent ML yet.. the TC may not be root cause, just the initiator of the problem.
It could be the BTMM associated with the TC.
https://discussions.apple.com/thread/4160415?start=0&tstart=0

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.

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.

Can I install Snow Leopard on Mac Mini Server hardware?

What I would like to do is buy the Mac Mini Server but I don't need the server OS. I want the desktop OS on the Mac Mini Server. Will installing Snow Leopard on the server hardware be just like installing it on a regular Mac Mini?
Or should I just wait and see how Lion shakes out?

Thanks Indy, I already had proceeded the installation according your tip. Just an objection related to the updates: I was able to install the OS updates only while in target mode, as when I made 2 attempts to update the version 10.6.6 to the current one (10.6.7 - the combo one and the MBP version too) it was not permitted. I had to plug the FW cable into the MBP again and update the Mini's OS (using the special MBP version of 10.6.7) in target disc mode. I want to use the Mini as a media server and intend to install Windows 7 on the other HD which now hosts the server OS. However, according to one poster (Sven G) there are some problems (I don't know exactly what they are) related to Boot Camp software. Have you any information about these problems?
I have maintained both OS (standard and server) living side by side on the Mini, is there any problem with that?
Again many thanks, you were succinct, right to the point, and your tip just proved itself correct.
Cheers
Marola

Can't log new user onto Mac Mini Server

I can't log a new user into Mac Mini server. Have added the user to the Workgroup Manager, and am now trying to use the password created there for log-in on user computer. Any advice?

Do you have Server Access Control Lists (SACLs) configured? If so, you will need to add this new user to the appropriate SACLs before it can connect. As an example, when I create new users, I need to add them to the File Sharing SACL or they never see any available shares on the server.

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

Can't Install Lion on a Mac Mini i5 in no way

Hi, i have got a mac mini 2011 (i5, 4gb ram, 500gb hdd) recently...
Im trying to boot from a dvd with OS X Lion but im getting a prohibitory sign, i have learn lot of posts on internet about that but no usefull solution.
I have tried botting from a usb flash drive, but it doesn't work...
I have tried downloading the system using the recovery client on the mac mini... but download process die at the middle everytime i start it.. so...
I don't know what to do... i read that OS X Lion 10.7 cannot boot on this kind of mac mini (and macbook air), and i needed to do this with a more recent version like 10.7.2 or 10.7.3... so i've done it with 10.7.3, but the prohibitory is still appearing..
I don't know what's the problem.. i have got OS X Lion clean install on my macbook pro (2010) without problem.. but i cannot get it working on the mac mini....
Any help please?
Regards

what kind of hardware fault are you talking about?
Memory or logic board.
if it was installed, what would be the problem (for you) to be installed again?
I'm not sure what you mean. I agree that if the machine is in working order, you should be able to install Lion on it. But apparently you can't, despite trying in at least three different ways.

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

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

Similar Messages

Maybe you are looking for