SOLVED - Apache upgrade from 2.0 to 2.2

[spottraining]

How difficult is to upgrade from 2.0.59-r5 to new Apache 2.2 series?
I found this http://www.gentoo.org/doc/en/apache-upgrading.xml guide, and now I dont understand. Need I fallow Upgrading from <2.2.6-r4 guide or Upgrading from <2.0.52-r3 guide?

At my apache right now I have all modules modules.d directory and I have all ready httpd.conf file.

Can someone tell, how hard it was to upgrade in working server to new 2.2?

[cjubon]

Need I fallow Upgrading from <2.2.6-r4 guide or Upgrading from <2.0.52-r3 guide?

Well, you want to upgrade from 2.0.59-r5. Is this lower than 2.0.52-r3 . I guess the answer is "No". So, follow the "Upgrading from <2.2.6-r4" chapter in the guide.

It's not that difficult (at least it was not for me). Just be sure that your /etc/make.conf is prepared accordingly (as explained in the upgrade guide). If your /etc/apache2/httpd.conf is still old style (i.e., including listen and config directives for the content root directory), it's good to know that most of those directives are now in /etc/apache2/vhosts.d/00_default_vhost.conf and /etc/apache2/vhosts.d/default_vhost.include. Many people get "Socket already in use" errors because they have the same listen directives both in /etc/apache2/httpd.conf and /etc/apache2/vhosts.d/00_default_vhost.conf.

If you're not sure and your server actually serves webcontent, you can always run

Code: Select all

quickpkg --include-config=y --include-unmodified-config=y =apache-2.0.59-r5

before changing anything. If something goes wrong, you can then easily revert to the older version. quickpkg is part of app-portage/gentoolkit.

Hope this helps.

[dalu]

Err excuse me, but what is happening here?

Apache 2.0.x has been completely removed from portage
why?
I just went over to httpd.apache.org and there is 2.0.63 out
On my system 2.0.61 is installed and i wanted to upgrade to 2.0.63.
But lo and behold the STABLE 2.0 branch isn't available at all anymore.
What is this nonsense?

I'm depending on the 2.0 branch and i'm sure that i'm not the only one

I wanted to move the contents of the older and slower server to a faster one because of capacity issues, but guess what apache2.0.x isn't available
and 2.2.x isn't suited (tested and failed) for the task.
WTF were you thinking?

sigh ok i calmed down, now what?
switch to a different distro or is there any way to solve this mess?

[spottraining]

Code: Select all

quickpkg --include-config=y --include-unmodified-config=y =apache-2.0.59-r5

before changing anything. If something goes wrong, you can then easily revert to the older version. quickpkg is part of app-portage/gentoolkit.

Hope this helps.

How to get it back?????

I have right now lot of problems with apache2.2 upgrade
Modules are added to make.conf file as APACHE2_MODULES, but when I emerge - then most of modules are out. Like -vhost-alias etc.

[spottraining]

After three hours I have now at Apache 2.2.8.

Problem was easy - when I run
echo APACHE2_MODULES=\"$(sed '/^mod_/s/mod_\(.*\)\s\+\(shared\|static\)/\1/;t n;d;:n' /etc/apache2/apache2-builtin-mods)\" >> /etc/make.conf
after that I add some modules with nano.

And now - I understand, that nano don't likes wery long lines. Its cut lot of modules off and so I was unable to start server.

I commented out first added modules and then I paste to the nano new modules, what I found from forum (then nano shows me also three lines of modules, not like before - only one long line) and after that I emerged apache again. I changed the httpd.conf file, added there my custom Includes and aliases (I am using VHCS control panel) and I get it work.

[caspar]

And now - I understand, that nano don't likes wery long lines. Its cut lot of modules off and so I was unable to start server.

Use

Code: Select all

nano -w

then, or even better vim . I also came from nano to win. It is a bit difficult for starters but after that phase you will be more productive.

[spottraining]

Thanks for tip