Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgraded RH 7.1 to 8.0 have problems with Apache and Samba 1

Status
Not open for further replies.

2bmobile

IS-IT--Management
Nov 24, 2002
6
US
Hi,

I just used the upgrade option on a working Red Hat 7.1 system that was running Apache 1.37 and Samba 2.0.1 find.

Since I installed I can not get Apache to run. I have used the Apache 2.0 http.conf file instead of the old Apache 1.3. I read the RH doc about Migrating Apache config files but do not know what I am missing.

Also my current user's password for Samaba seems not to be working. I created a new user and it works with Samba.

Any thoughts?
 
What error message do you get when you try to (re)start apache? If it complains about mixing regular vhosts with ssl then you just need to delete the ssl.conf file. Check your mail server too while you're at it. Sendmail uses a different sentup and has moved some files during the upgrade. This may have been what happened to samba's passwords
 
Thnaks for the insight. I got Samaba's password issue fixed. The group level p[assword was set on instead of no password ( I use the User level for security). I am still having problems with HTTP 2.0 running. I started with Webmin remotely and it puts the system into a infinite loop causing me to reboot. I have stopped using Webmin and now working at the consuel.
 
Don't rag on webmin, I kinda like it myself. :) When you look at the apache setup from webmin, does it show some vhosts that you don't want? If so, get rid of those bad boys. On mine it showed _Default_:80 and and something for SSL. I 86ed both of those and had no problems since. What version of webmin are you using? I have 1.050. It seems to work better with RH 8.0. If that doesn't work, Try to use a fresh httpd.conf and see if it will let apache start. If it does, then you can add your vhost stuff to the bottom of it. It's not a bad idea to make a backup of your config files BEFORE you edit them just incase of times like these. For example, I bade a back up of httpd.conf and called it httpd.conf.orig so I would not that was the original config file. It's also not a bad idea to make a backup of the latest one that works. :) If you don't have one I can post one here or e-mail you a brand new fresh one.
 

The ssl.conf disabled and 86ing the vhosts. I got the http up and running. I am checking to see if all the features work on my site (like PHP, CGI and so).
Thanks for the help!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top