This is a discussion on Migration issues within the Apache Web Server forums, part of the Web Server and Related Forums category; I just bought a new Mac and migrated all my files to it. Since my Mac is an Intel box, ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I just bought a new Mac and migrated all my files to it. Since my Mac
is an Intel box, my former Server Logistics Complete Apache2 binary no longer works. I've successfully installed Apache2.2.4 and have moved all my htdocs and config files over to the new build. Of course, this is where errors started. After having module issues and ultimately disabling all the modules, I seemed to successfully get Apache to start, but when I try to access my site, I consistently get an error stating I don't have permission to access to (/) (I assume this means root). Have I disabled some essential module or is there something else in the httpd.conf file that needs to be enabled or disable. Or does this problem lie elsewhere? Oh, and the configtest comes up clean. My Apache build is in a new location. Formerly it was in /Library/ Apache2. Now it is in /apache2. I'd appreciate any thoughts. Jim |
|
|||
|
On Apr 21, 2:01 am, Davide Bianchi <davideyeahs...@onlyforfun.net>
wrote: > On 2007-04-21, jimcoyle1 <jamescoy...@mac.com> wrote: > > > my site, I consistently get an error stating I don't have permission > > to access to (/) (I assume this means root). > > The DocumentRoot I suppose. > > > essential module or is there something else in the httpd.conf file > > Check the permissions on the directories/files you are trying to > access, apache (or the user that it runs as) need read permissions > on the files and read/execute permissions on the directories. > > Davide > > -- > "Did you know God had a plan for you?" > "Does it involve a high-powered rifle and a belltower?" Thanks for your suggestions. After making some adjustments, I at least got the Apache page (surprised to see this page), so I knew something was working. Now things weirder. I discovered that I had a startup item in the Library for the binary version of Apache2 which I had had. I've deleted that and now Apache starts up okay, but my web page doesn't come up. According to the activity log in Safari, here's the problem: http://www2.heartfullofdirt.com:8111/ -= can't connect to host http://www.heartfullofdirt.com/ 0.5kb Because of firewall issues, in the past I've had to do redirects to the www2 URL using port 8111. My DNS update software is working fine, but for some reason, the redirect is not working. I checked my old httpd.conf file to see if there was something I've forgotten, but it doesn't appear that I have. Also, when I start up apache via sudo apachectl -k start, this is what the terminal says: James-Coyles-iMac:/apache2/bin jamescoy$ sudo apachectl -k start Password: usage: /usr/sbin/apachectl (start|stop|restart|fullstatus|status| graceful|configtest|help) start - start httpd stop - stop httpd restart - restart httpd if running by sending a SIGHUP or start if not running fullstatus - dump a full status screen; requires lynx and mod_status enabled status - dump a short status screen; requires lynx and mod_status enabled graceful - do a graceful restart by sending a SIGUSR1 or start if not running configtest - do a configuration syntax test help - this screen Processing config directory: /private/etc/httpd/users/*.conf /usr/sbin/apachectl start: httpd started Is Apache starting from this config in /private rather than using the one in apache2/conf? I'm wondering if remnants of my old binary installation are causing the problems here. Thanks again for any suggestions. Jim |
|
|||
|
On Apr 21, 2:01 am, Davide Bianchi <davideyeahs...@onlyforfun.net>
wrote: > On 2007-04-21, jimcoyle1 <jamescoy...@mac.com> wrote: > > > my site, I consistently get an error stating I don't have permission > > to access to (/) (I assume this means root). > > The DocumentRoot I suppose. > > > essential module or is there something else in the httpd.conf file > > Check the permissions on the directories/files you are trying to > access, apache (or the user that it runs as) need read permissions > on the files and read/execute permissions on the directories. > > Davide > > -- > "Did you know God had a plan for you?" > "Does it involve a high-powered rifle and a belltower?" Thanks for your suggestions. After making some adjustments, I at least got the Apache page (surprised to see this page), so I knew something was working. Now things weirder. I discovered that I had a startup item in the Library for the binary version of Apache2 which I had had. I've deleted that and now Apache starts up okay, but my web page doesn't come up. According to the activity log in Safari, here's the problem: http://www2.heartfullofdirt.com:8111/ -= can't connect to host http://www.heartfullofdirt.com/ 0.5kb Because of firewall issues, in the past I've had to do redirects to the www2 URL using port 8111. My DNS update software is working fine, but for some reason, the redirect is not working. I checked my old httpd.conf file to see if there was something I've forgotten, but it doesn't appear that I have. Also, when I start up apache via sudo apachectl -k start, this is what the terminal says: James-Coyles-iMac:/apache2/bin jamescoy$ sudo apachectl -k start Password: usage: /usr/sbin/apachectl (start|stop|restart|fullstatus|status| graceful|configtest|help) start - start httpd stop - stop httpd restart - restart httpd if running by sending a SIGHUP or start if not running fullstatus - dump a full status screen; requires lynx and mod_status enabled status - dump a short status screen; requires lynx and mod_status enabled graceful - do a graceful restart by sending a SIGUSR1 or start if not running configtest - do a configuration syntax test help - this screen Processing config directory: /private/etc/httpd/users/*.conf /usr/sbin/apachectl start: httpd started Is Apache starting from this config in /private rather than using the one in apache2/conf? I'm wondering if remnants of my old binary installation are causing the problems here. Thanks again for any suggestions. Jim |