OSX Server 10.3.4 updating?

I am a Noob at OSX Server. Client currently is running OSX Server 1.3.4 on an older G4. Minimal use, just a few sharepoints, about 10 users.
Q: Can I update (it) to 10.3.8 (or 10.3.9, i forget) by using the assumed Software update feature, like in OSX Client?
After this, I want to get them up to 10.4.x Server also. Any tips or caveats to watch out for, greatly appreciated.
Thx,
Chotty
PowerMac G4 Mac OS X (10.3.4) OSX Server

I am a Noob at OSX Server. Client currently is
running OSX Server 1.3.4 on an older G4. Minimal use,
just a few sharepoints, about 10 users.
Q: Can I update (it) to 10.3.8 (or 10.3.9, i forget)
by using the assumed Software update feature, like in
OSX Client?
Yes. Run 'Repair Permissions' in Disk Utility before and after system updates (just a good precaution to take).
After this, I want to get them up to 10.4.x Server
also. Any tips or caveats to watch out for, greatly
appreciated.
Personally speaking, I have always done a new install between major updates rather than over-writing old ones. You have to purchase a new system installer so an additional expense (in time) to do a clean install has always seemed a good move to me. Particularly if your existing install is relatively simple then it should be straightforward. Preferably, I would undergo a couple of 'run throughs' on a test machine (or firewire disk partition) before undertaking the real replacement - just to make yourself familiar with it (probably not too much changed in your case). Good idea to make a disk image of the old one prior to overwriting it or even better, swap out the existing system disk which is probably as old as machine ? for a new one and keep old one, just-in-case. However, watch for probable 128G max size disk for old G4s if you replace existing.
See following pdf doc for updating 10.3 directly to 10.4...
http://manuals.info.apple.com/en/Migrationv10.4_2ndEd.pdf
-david
Server 10.4.8

Similar Messages

OSX Server 2.2.2 update broke my websites

I updated to server 2.2.2 yesterday and my owncloud website on my server stopped working. It was so frustrating I restored via time machine. Is there something I should check so I can update again?
Information of my setup.
owncloud 5.0
using osx server website feature pointing to folder.
using ssl 443 port for my website.
I have port 80 open as well but I have own cloud redirect to ssl.
if you browse diectly to my server ip it brings up the osx server webpage.
i have my computers point to my server ip for dns
my dns server routes my local website dns to my local ip of server (had to do this because I was getting NAT loopback issues)
all other dns should forward to opendns
Please help, thanks!

I have the same problem. Even trying http://127.0.0.1 from the server itself still the server cannot be found. My system log however is now generating what looks like an error from the server:
Sep 20 20:09:34 home com.apple.launchd[1] (org.apache.httpd[69048]): Exited with code: 1
Sep 20 20:09:34 home com.apple.launchd[1] (org.apache.httpd): Throttling respawn: Will start in 10 seconds
This repeats constantly until the server is stopped.
I'm guessing there is a permissions issue somewhere that 2.2.2 has now broken. No idea where to start to resolve.

OSX Server 3 Failed to Update Services, Reboot Fails now

I upgraded my Mini Server to Mavericks, then installed the Server 3 upgrade (paid $19.99). The installation hangs during "Updating Services" and most windows become unresponsive. Remains in that state for hours. I lost patience and rebooted from a remote ssh session. Now the server doesn't reboot. I restored back to 10.8.5.
Has anyone encountered and resolved this condition?
To be precise, during the Update Services process, the gauge stops at the "d" in Updating... label.

I had the same problem. Finally found a solution that appears to work fine.
Using any free app uninstaller, remove "server" from your applications and remove it and all of its related files.
Empty the trash.
Restart your Mac holding down the 'shift' key. This puts you in safe mode.
Go to the Apple app store and re-download the "server" app.It will ,et you do this, becuase it cannot find a copy of the app anyplace on your computer.
After downloading and installation, configure the 'server' app following its commands.
Restart as usual .... presto ... works!
You can then re-configure as required.

How to customize mavericks' mac osx server apache configuration?

I have installed Mac OSX Mavericks Server and I would like to add some features to the Apache Server (gitolite, redmine, etc.) I've started with updating the httpd_server_app.conf file in/Library/Server/Web/Config/apache2 but unfortunately it has been overwritten by the server to its default. Maybe because I've updated something in the UI, or an update occurred... Anyway, I would like to know how can I update the configuration file in a permanent and persistent way, and still benefit the OSX Server UI and/or updates...
I've probably missed the big : "Put your own things here:" label...
PS: By the way, I wish to modify some of the current configuration, not only adding things...

