OSX April Update - webserver, ftp now broken

J

jasonbarak

Registered
I've been hosting a web site and accessing my computer via ftp for several months now - OSX is fantastic. I use dnydns.com to manage my dynamic ip.

The only changes I've made to the default setup have been to the httpd.conf file to allow for name-based virtual hosting.

After applying Mac OSX April 2002 Update, my webhosting and ftp no longer work. I can ping my ip address and my dnydns listing and I receive packets - all ok there.

I checked my, /var/log/httpd/error_log, and the last entry is (i replaced my actual userame with [myusername] below):

[Sun Apr 7 10:24:40 2002] [notice] caught SIGTERM, shutting down
Processing config directory: /private/etc/httpd/users
Processing config file: /private/etc/httpd/users/myusername.conf
[Sun Apr 7 10:24:43 2002] [notice] Apache/1.3.23 (Darwin) configured -- resuming normal operations
[Sun Apr 7 10:24:43 2002] [notice] Accept mutex: flock (Default: flock)

Does anyone have a clue as to the issues here? Any advice.
 
This might be the dumbest suggestion ever, but have you checked the Sharing pane in System Preferences? It's possible that the security update might have turned off external services like http and ftp.
 
By "no longer work," what exactly do you mean? When you ftp mymachine what kind of error message do you get back, or does it just sit until it times out?
 
BLB...

The connection is never made so there is a timeout. This happens for both the web access and ftp access.

It seems that my computer is not responding to any requests.
 
That's definitely strange; if a service happened to turn off, you should receive an error in the form of connection refused instead of nothing at all.
This update modified Apache (and other items) and restarts it, but didn't touch ftp at all. You're absolutely sure the dyndns stuff is still updating correctly? Also, you haven't started testing out the firewall in the OS, have you?
 
I double checked all settings and then as a last resort, I rebooted my Mac again (I rebooted several times during my testing). Now, all is working again. I didn't change anything, so I'm at a loss for the sudden "fix".

I'll chalk this up to a glitch and hope that it holds.

Thanks for all the suggestions.
 
You must log in or register to reply here.
Back
Top