Hi Simo, Thanks for the help. I am just going to back up to an old RedHat 9 and Apache 1.whatever. I have wasted far too much time fooling around with Debian and Apache 2, it's a matter of how much lost time is really costing me. I just do not have the luxury to do it. I have rebuilt Debian 3.1 4 times now and each time I try to make any changes what so ever to Apache2 it just breaks the whole damn OS. Perhaps at my age and road mileage I am just unable to "get it". So, thanks again. I really did follow your last email to the letter, I printed it out and typed out each step. This last time I tried it with Manhattan VC being the only site served by the Server and still nothing. Once you remove the 000_default out of Apache2 it seems nothing will work right after that. So, I am at a total loss as to what the deal is. I actually had it working 2 nights ago, but when I logged out from one of the classrooms I created in the Administration tutorial as a teacher, I was not redirected back to the teacher login screen. I checked into this and I was told the ServerName directive was either wrong or not set. Well I never found a ServerName directive in any file dealing with Apache 2. It seems odd though, for the administrator of the ManhattanVC the redirect back worked fine, Thanks,
Cary Pembleton IT Consultant PC Tech Help, LLC 32 Cove Lane Campbellsville, KY 42718 (270) 789-0187 Office http://www.pctechhelp.net -----Original Message----- From: Cary Pembleton [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 5:17 PM To: 'Simo Kauppi' Cc: debian-user@lists.debian.org Subject: FW: Apache2 Manhattan Virtual Classroom Simo, I have finally discovered the problem when I restarted Apache2 service and received this message. (98)Address all ready in use :make_sock could not bind to address 69.40.134.205:80 No listening sockets available, shutting down Unable to open logs Closer investigation finds a version 1.3 of Apache running! What's the deal here? Why install 2 versions of Apache , "Debian"? I guess I should have used the "manually install packages" option during installation to avoid this. So, now I either have to figure a way to kill off the old version of Apache or just keep it from running. I would prefer to be rid of it and only have Apache 2. Thanks, Cary Pembleton IT Consultant PC Tech Help, LLC 32 Cove Lane Campbellsville, KY 42718 (270) 789-0187 Office http://www.pctechhelp.net -----Original Message----- From: Cary Pembleton [mailto:[EMAIL PROTECTED] Sent: Sunday, August 06, 2006 11:08 PM To: 'Simo Kauppi' Cc: debian-user@lists.debian.org Subject: RE: Apache2 Manhattan Virtual Classroom Simo, Ok I have the default site working for Apache2, I have completed all the installation instructions for the MVC, I followed every step you gave me and I receive this error when I try to restart the Apache2; Apache2: Could not open document config file /etc/apache2/sites-enabled/000_mydefault Also my Apache2 default site does not display, but this was expected since we removed it. So how will I be able to "test" if Apache is running or working? I have to admit this is becoming a real pain in my ass! I certainly think I could have gotten this working with Apache 1.3.33 a long time ago, but there must be a reason you recommended against using this. If only I could get Webmin to see Apache 2 instead of Apache 1.3.33 I could configure all of this quite easily and quickly. Somehow I suspect your going to give some sort of Linux Purist response to nice cushy web interfaces, yeah yeah, I have been doing Microsoft stuff too long I guess and forgot how to work and think at the command line. But hey, I have a family of 5, a wife with Muscular Dystrophy, 2 special needs children ages 4 and 5 and a teen age son. I do not have the luxury of time like a lot of people, so who could blame me for wanting, quick , neat and sweet. :o) So, my good and patient friend, what do I do now? I really want to be able to host a couple of web sites off this box. But for now I would be happy to just have one site which gives a brief explanation of the virtual classroom, the courses available and the costs, Then a nice link to send the paying customers on their way to the MVC. Is this too much to ask? I am beginning to think so on Apache 2. Respectfully, Cary Pembleton IT Consultant PC Tech Help, LLC 32 Cove Lane Campbellsville, KY 42718 (270) 789-0187 Office http://www.pctechhelp.net -----Original Message----- From: Simo Kauppi [mailto:[EMAIL PROTECTED] Sent: Thursday, August 03, 2006 1:07 PM To: Cary Pembleton Subject: Re: Apache2 Manhattan Virtual Classroom On Thu, Aug 03, 2006 at 11:48:13AM -0400, Cary Pembleton wrote: > Simo, > It "More" than helps! You should consider "teaching" as a secondary > career for Linux Debian and hosting your own web server. You have a > "gift" for explanation and clarity. This is quite unusual, trust me, I > get customers all the time which have been thoroughly confused by > other technicians , engineers or service centers. It has taken me > slightly over 20 years to develop these kind of skills. I am going to > do an OS rebuild. I am considering, not installing Apace2, but rather > waiting and installing Apache 1.3, the reason is simple. I believe the > Manhattan VC was designed with the older version in mind. It may > simplify things quite a bit. I had this working on a RedHat 7 box a > few years back and had little or no difficulty with it. I even had > FrontPage extensions working so building a front end web site for it > was a snap. What are your thoughts on this approach? I think Debian > will be a far better OS choice than some of the other Linux > distributions, based on my research it has a better record for stability. > As always, you da man! Thanks! > Cary Hi Cary, Thanks for your kind words :) I actually do technical writing as a part of my job. I try to convert the engineers' jargon into a human understandable form. I just tested my own instructions with a fresh install of Apache2 in a Debian box and it works like a charm :) A couple of minor details I noticed: The fresh install of apache2 already has 'Listen 80' in the /etc/apache2/ports.conf, so either let it be or change it to 'xx.yy.zz.ww:80', it cannot have both. Also, you can do without the DocumentRoot -directive in the file /etc/apache2/sites-available/manhat (it doesn't hurt either). Also, the link in the /etc/apache2/sites-enabled is called 000-default, so to remove it: rm /etc/apache2/sites-enabled/000-default Also, you probably noticed that you need to change the HTTPD_GROUP to "www-data" both in custom.h and Makefile before compiling the MVC. You can do the installation without using the virtualhost, if this is going to be the only site in your server. Just don't link the default file into the /etc/apache2/sites-enabled/ directory and remove the <VirtualHost> and </VirtualHost> tags from the file manhat. I.e. the file manhat is the only file in the /etc/apache2/sites-enabled/ -directory. I would not go to the version 1.3 without a very good reason. I've learnt to like the way things are arranged in the Debian version of Apache2. Also if you want to start using SSL-access to the site, Apache2 has the mod_ssl included. Also I am a big fan of Debian GNU / Linux and I wouldn't switch to another distribution :) With kind regards Simo So here are the revised instructions: After installing apache2, check that user manhat belongs to the group www-data. Log in as manhat and give the command 'groups'. If the group www-data is not there, add it: adduser manhat www-data Change the Listen directive in the /etc/apache2/ports.conf to: Listen xx.yy.zz.ww:80 Create a file /etc/apache2/sites-available/manhat and put this into it: -------------8<-cut here---------------------------------- # Remove the tag below, if this is your only site <VirtualHost xx.yy.zz.ww:80> # This should be a working email address ServerAdmin [EMAIL PROTECTED] # Make sure that you put your real servername here ServerName www.manhat.yourdomain.com # You might want to make a simple index.html into /home/manhat # e.g just a link to the manhat-bin/doorstep # Otherwise you can change this to # DocumentRoot /var/www # DocumentRoot /home/manhat ScriptAlias /manhat-bin/ /home/manhat/manhat-3.1.0/bin/ <Directory "/home/manhat/manhat-3.1.0/bin/"> AllowOverride None Options +ExecCGI -Includes Order allow,deny Allow from all </Directory> ScriptAlias /manhat-sbin/ /home/manhat/manhat-3.1.0/sbin/ <Directory "/home/manhat/manhat-3.1.0/sbin/"> AllowOverride None Options +ExecCGI -Includes Order allow,deny Allow from all </Directory> Alias /manhat-images/ /home/manhat/manhat-3.1.0/images/ <Directory /home/manhat/manhat-3.1.0/images> Options FollowSymLinks AllowOverride None Allow from all </Directory> CustomLog /var/log/apache2/manhat-access.log combined ErrorLog /var/log/apache2/manhat-error.log # LogLevel can be: debug, info, notice, warn, error, crit, alert or emerg LogLevel warn # Remove the tag below, if this is your only site </VirtualHost> -------------------8<-cut here----------------------------- Remove the default link from the /etc/apache2/sites-enabled: rm /etc/apache2/sites-enabled/000-default Copy /etc/apache2/sites-available/default to /etc/apache2/sites-available/mydefault Note! Not needed, if this is your only site Edit the file /etc/apache2/sites-available/mydefault and change the first two lines to: NameVirtualHost xx.yy.zz.ww:80 <VirtualHost xx.yy.zz.ww:80> Note! Link only the file manhat, if this is your only site Link the files to the /etc/apache2/sites-enabled/: ln -s /etc/apache2/sites-available/mydefault /etc/apache2/sites-enabled/000_mydefault ln -s /etc/apache2/sites-available/manhat /etc/apache2/sites-enabled/010_manhat The prefix numbers are there to make sure that the files are read in the correct order :) Restart your www-server. Make sure that you have your ip-address defined in the /etc/hosts. Note, if you want people to access the site, you need to have your ip-address defined in a DNS-server which is visible to other machines. The other machines cannot see your /etc/hosts. If you don't have a DNS-server, you can define the ip-address in each machine's /etc/hosts file (or \windows\system32\drivers\etc\hosts in case of windows-clients). If you have a firewall, make sure that it lets incoming connections to the port 80. Point your browser to http://www.manhat.yourdomain.com/manhat-bin/doorstep You can check the log file /var/log/apache2/manhat-error.log for any problems. You can increase the loglevel to debug to see more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
