Services are being restored slowly. Unfortunately, the move was delayed somewhat due to a flub-up with our IP provider, a .forwarded user’s e-mail, and AOL being a little careless in examining said user’s e-mail.
With luck everything will be fully back to normal later today.
Moving machines can be something of a nightmare (for example: you basically lose ALL your user account passwords). Once the restoration is complete, look for an article from David on his experiences.
[quote:5a27a392fa=”Timbits”]Well i already reinstalled(i’ve got this down to an art.) and i’m thinking that i should from now on try to firugre out whats wrong and how to fix it. instead of just reinstalling.[/quote:5a27a392fa]
Probably a good idea 🙂 Should it happen again, take a look a the logs and apachectl output first. Chances are that will give you enough information to determine where the problem is occurring and what needs to get fixed.
In addition to Postfix and Exim (covered on the main site), QMail has been ported to Mac OS X. If you want to shell out tons of cash, you can also run Communigate Pro or Post.Office.
IMO, Postfix or Exim are the way to go. I know Postfix is dead simple to set up, and Joel’s even put together an Installer for Exim.
The first place to turn in situations like this is your system logs: /var/log/system.log and /var/log/httpd/ (in the latter, check for error_logs) Between them, you may get some idea as to why Apache isn’t starting for you.
When you moved the logs, did you use Server Settings to do it, or the command line? If the latter, did you update the requisite entries in /etc/httpd/httpd_macosxserver.conf?
What happens when you run sudo apachectl configtest?
Apple’s implementation is minimal-to-missing. I did a little digging around on this a while ago, and never successfully found an answer. I [i:e7c086c416]think[/i:e7c086c416] there are multiple versions of db support available (not just Berkeley DB 3 and 4), and that the db that Apple has is [i:e7c086c416]really[/i:e7c086c416] old.
If you take a look in /usr/include/db.h, for example, you’ll see that the code dates from early 1994. I can’t tell from the code there which version—or implementation—of db/Berkeley DB it is, but I’m willing to bet it’s not v3 (and am pretty certain it isn’t v4!)
Regardless, all we seem to have is the db.h header file, not the rest of the library.
Be forewarned: if you install a Berkeley DB, you may lose functionality in other applications that have built, e.g., hash-table databases. This will be especially important if you use Postfix. I’m not saying it can’t be done, only that the last time I tried (admittedly, under Server 10.1.x) things got bollixed up.
I haven’t tried it, but I wouldn’t be surprised given that XP caused SMB problems (which Apple fixed in 10.2.x). Can you try setting up WebDAV on, e.g., a Linux machine and see if there are similar problems?
You can do this! You’ll need to write a shell script to handle the rename/move bit, though. I recommend picking up a copy of [i:5306a32a42]Using csh & tcsh[/i:5306a32a42] (O’Reilly) if you aren’t familiar with the shell. Or, you could write the script in Perl or Python, too. Heck, you could probably write a compiled AppleScript to do it, too.
Regardless, you’ll want the script to build a string with the current date?this will probably be easier to do in Perl or Python?and append it to a string representing the file name.
Execute the mv shell command, giving it the old and new file names. That will move the file from the old to the new name. You may need to ‘touch’ the plain file so that the log daemon will pick up the name change, or send SIGHUP to the daemon process.
Once you have the script created and working, you can add it to a cron job under your account. If you don’t already have a crontab, then create a file called “mycron.in” containing:[code:1:5306a32a42]#
Are you on a dynamic IP, or fixed? Are you using Apple Mail Service, or a different MTA? We have WebMail configured here and it works flawlessly, but we’re on a fixed IP using Postfix as the MTA.
Apple doesn’t seem to supply any ready-made tools to accomplish this. However, you should be able to create a RAM disk using the command line. I would start out by reading the man pages on fstab, mount, and newfs.
[quote:9e6327d4a8=”RobotDeathSquad”]Is there any way to set the DNS settings from the terminal? I don’t have physical access to the machine. Only SSH.[/quote:9e6327d4a8]
[code:1:9e6327d4a8]
sudo emacs /etc/resolv.conf
SystemStarter restart Network
[/code:1:9e6327d4a8]
Should do the trick. Feel free to substitute your preferred command line editor for ’emacs,’ if you’re not one of the enlightened :).
[quote:c3340c6aea=”RobotDeathSquad”]Well, I’m trying to get my NS working correctly. The incoming works, but now outgoing. Is it possible to use your own nameserver for outgoing requests, and not use your ISPs? If so, how would I do that?[/quote:c3340c6aea]
You’d need to set yourself up to receive zone updates from another DNS out there, which takes a fair amount of space as well as time. Unless there is a [b:c3340c6aea]compelling[/b:c3340c6aea] reason to do this, I wouldn’t.
[quote:3b414a35e2=”legwind”]Anyone have any ideas on how I can make OS X 10.2.3 Server keep my DSL connection alive?
I have the DSL modem connected to my built-in ethernet card, and under System Preferences->Network, I am using PPPoE, with the appropriate details entered.
Under PPPoE options, I have ticked the box which says ‘Connect automatically when needed’, but it doesn’t seem to do what I want. I need to have the server keep the connection alive, even when the server isn’t logged on.[/quote:3b414a35e2]
I’d recommend switching to always-on DSL first. It’s less hassle. Failing that, make sure you don’t have any timeouts set in your Network Preference and in Internet Connect. Also, you could set up a cron job to ping some known good server every few minutes, though that’s really a poor use of network resources.
[quote:ce7265e6db=”afriis”]I have over 20 (and counting) domains running on our webserver (Server 10.1). I would like to be able to use wildcards in the domain names to allow both “domainname.com” and “www.domainname.com” without resorting to adding two posts to the sites list in the Server admin for each domain. I tested this out using both blanks and “*” without sucess. Any tips?[/quote:ce7265e6db]
The simplest way to do this is to specify one name in Server Admin, and then edit [b:ce7265e6db]httpd_macosxserver.conf[/b:ce7265e6db] to add the other name as a [b:ce7265e6db]ServerAlias[/b:ce7265e6db].
For example, create the entry in Server Admin for “www.foobar.com” and then add[code:1:ce7265e6db]ServerAlias foobar.com[/code:1:ce7265e6db]right after the [b:ce7265e6db]ServerName[/b:ce7265e6db] line. Apple tried to discourage people from editing Apache configuration files in Server 10.1, but this small change won’t hurt Apache and will simplify your sites list in Server Admin.
I [i:ce7265e6db]think[/i:ce7265e6db] you might be able to achieve a similar effect by using wildcard DNS records, but am not certain. I know the directions above work, as I used them myself.
Recent Comments