Did you follow the procedure provided in the UPGRADING document found in the otrs directory, when you initially upgraded from 1.2 to 1.3?
On Fri, 2005-06-17 at 01:33 +0100, Des Quinn wrote: > Well I have made some progress albeit is a parralell direction :) I have > installed the windows version of otrs installer onto a vmware XP session. I > have then pointed this at the OTRS database on the linux machine. And it > works with me being able to view all the tickets. > > Now I have not done too much testing yet but I am wondering if a otrs 1.24 > install pointing at a otrs 1.31 database is going to end in some trouble. > However thats not a major issue as I will be using this as a read only > system to look at past info until I get it working properley on the Linux > box > > so does this give any more clues into my problem .....? > > > "Des Quinn" <> wrote in message news:[EMAIL PROTECTED] > > Hi, > > > > I was using a RH9 based distribution with Apache 2 (httpd-2.0.40-24) and > > mysql 3 (mysql-3.23.58-1.9) but decided to upgrade to the latest version > > of the distribution which is based on Fedora Core 2 (kernel 2.6.9.10). > > This uses apache 2 (httpd-2.0.51-3.0.cc) and mysql 4 > > (mysql-server-4.1.8-1.cc). Old perl version was 5.8 and new perl version > > is 5.8.3 and is located in /usr/bin/perl. Otrs version is 1.31 at the > > moment but I do not want to upgrade to 1.32 unless that is going to make > > sense in my current situation. > > > > This is th eonly web based application on the box that has failed to work > > after the upgrade. I have other php based web applications that can access > > the database without issue, and the websites located on the box are not > > showing any issues. It is only OTRS that seems to have an issue that > > results in an apache child process seg faulting. > > > > This occurs when I try to access the logon page, either customer or agent > > and sometimes I dont even get the logon page displaying. When I start the > > otrs service its checks complete ok although I did have to set > > OTRS_DB_RUNNING=0 in /etc/sysconfig/otrs. The log shows the connection > > being authorised when I enter my details into the logon fields but then it > > just goes to a 404 page. Setting apaches log level to debug does not seem > > to produce any more information. > > > > Having looked through this thread "Segmentation fault (Apache 1.3 & 2) > > when trying to login to OTRS" on the mailing list which appears to be very > > similar, but I dont get any further by following its suggestions. I do not > > get any error message when starting via apachectl. Perl:DBI is > > perl-DBI-1.40-4. > > > > Can anyone give me a direction to follow as I am at a loss. > > > > regards > > > > Des Quinn > > > > > > > > > > > > _______________________________________________ > > OTRS mailing list: otrs - Webpage: http://otrs.org/ > > Archive: http://lists.otrs.org/pipermail/otrs > > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs > > Support oder Consulting fr Ihr OTRS System? > > => http://www.otrs.de/ > > > > > > _______________________________________________ > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs > Support oder Consulting fr Ihr OTRS System? > => http://www.otrs.de/ > _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
