V5 upgrade problems - centos 6

[minijay]

Hi All

we run the update this morning to move up to v5.02 which surprisingly went really well.. we had to install a dependency to install version 5 but the rest of the install went well.. i tool the liberty of installing the crypt module for password encryption as we havnt used that before but i dont think that has caused the problem

once the install was complete without errors i navigated to our web page and was greeted with


Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.


i did notice that when restarting the httpd service that we got the following errors..


Starting httpd: [Thu Nov 05 08:45:57 2015] [warn] The Alias directive in /etc/httpd/conf/httpd.conf at line 551 will probably never match because it overlaps an earlier Alias.
[Thu Nov 05 08:45:57 2015] [warn] The ScriptAlias directive in /etc/httpd/conf/httpd.conf at line 576 will probably never match because it overlaps an earlier Alias.
[Thu Nov 05 08:45:57 2015] [warn] The Alias directive in /etc/httpd/conf/httpd.conf at line 855 will probably never match because it overlaps an earlier Alias.

we normally get two lines but now we get a third. ive attached our httpd.conf file so you can take a look but to be honest im not sure where to start so im really looking for some advise. we did change our code so that we lose the otrs/index.pl so its just index.pl so im not sure if this is part of the problem but has been working up till now.

im thinking it may be worth building a new server with v5 on it and going from there, do you think that would be advisable.. obviously i would need to upgrade the DB on the old server before copying it over to the new server.

can anyone advise what may have gone wrong as to why i cant get the login page on v5 anymore.

if i did decide to do a new install would you recommend centos 7 or is 6 still better for otrs.

thanks for your help in advance. ive rolled back to v4 (snapshot) so i can still use the system in the meantime

Jay

[xhoy]

Most of the time these error are because you did not restart your apache server. Since you tried that it should be something else.

• * have you included the new apache2-httpd.include.conf in your httpd?
  * have you followed every step of the upgrade process
  ** clear cache
  ** backuping var/ but not putting it back to the orignal place (then stuff breaks)
  ** run bin/otrs.CheckModules.pl
  * have you looked at your apache logs? Most of the time they have good clues :>

[minijay]

hi xhoy

i did follow the guide exactly and we used the rpm which is "supposed" to restore the files as part of the install but i have seen in the past this not doing as it should so ill have another go and copy the files back and see what happens

the apache2-httpd.include file ? never heard of this or seen it referenced in the guide.. could you tell me a little more about it and what i should do with it

ill give the upgrade another go. we had a similar issue nearly a year ago which i have found the posts for so ill reference those as well just in case that helps fix the problem

i think ultimatly it may be better for me to setup a brand new fresh server and copy the database over this way i should get any gremlins out of the current setup (hopefully) it would be nice to start from scratch but i have to many current tickets that i would need to get closed before i could fully change

thanks for your help ill see if i can dig up more info

jay

[crythias]

Step 6 in installation, but understood about Upgrading.

[minijay]

Hi crythias

I was following the upgrade from 4 to 5 step 6 is the db upgrade

So in this case I should follow step 6 from the install guide is this correct ? Then go back to see if I can login

I'm going to copy the vm to another machine and try from there to save disturbing the production server once it's working repeat the steps again.

Thanks for all your help

Jay

[minijay]

hi all

i managed to get this working afterall..

i had to remove all the packages before the upgrade would work, not sure what the problem was but it seems to be working fine now.

we were using the FAQ module but luckily only had a few cases so it was easy to copy and set back up again afterwards

thanks

justin