If you scroll down through the standard httpd_server_app.conf file you will eventually find a section full of include options. (Some of which are commented out.)
One of these enabled include options is for /Library/Server/Web/Config/apache2/other/*.conf
The implication of this is that if you put your own httpd.conf file in the 'other' directory then any settings you put in it will be included in your Apache configuration and will not be over-written by Apple's Server.app software.

Update my mac osx server 10.6.8 to mac osx server 10.8

How to go from osx 10.6.8 (server) to osx server 10.8?
Do you have to install osx 10.8 first?

Yes. First purchase and install Mountain Lion ($20) and do all of the updates and then purchase and install Server (also $20).
Clinton

Heartbleed update for OSX Server on the way?

Hi all. Just curious about the Heartbleed situation as it relates to OSX Server. Any insights?

MadMacs0 wrote:
MrHoffman wrote:
LogMeIn is reporting the code as vulnerable.
Right, that was the most detailed information I could find.
I just wanted to let you know that I did research the inards of the effected software and found nothing.
What is effectively being discussing here is also known as reverse engineering. If the text strings related to OpenSSL were changed or were expurgated from the tool or have been obfuscated, then grep or strings or related won't find the keywords, and it'll be a false negative.
If OpenSSL is more overtly included in the package, then the grep and strings and find commands and related should find evidence of OpenSSL.
Check for updates from the tools and packages that use SSL/TLS, and run the tests, and upgrade to current.
Also review the network devices in use for updates, and particularly if there are any outward-facing or remotely-accessible HTTPS or SSL connections on any of those devices.
There's no easy way to do this. This is analogous to the problems that anti-malware scanners have, too; finding needles in haystacks.

OSX Server Caching iOS updates

Hello,
I have a question regarding the OSX Server Caching feature, the documentation states that this feature will cache all updates(including iOS) which is great for the company i work at.
However, the biggest issue is that the server itself does not download or cache the iOS updates, if i were to add the *.ipsw files manually to "~/Library/iTunes/iPad Software Updates/" for example the server will NOT cache these.
If a computer in the network downloads the IPSW via iTunes, the server will not cache this.
If i were to restore a device in iTunes on the server and iTunes has to download the update, it is NOT cached.
We're trying to have all IPSWs ready to go from one device instead of 7-10 devices individually downloading each and every update from Apple but we cannot find a solution for this.
If anyone knows a good solution, that would be great.

The answer is here:
OS X Server: Caching service doesn't cache the iOS 8 update

Websites were deleted from configuration after Maverick OSX Server Update

Websites were deleted from configuration after Maverick OSX Server Update. My subversion access was also overwritten and no longer works.

if that was a bug report, then Apple might or might not see it here. There's a Provide Server Feedback in the menus of Server.app, if you'd like to let the Server.app folks know about the upgrade problems I've encountered.
If you're looking for help resetting the web sites (I'm not clear if you're reporting a bug or looking for help with this), then check Server.app for where the files should be (the default location is under /Library/Server/Web/Data directory) and see where your current sites are stored in the file system, establish the Site via Server.app (usually with a directory under the /Library/Server/Web/Data path) and move the contents over to the new location.
As for the Outlook comment in your footer, Microsoft Outlook also generally needs to have the FQDN requirements removed in the SMTP HELO processing. Outlook doesn't send that, and the default Postfix configuration will reject those connections as spam. Here's a discussion of how to do this. (I don't see a path to the HELO processing via sudo serveradmin settings mail:postfix commands.)

Connection reset by peer when trying to update to OSX server 3.01 on 10.9

connection reset by peer when trying to update to OSX server 3.01 on 10.9. PLease help

Assuming your network is working for other activities, and it's just the Mac App Store that's failing...
Try restarting the download within the Mac App Store.
Failing that, restart Mac App Store and try restarting the download again.
Then failing all that, I'd close Mac App Store, reboot the system, and open and try the Mac App Store download again.
Here are some details on the Mac App Store (including how to cancel and restart downloads), and here are the App Store Troubleshooting suggestions from Apple.

TV don't work with OSX Server software?

Everything worked great BEFORE I updated our MacMini Intel to OSX Server software, now iTunes can't find the recent found Apple TV. And therefore the connection is gone and the syncing don't work anymore.
Any work-around or suggestions on how to solve this?
Or do I have to revert to previus userversion of OSX to make it work again?
Is there a limitation built into OSX Server software or is there maybe some kind of firewall / preferences etc that needs to be adjusted? (The built in firewall has been disconnected.)
FYI:
All apps are up to date. The Mac Mini + Apple TV is on my local network at home and I'm trying to make it my family's digital hub for all family-related media.
MacBook Pro CD2 & X-servers Mac OS X (10.4.9)
MacBook Pro CD2 & X-servers Mac OS X (10.4.9)

1) I've not tried to reset ATV from scratch. But it works fine on other Mac's on the network (sharing).
2) Security options, yes I belive so to. I've followed all instructions and opened all ports I've seen mentioned i apples Knowledge database / support. Still don't work. Maybe I've missed some ports...
3) YES! It works fine sharing the MacMinis lib over the network.
4) Today I also tried to reinstall iTunes. But no luck.
Any mor suggestions anyone? Thx
I really wanny solve this, otherwhise my ATV is pretty useless for me...

File locking with OSX Server & Microsoft Word

We have a small office LAN based on a Airport Extreme bases station. Periodically Microsoft Word reports a break in connection to the shared folder where we store documents to get disconnected. When that happens and the user reconnects to the share, the user gets the file read-only message for the Word document that was open at the time.
I have found that in order to clear the read-only flag, I have to restart the server and open the Word file on the server with the ID of the user who was editing the file on the remote computer. Only that seems to clear the file locking that causes the file to be read-only.
I cannot figure out a less drastic way to release the lock file. I don't see any hidden temp files in the same folder as the document that is locked for editing found by ls -a or in the root direction of the shared folder in the .TemporaryItems/folders.<UID> that seems to be holding the lock.
I have run chflags nouchg <Word file> from Terminal, but that seems to have no effect either. I also used xattr to see if there were any locks held that way, but I don't see anything that way either.
File sharing to Macs only, which are configured just to use AFP through OSX Server.
Does anyone understand how the file locks of Word documents can be released directly with out restarting the server?
I should add that the underlying problems seems to be WiFi related. The behavior is that the WiFi connection seems to break long enough that the shared volumes disconnects. Outlook also causes a break. This behavior seems to have started with 10.9 and the purchase of new Retina Display MacBook Pros. I turned off AppNap on the Office applications but that is not clearly helpful. I also have been told the problem seems more likely to occur when Word is open in the background and another program like Outlook is in the foreground.
Any suggestions appreciated.

Apple write an operating system and also produce file sharing software as part of that to be used as a file server. Apple provide documentation for third-party software developers on how they should write software to work with Apple's software and also give those developers early access to new versions so those third-party developers can test and if needed make adjustments and issue updates to cope with any Apple changes.
Some third-party developers are good at dealing with this, some are bad, and some totally ignore what Apple does and give the impression they don't care if their product works properly or not. I think we can all judge where Microsoft sits.
It appears Microsoft have never paid any attention in particular to how Apple expect file-locking to be handled when accessing files on a Mac server. There have been problems for years and years and years with Office. Two other problems I have seen which seem different to yours but probably related are -
With Office documents it is supposed to be possible for more than one person to edit the same file at the same time, consider it a miracle if this actually works
With Office in particular Word, there is an auto-save function, unfortunately the way this seems to be implemented it seems that Word creates a new temporary file each time it auto-saves the document and keeps all the previous temporary files open still, this eventually means potentially over a hundred temporary files are open - just for one Word document and you can then hit a limit on the total number of files you are allowed to have open at the same time. At this point further auto-saves fail, and you also encounter great difficulty doing a real full save of the document.
I do not hold Apple completely blameless over this issue, it is likely their file-locking implementations change too often, and have inadequate documentation, however even considering this a company the size of Microsoft with the amount of sales (and profit) they derive from Office for the Mac has no excuses at all for failing to put the effort in to resolve any such clearly critical problems.
We could go on and on about other areas where Microsoft don't play by the (software) rules. Even in Windows Office does not obey the standard print dialog rules Microsoft specified themselves!
Unfortunately not only is Office for Mac upgraded infrequently, but even when new paid for upgrades are released Microsoft have a history of still not fixing bugs. It goes without saying that a mere free update is even less likely to actually fix a bug, typically such free updates only address security issues. The next version of Office is going to be Office for Mac 2014 see http://www.macworld.com/article/2106643/microsoft-will-release-a-new-version-of- office-for-mac-this-year.html
One area I confidently predict Microsoft not to resolve in Office for Mac 2014 is that fact that Word for Mac still does not support right-to-left languages like Hebrew and Arabic. This is despite the fact that OS X itself has supported this for years and years, and despite the fact other Mac programs support this including the free TextEdit and Pages - both of which can read Word files. Some people may remember that at one point the Israeli Government temporarily banned all Microsoft software over this issue. See http://apple-beta.slashdot.org/story/03/10/15/2215249/israeli-government-suspend s-microsoft-contracts This issue goes back over TEN years!!
I note that Microsoft has now taken their OfficeForMac blog offline, probably due to the weight of criticisms. I would not say it is due to out-right anti-Microsoft hate, that war ended long ago. We just want products that work. I myself do use Microsoft products, even at home - where they are the best solution, so I use Microsoft Media Center for example. Sadly this is now being neglected by Microsoft.

Help needed with OSX Server 10.5.8

We're running a headless Xserve (RackMac3,1) with OSX Server 10.5.8 that did its job flawlessly.
Now we want to update the Perl software from 5.8.6 to 5.20.0 or newer. After downloading the suitable version from CPAN we tried to install, but get the following msg:
Uh-oh, the C compiler 'cc' doesn't seem to be working.
You need to find a working C compiler.
Either (purchase and) install the C compiler supplied by your OS vendor,
or for a free C compiler try http://gcc.gnu.org/
I cannot continue any further, aborting.
Is there a way to install the missing tools remotely via the command line (SSH)? A step-by-step recipe would be most welcome.
- Harald -

RackMac3,1 is PPC/G5 processor so you are not going to have an easy time with this. Perl 5.2.20 is bleeding edge (OS X 10.10.3 comes with v5.16.3).
I would leave Apple's installation of Perl, etc. on the server strictly alone and install MacPorts:
The MacPorts Project -- Home
and work from there. You aren't likely to get a step-by-step recipe because its not an exercise a rational person would chose to spend time on.
Have you considered rewriting whatever features in your code require Perl 5.2.20 than to upgrade your server? Or buy a new server, you could probably pick up a Mini for about $200.
C.

Server File Sharing unstable on mac and windows network on Mavericks and OSX Server 3.0

Since I've updated our mac mini server from Mountain Lion and OSX Server 2.X to Mavericks and OSX Server 3.0 we are having sharing issues with Windows (7 and 8) and OSX Mavericks users, not being able to access files on the mac mini server.
What I've notice is that OSX Serer 3.0 stop working and I have to restart the Mac Mini Server to make things start working again.
This was not happening with Mountain Lion and OSX Server 2.X.
On the Windows and OSX users what happen is the computers keep trying to connect to the server and are not being able to open or copy files. Again this is intermittent, and I suspect it might be a OSX Server bug.
Any one having the same problem or can give us and advice would be great help.
Thanks.
Andre Tenenbaum

I too am having this exact problem as well as a few of my network administrator contacts that have gone through the Mavericks / Server 3 upgrade.
It may be worth noting that before the upgrade I had run a mac mini server (core 2 duo) that never had any unintentional downtime, and the current mac server had never gone down or lost connection so I know it has nothing to do with user or network configuration.
NAS server hardware:
- Mac Mini core i5
- 16 GiB ram
- Promise Pegasus Raid5 external drive (thunderbolt)
I am NOT running time machine as the backup.
Everyting posted above is occuring although the rate at which my users lose acces is sporadic. Sometimes the server will stay up 24-36 hours and sometimes it will only stay up for around 4. Every user, every group loses acces AT THE EXACT SAME TIME EVERYTIME to EVERY SHAREPOINT...all of my local users as well as my remote users. All of my users are on Windows machines (mostly win7, but a couple of XP and 8 users as well). The share is accessed via a mapped drive using the format x.x.x.x/share and I have had 0 issues with getting users connected. The problem is 100% keeping them connected. When the users lose access the get the "drive cannot be accessed" error on their end, however when I check the server 3 app, it still shows all users connected and I have let it run for a few minutes and the idle times do change.
I also cannot see any spikes in the Activity monitor that might indicate a memory strain issue on the server side, but I assume that is because I am not watching the Activity Monitor at the moment everyone loses access.
Let me say that the SMB2 protocol does work much better when it actually works, much faster, but intermitent connectivity is a VERY SERIOUS ISSUE and has resulted in several corrupt files for my workers already. Also, because I was one of the unfortunate people that had the upgrade lock up on me and I had to restart it, I lost my 10.8.x recover backup and so I would have to do a clean install in order to restore my server back to its original state. I am also hesitant to do this because I would most likely only be able to download the Server3 app from the app store and I have not heard from apple or any other power user group on whether the bug is with the app or the OS.

What are the right DNS records to host more than one site on OSX Server (ML). My conf in Server.app looks right but one of my sites lands on the default server. Any suggestion?

I started using OSX Server on Mountain Lion a few days ago and it looks promising.
I do however measure my ignorance in DNS matters...
I defined two websites in addition to the the Default Server, so I have three names to deal with.
For argument's sake
- www.main.com is the default site
- www.sitea.com is the first site
- www.siteb.com is the second site
I define a virtual host for www.sitea.com and another for www.siteb.com
The resulting apache conf is what I would expect, I am pretty sure it is correct.
So I modified my DNS entries (they were A records) to point to my new OSX Server.
My result is:
- www.main.com shows the default site
- www.sitea.com shows the first site
- www.siteb.com shows...the default site
Any ideas?
Cheers

Thanks MrHoffman!
My problem ended up being a name but not in the DNS!...In Apache.
Your information allowed me to rule out possibilities and zoom in to the culprit faster.
I just report here the conclusion hoping it can help someone else.
When I installed OSX Server last week, I had in mind to principally run siteb.
During the initial install, this is what I must have entered and then forgot about it.
Then I defined my virtual hosts sitea and siteb and realised my machine was called siteb and changed its name to main to avaid a name collision. At which time I remember OSX Server telling me that changing the name could have consequences...But it apparently went ok, and it did except for one little thing.
The consequence was this:
in the main configuration file /Library/Server/Web/Config/apache2/http_server_app.conf the ServerName directive had remained siteb (instead of main). I manually updated it with TextEdit (could do vi from bash, its the same) and replaced siteb with main.
There is a way to detect it.
In Server.app, there is a "logs" panel, which displays all sorts of logs for everything including the websites.
Each website's logs are presented as "access" and "error" logs. The information was there, but I could not see it because the viewing window in remarkably small for so much information in raw text...
web logs are actually written to only two files in /var/log/apache2 (error.log and access.log)
I openned two bash windows and run tail -f on error.log in one and tail -f access.log in the other.
When I started the web service, apache threw a warning stating from mod_ssl saying that the certificate did not match the serve name...I the certificate was what I expected, I checked http_server_app.conf and found the ServerName directive that was not changed when I renamed my server...
Easily fixed when its found, but it can take a while to find.
BTW, I was using A DNS records for and it works, but I find your method of using CNAME records documents the administrator's intent better than with A records; I started to do the same. (A records a useful though, they can run a domain across multiple machines)
Cheers mate!

File and Directory Maintenance on OSX Server

Are there any special considerations for using file and directory maintenance utilities such as Disk Warrior or TechTool, etc. when dealing with OSX Server, or can it be handled just like any other volume.
We have all of our data and our user home directories on the server and I would like to run some miantenance on them.
Thanks.

I am no expert on disk utilities.
Personally, I just have a separate 5G partition with a minimal OSX which I boot from once a month (or before a server update) and run Disk Repair & Repair Permissions from.
As far as I know, there is nothing going on on the server that is not going on on a 'normal' OSX machine (at file level mode). The OSX unix offering is miles from the previous OS9 model where the likes of Norton was almost mandatory. The built-in 'periodic' scripts and disk utility 'repair' (see "man fsck" in Terminal) all run at unix level, and have done for years, even before Apple II days!
Although I have both Disk Warrior & TechTool, I don't use them except in an 'emergency' (otherwise called: "try anything").
I would be interested in any other comments though.
-david

OSX Server 10.3.4 updating?

Similar Messages

Maybe you are looking for