Upgraded system and now OTRS causes a segfault in apache

newer
Filemanager for OTRS 2.0.0 beta2...

Des Quinn

15 Jun 2005 15 Jun '05

9:58 a.m.

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

Show replies by date

Des Quinn

16 Jun 16 Jun

11:36 p.m.

Hi, I was wondering if anyone had any ideas on this or is there any more information that I can provide that might help? regards "Des Quinn" wrote in message news:d8ots7$715$1@sea.gmane.org...

...

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 für Ihr OTRS System? => http://www.otrs.de/

Des Quinn

17 Jun 17 Jun

12:33 a.m.

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:d8ots7$715$1@sea.gmane.org...

...

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 für Ihr OTRS System? => http://www.otrs.de/

Graham T. Smith

7:35 a.m.

New subject: Upgraded system and now OTRS causes a segfault in apache

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:d8ots7$715$1@sea.gmane.org...

...
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/

Des Quinn

9:09 a.m.

New subject: Upgraded system and now OTRS causes a segfault inapache

Hi and thanks for the reply. I did not upgrade from 1.2 to 1.3.1, as the upgrade I performed was on the linux box. The otrs version stayed at 1.3.1 while apache, perl, and mysqls version changed. The current windows vmware session has otrs 1.2.4 on it at present but is pointing at a 1.3.1 database on the "broken" linux machine. regards "Graham T. Smith" wrote in message news:1118993716.7817.3.camel@GTSSony.gtshome...

...

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:d8ots7$715$1@sea.gmane.org...

...
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/

Christian Schoepplein

10:30 a.m.

New subject: Upgraded system and now OTRS causes a segfault inapache

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Des, maybe there is a problem with mod_perl after the upgrade. Would you try OTRS without mod_perl please? Best regards, Christian On Fri, Jun 17, 2005 at 10:09:47AM +0100, Des Quinn wrote:

...

Hi and thanks for the reply.

I did not upgrade from 1.2 to 1.3.1, as the upgrade I performed was on the linux box. The otrs version stayed at 1.3.1 while apache, perl, and mysqls version changed. The current windows vmware session has otrs 1.2.4 on it at present but is pointing at a 1.3.1 database on the "broken" linux machine.

regards

"Graham T. Smith" wrote in message news:1118993716.7817.3.camel@GTSSony.gtshome...

...
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:d8ots7$715$1@sea.gmane.org...

...
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/

_______________________________________________ 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/

Des Quinn

7:13 p.m.

New subject: Upgraded system and now OTRS causes a segfaultinapache

Hi Christian, Thanks for helping me out, disabling mod_perl sorted it. The question is what can I do to troubleshoot this further and get mod_perl working again. I have mod_perl-1.99_12-2.1 installed but to be honest I have no idea what to do next. Any pointers to other information sources would be appreceiated regards "Christian Schoepplein" wrote in message news:20050617103038.GC4664@jvc-schoeppi.schoeppi.net... -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Des, maybe there is a problem with mod_perl after the upgrade. Would you try OTRS without mod_perl please? Best regards, Christian On Fri, Jun 17, 2005 at 10:09:47AM +0100, Des Quinn wrote:

...

Hi and thanks for the reply.

I did not upgrade from 1.2 to 1.3.1, as the upgrade I performed was on the linux box. The otrs version stayed at 1.3.1 while apache, perl, and mysqls version changed. The current windows vmware session has otrs 1.2.4 on it at present but is pointing at a 1.3.1 database on the "broken" linux machine.

regards

"Graham T. Smith" wrote in message news:1118993716.7817.3.camel@GTSSony.gtshome...

...
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:d8ots7$715$1@sea.gmane.org...

...
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/

_______________________________________________ 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/

- -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCsqZOTFWOq90iSiERAuQGAKCPzXkfG9QMaD5GMrXdr4fmmV3fngCg1yvL hyfIC9tNFIAd1Q27HOjLLzY= =CvgF -----END PGP SIGNATURE----- _______________________________________________ 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/

Graham T. Smith

11:29 a.m.

New subject: Upgraded system and now OTRS causes a segfault inapache

Some points of clarification. You seem to be suggesting that you have a 1.3.1 otrs database backending for a 1.2.4 otrs system. As the database schema is different between 1.2.x and 1.3.x would suspect that this could cause a few problems. If on the otherhand you have a unupgraded 1.2.x database being accessed by a 1.3.x otrs setup the 1.3.x setup will tend fall apart. Both 1.2.4 and 1.3.1 accessing the same dataset sounds like one of those interesting experiences :-) The problems you are reporting seems to be consistent with a 1.2.x database being used with 1.3.x (at least in my experience), it is possible that the database itself was not upgraded when you upgraded to the new distro if you were originally running 1.2.x. You do not report what version of otrs was installed before you upgraded the distro. On Fri, 2005-06-17 at 10:09 +0100, Des Quinn wrote:

...

Hi and thanks for the reply.

I did not upgrade from 1.2 to 1.3.1, as the upgrade I performed was on the linux box. The otrs version stayed at 1.3.1 while apache, perl, and mysqls version changed. The current windows vmware session has otrs 1.2.4 on it at present but is pointing at a 1.3.1 database on the "broken" linux machine.

regards

"Graham T. Smith" wrote in message news:1118993716.7817.3.camel@GTSSony.gtshome...

...
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:d8ots7$715$1@sea.gmane.org...

...
Hi,

[Stuff deleted]

...
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 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/

Des Quinn

2:57 p.m.

New subject: Upgraded system and now OTRS causes a segfaultinapache

Hi, some points inline "Graham T. Smith" wrote in message news:1119007789.7817.52.camel@GTSSony.gtshome...

...

Some points of clarification.

You seem to be suggesting that you have a 1.3.1 otrs database backending for a 1.2.4 otrs system. As the database schema is different between 1.2.x and 1.3.x would suspect that this could cause a few problems. If on the otherhand you have a unupgraded 1.2.x database being accessed by a 1.3.x otrs setup the 1.3.x setup will tend fall apart. Both 1.2.4 and 1.3.1 accessing the same dataset sounds like one of those interesting experiences :-)

I have 1 Linux server and an XP vmware session. The Linux box has 1.31 (always has) and the XP box has 1.24. In order to get access to the tickets for billing purposes :) and troubleshooting I have pointed the XP install at the Linux database.

...

The problems you are reporting seems to be consistent with a 1.2.x database being used with 1.3.x (at least in my experience), it is possible that the database itself was not upgraded when you upgraded to the new distro if you were originally running 1.2.x. You do not report what version of otrs was installed before you upgraded the distro.

I have no functionality at the moment with otrs running on the linux box but will check the mod_perl suggestion above. OTRS was the same version before the upgrade to the linux box, and otrs has not been upgraded. So there is the possibility of corrupting the database if I work on it thru the XP otrs install but thats not an issue as I dont want to add any info to it at the moment, thanks for the help so far.

...

On Fri, 2005-06-17 at 10:09 +0100, Des Quinn wrote:

...
Hi and thanks for the reply.

I did not upgrade from 1.2 to 1.3.1, as the upgrade I performed was on the linux box. The otrs version stayed at 1.3.1 while apache, perl, and mysqls version changed. The current windows vmware session has otrs 1.2.4 on it at present but is pointing at a 1.3.1 database on the "broken" linux machine.

<snip>

7337

Age (days ago)

7339

Last active (days ago)

List overview

Download

8 comments

3 participants

participants (3)

Christian Schoepplein
Des Quinn
Graham T. Smith