Re: [dev] OTRS Ajax/JSON Issues
I was able to get my Ajax communication error message to go away, at least for now. I installed the apache2-mpm-worker module on Apache (description Multi-Processing Module implementing a hybrid multi-threaded multi-process web server). I used the following on Ubuntu 12.04: apt-get update apt-get install apache2-mpm-worker I am really not sure why that worked. Maybe because the JSON object is so large that it needs more threads(?). But so far the error message is gone. Thanks to all who sent me helpful information…Dan. *From:* Dan Stover [mailto:dsto...@emacinc.com] *Sent:* Monday, January 06, 2014 9:37 AM *To:* 'Development community of OTRS' *Subject:* RE: [dev] OTRS Ajax/JSON Issues Please note that this Ajax communication error only crops up when selecting an entry in either a drop down list or a multiselect box. Apparently there is some interaction with Ajax and JSON behind the scenes. *From:* Dan Stover [mailto:dsto...@emacinc.com ] *Sent:* Monday, January 06, 2014 6:51 AM *To:* Development community of OTRS *Subject:* Re: [dev] OTRS Ajax/JSON Issues Thanks, Martin, for your response. Actually i am running Otrs on Ubuntu 12.04. I found that information earlier and uninstalled JSON::XS but it didnt help. It appears to be something external to Otrs but i cant figure out what. Further assistance would be appreciated. Thanks again...Dan. On Jan 6, 2014 1:44 AM, "Martin Gruner" wrote: Hi Dan, you're running on Windows, right? Please see http://bugs.otrs.org/show_bug.cgi?id=7337. There is a fix available to disable JSON::XS on PerlEx. Alternatively, uninstall JSON::XS on your system and see if this makes the error go away. Regards, mg Am 02.01.14 20:51, schrieb Dan Stover: > I updated all the tables to InnoDB (otrs.MySQLInnoDBSwitch.pl) and still > am getting Ajax errors. I am getting the following error in > /var/log/apache2/error.log: > > [error] encountered object 'true', but neither allow_blessed nor > convert_blessed settings are enabled at /opt/otrs//Kernel/System/JSON.pm > line 107.\n > > Here is an entry from /var/log/apache2/access.log: > > 10.0.2.102 - - [02/Jan/2014:13:18:57 -0600] "POST /otrs/index.pl? > HTTP/1.1" 500 641 > "http://otrslamp.emacinc.com/otrs/index.pl?Action=AgentTicketProcess"; > "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0" > >>From /var/log/mysql/error.log: > > Version: '5.5.31-0ubuntu0.12.04.1' socket: '/var/run/mysqld/mysqld.sock' > port: 3306 (Ubuntu) > 140102 12:52:21 InnoDB: ERROR: the age of the last checkpoint is 9445506, > InnoDB: which exceeds the log group capacity 9433498. > InnoDB: If you are using big BLOB or TEXT rows, you must set the > InnoDB: combined size of log files at least 10 times bigger than the > InnoDB: largest such row. > > I have looked in the OTRS log and there is just normal things in there. Is > there any other log I should send? > > I have, as far as I can tell, gone through everything with a fine toothed > comb and cannot find the problem. > > Any advice would be greatly appreciated. Thanks in advance...Dan. > > -----Original Message- > From: Dan Stover [mailto:dsto...@emacinc.com] > Sent: Thursday, January 02, 2014 12:12 PM > To: 'Development community of OTRS' > Subject: RE: [dev] OTRS Ajax/JSON Issues > > I ran the script and nothing changed. I did notice that the > otrs.CheckDB.pl output said that my database is defined as InnoDB and my > tables are not the same (MYISAM). This is the same on the beta site, which > appears to be working correctly. Is this a big problem? I did a restore > but created the database myself, apparently with the wrong storage engine. > > > -Original Message- > From: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] On Behalf Of > Moritz Lenz > Sent: Thursday, January 02, 2014 10:06 AM > To: dev@otrs.org > Subject: Re: [dev] OTRS Ajax/JSON Issues > > > > On 01/02/2014 04:54 PM, Dan Stover wrote: >> I did not delete the caches. I guess I assumed that things like that >> would be done during the restore. Please let me know how to do that >> and I will give it a shot. > > There's a otrs.deleteCaches.pl script shipped with otrs. Run it. > ___ > OTRS mailing list: dev - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/dev > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev > ___ > OTRS mailing list: dev - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/dev > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev > -- Martin Gruner Senior Developer R&D OTRS AG Europaring 4 94315 Straubi
Re: [dev] OTRS Ajax/JSON Issues
Please note that this Ajax communication error only crops up when selecting an entry in either a drop down list or a multiselect box. Apparently there is some interaction with Ajax and JSON behind the scenes. *From:* Dan Stover [mailto:dsto...@emacinc.com] *Sent:* Monday, January 06, 2014 6:51 AM *To:* Development community of OTRS *Subject:* Re: [dev] OTRS Ajax/JSON Issues Thanks, Martin, for your response. Actually i am running Otrs on Ubuntu 12.04. I found that information earlier and uninstalled JSON::XS but it didnt help. It appears to be something external to Otrs but i cant figure out what. Further assistance would be appreciated. Thanks again...Dan. On Jan 6, 2014 1:44 AM, "Martin Gruner" wrote: Hi Dan, you're running on Windows, right? Please see http://bugs.otrs.org/show_bug.cgi?id=7337. There is a fix available to disable JSON::XS on PerlEx. Alternatively, uninstall JSON::XS on your system and see if this makes the error go away. Regards, mg Am 02.01.14 20:51, schrieb Dan Stover: > I updated all the tables to InnoDB (otrs.MySQLInnoDBSwitch.pl) and still > am getting Ajax errors. I am getting the following error in > /var/log/apache2/error.log: > > [error] encountered object 'true', but neither allow_blessed nor > convert_blessed settings are enabled at /opt/otrs//Kernel/System/JSON.pm > line 107.\n > > Here is an entry from /var/log/apache2/access.log: > > 10.0.2.102 - - [02/Jan/2014:13:18:57 -0600] "POST /otrs/index.pl? > HTTP/1.1" 500 641 > "http://otrslamp.emacinc.com/otrs/index.pl?Action=AgentTicketProcess"; > "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0" > >>From /var/log/mysql/error.log: > > Version: '5.5.31-0ubuntu0.12.04.1' socket: '/var/run/mysqld/mysqld.sock' > port: 3306 (Ubuntu) > 140102 12:52:21 InnoDB: ERROR: the age of the last checkpoint is 9445506, > InnoDB: which exceeds the log group capacity 9433498. > InnoDB: If you are using big BLOB or TEXT rows, you must set the > InnoDB: combined size of log files at least 10 times bigger than the > InnoDB: largest such row. > > I have looked in the OTRS log and there is just normal things in there. Is > there any other log I should send? > > I have, as far as I can tell, gone through everything with a fine toothed > comb and cannot find the problem. > > Any advice would be greatly appreciated. Thanks in advance...Dan. > > -----Original Message- > From: Dan Stover [mailto:dsto...@emacinc.com] > Sent: Thursday, January 02, 2014 12:12 PM > To: 'Development community of OTRS' > Subject: RE: [dev] OTRS Ajax/JSON Issues > > I ran the script and nothing changed. I did notice that the > otrs.CheckDB.pl output said that my database is defined as InnoDB and my > tables are not the same (MYISAM). This is the same on the beta site, which > appears to be working correctly. Is this a big problem? I did a restore > but created the database myself, apparently with the wrong storage engine. > > > -Original Message- > From: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] On Behalf Of > Moritz Lenz > Sent: Thursday, January 02, 2014 10:06 AM > To: dev@otrs.org > Subject: Re: [dev] OTRS Ajax/JSON Issues > > > > On 01/02/2014 04:54 PM, Dan Stover wrote: >> I did not delete the caches. I guess I assumed that things like that >> would be done during the restore. Please let me know how to do that >> and I will give it a shot. > > There's a otrs.deleteCaches.pl script shipped with otrs. Run it. > ___ > OTRS mailing list: dev - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/dev > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev > ___ > OTRS mailing list: dev - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/dev > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev > -- Martin Gruner Senior Developer R&D OTRS AG Europaring 4 94315 Straubing T: +49 (0)6172 681988 0 F: +49 (0)9421 56818 18 I: www.otrs.com/ Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: DE256610065 Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann (Vorsitzender), Christopher Kuhn, Sabine Riedel Einfache Planung, bessere Übersicht - Mit OTRS 3.3 einfach besseres Service Management - Jetzt downloaden und testen ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Re: [dev] OTRS Ajax/JSON Issues
Thanks, Martin, for your response. Actually i am running Otrs on Ubuntu 12.04. I found that information earlier and uninstalled JSON::XS but it didnt help. It appears to be something external to Otrs but i cant figure out what. Further assistance would be appreciated. Thanks again...Dan. On Jan 6, 2014 1:44 AM, "Martin Gruner" wrote: > Hi Dan, > you're running on Windows, right? > Please see http://bugs.otrs.org/show_bug.cgi?id=7337. There is a fix > available to disable JSON::XS on PerlEx. Alternatively, uninstall > JSON::XS on your system and see if this makes the error go away. > Regards, mg > > Am 02.01.14 20:51, schrieb Dan Stover: > > I updated all the tables to InnoDB (otrs.MySQLInnoDBSwitch.pl) and still > > am getting Ajax errors. I am getting the following error in > > /var/log/apache2/error.log: > > > > [error] encountered object 'true', but neither allow_blessed nor > > convert_blessed settings are enabled at /opt/otrs//Kernel/System/JSON.pm > > line 107.\n > > > > Here is an entry from /var/log/apache2/access.log: > > > > 10.0.2.102 - - [02/Jan/2014:13:18:57 -0600] "POST /otrs/index.pl? > > HTTP/1.1" 500 641 > > "http://otrslamp.emacinc.com/otrs/index.pl?Action=AgentTicketProcess"; > > "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 > Firefox/26.0" > > > >>From /var/log/mysql/error.log: > > > > Version: '5.5.31-0ubuntu0.12.04.1' socket: '/var/run/mysqld/mysqld.sock' > > port: 3306 (Ubuntu) > > 140102 12:52:21 InnoDB: ERROR: the age of the last checkpoint is > 9445506, > > InnoDB: which exceeds the log group capacity 9433498. > > InnoDB: If you are using big BLOB or TEXT rows, you must set the > > InnoDB: combined size of log files at least 10 times bigger than the > > InnoDB: largest such row. > > > > I have looked in the OTRS log and there is just normal things in there. > Is > > there any other log I should send? > > > > I have, as far as I can tell, gone through everything with a fine toothed > > comb and cannot find the problem. > > > > Any advice would be greatly appreciated. Thanks in advance...Dan. > > > > -Original Message- > > From: Dan Stover [mailto:dsto...@emacinc.com] > > Sent: Thursday, January 02, 2014 12:12 PM > > To: 'Development community of OTRS' > > Subject: RE: [dev] OTRS Ajax/JSON Issues > > > > I ran the script and nothing changed. I did notice that the > > otrs.CheckDB.pl output said that my database is defined as InnoDB and my > > tables are not the same (MYISAM). This is the same on the beta site, > which > > appears to be working correctly. Is this a big problem? I did a restore > > but created the database myself, apparently with the wrong storage > engine. > > > > > > -Original Message- > > From: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] On Behalf Of > > Moritz Lenz > > Sent: Thursday, January 02, 2014 10:06 AM > > To: dev@otrs.org > > Subject: Re: [dev] OTRS Ajax/JSON Issues > > > > > > > > On 01/02/2014 04:54 PM, Dan Stover wrote: > >> I did not delete the caches. I guess I assumed that things like that > >> would be done during the restore. Please let me know how to do that > >> and I will give it a shot. > > > > There's a otrs.deleteCaches.pl script shipped with otrs. Run it. > > ___ > > OTRS mailing list: dev - Webpage: http://otrs.org/ > > Archive: http://lists.otrs.org/pipermail/dev > > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev > > ___ > > OTRS mailing list: dev - Webpage: http://otrs.org/ > > Archive: http://lists.otrs.org/pipermail/dev > > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev > > > > -- > Martin Gruner > Senior Developer R&D > > OTRS AG > Europaring 4 > 94315 Straubing > > T: +49 (0)6172 681988 0 > F: +49 (0)9421 56818 18 > I: www.otrs.com/ > > Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, > USt-Nr.: DE256610065 > Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André > Mindermann (Vorsitzender), Christopher Kuhn, Sabine Riedel > > Einfache Planung, bessere Übersicht - Mit OTRS 3.3 einfach besseres > Service Management - Jetzt downloaden und testen > ___ > OTRS mailing list: dev - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/dev > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev > ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Re: [dev] OTRS Ajax/JSON Issues
Hi Dan, you're running on Windows, right? Please see http://bugs.otrs.org/show_bug.cgi?id=7337. There is a fix available to disable JSON::XS on PerlEx. Alternatively, uninstall JSON::XS on your system and see if this makes the error go away. Regards, mg Am 02.01.14 20:51, schrieb Dan Stover: > I updated all the tables to InnoDB (otrs.MySQLInnoDBSwitch.pl) and still > am getting Ajax errors. I am getting the following error in > /var/log/apache2/error.log: > > [error] encountered object 'true', but neither allow_blessed nor > convert_blessed settings are enabled at /opt/otrs//Kernel/System/JSON.pm > line 107.\n > > Here is an entry from /var/log/apache2/access.log: > > 10.0.2.102 - - [02/Jan/2014:13:18:57 -0600] "POST /otrs/index.pl? > HTTP/1.1" 500 641 > "http://otrslamp.emacinc.com/otrs/index.pl?Action=AgentTicketProcess"; > "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0" > >>From /var/log/mysql/error.log: > > Version: '5.5.31-0ubuntu0.12.04.1' socket: '/var/run/mysqld/mysqld.sock' > port: 3306 (Ubuntu) > 140102 12:52:21 InnoDB: ERROR: the age of the last checkpoint is 9445506, > InnoDB: which exceeds the log group capacity 9433498. > InnoDB: If you are using big BLOB or TEXT rows, you must set the > InnoDB: combined size of log files at least 10 times bigger than the > InnoDB: largest such row. > > I have looked in the OTRS log and there is just normal things in there. Is > there any other log I should send? > > I have, as far as I can tell, gone through everything with a fine toothed > comb and cannot find the problem. > > Any advice would be greatly appreciated. Thanks in advance...Dan. > > -----Original Message----- > From: Dan Stover [mailto:dsto...@emacinc.com] > Sent: Thursday, January 02, 2014 12:12 PM > To: 'Development community of OTRS' > Subject: RE: [dev] OTRS Ajax/JSON Issues > > I ran the script and nothing changed. I did notice that the > otrs.CheckDB.pl output said that my database is defined as InnoDB and my > tables are not the same (MYISAM). This is the same on the beta site, which > appears to be working correctly. Is this a big problem? I did a restore > but created the database myself, apparently with the wrong storage engine. > > > -Original Message- > From: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] On Behalf Of > Moritz Lenz > Sent: Thursday, January 02, 2014 10:06 AM > To: dev@otrs.org > Subject: Re: [dev] OTRS Ajax/JSON Issues > > > > On 01/02/2014 04:54 PM, Dan Stover wrote: >> I did not delete the caches. I guess I assumed that things like that >> would be done during the restore. Please let me know how to do that >> and I will give it a shot. > > There's a otrs.deleteCaches.pl script shipped with otrs. Run it. > ___ > OTRS mailing list: dev - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/dev > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev > ___ > OTRS mailing list: dev - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/dev > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev > -- Martin Gruner Senior Developer R&D OTRS AG Europaring 4 94315 Straubing T: +49 (0)6172 681988 0 F: +49 (0)9421 56818 18 I: www.otrs.com/ Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: DE256610065 Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann (Vorsitzender), Christopher Kuhn, Sabine Riedel Einfache Planung, bessere Übersicht - Mit OTRS 3.3 einfach besseres Service Management - Jetzt downloaden und testen ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Re: [dev] OTRS Ajax/JSON Issues
I updated all the tables to InnoDB (otrs.MySQLInnoDBSwitch.pl) and still am getting Ajax errors. I am getting the following error in /var/log/apache2/error.log: [error] encountered object 'true', but neither allow_blessed nor convert_blessed settings are enabled at /opt/otrs//Kernel/System/JSON.pm line 107.\n Here is an entry from /var/log/apache2/access.log: 10.0.2.102 - - [02/Jan/2014:13:18:57 -0600] "POST /otrs/index.pl? HTTP/1.1" 500 641 "http://otrslamp.emacinc.com/otrs/index.pl?Action=AgentTicketProcess"; "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0" >From /var/log/mysql/error.log: Version: '5.5.31-0ubuntu0.12.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) 140102 12:52:21 InnoDB: ERROR: the age of the last checkpoint is 9445506, InnoDB: which exceeds the log group capacity 9433498. InnoDB: If you are using big BLOB or TEXT rows, you must set the InnoDB: combined size of log files at least 10 times bigger than the InnoDB: largest such row. I have looked in the OTRS log and there is just normal things in there. Is there any other log I should send? I have, as far as I can tell, gone through everything with a fine toothed comb and cannot find the problem. Any advice would be greatly appreciated. Thanks in advance...Dan. -Original Message- From: Dan Stover [mailto:dsto...@emacinc.com] Sent: Thursday, January 02, 2014 12:12 PM To: 'Development community of OTRS' Subject: RE: [dev] OTRS Ajax/JSON Issues I ran the script and nothing changed. I did notice that the otrs.CheckDB.pl output said that my database is defined as InnoDB and my tables are not the same (MYISAM). This is the same on the beta site, which appears to be working correctly. Is this a big problem? I did a restore but created the database myself, apparently with the wrong storage engine. -Original Message- From: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] On Behalf Of Moritz Lenz Sent: Thursday, January 02, 2014 10:06 AM To: dev@otrs.org Subject: Re: [dev] OTRS Ajax/JSON Issues On 01/02/2014 04:54 PM, Dan Stover wrote: > I did not delete the caches. I guess I assumed that things like that > would be done during the restore. Please let me know how to do that > and I will give it a shot. There's a otrs.deleteCaches.pl script shipped with otrs. Run it. ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Re: [dev] OTRS Ajax/JSON Issues
I ran the script and nothing changed. I did notice that the otrs.CheckDB.pl output said that my database is defined as InnoDB and my tables are not the same (MYISAM). This is the same on the beta site, which appears to be working correctly. Is this a big problem? I did a restore but created the database myself, apparently with the wrong storage engine. -Original Message- From: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] On Behalf Of Moritz Lenz Sent: Thursday, January 02, 2014 10:06 AM To: dev@otrs.org Subject: Re: [dev] OTRS Ajax/JSON Issues On 01/02/2014 04:54 PM, Dan Stover wrote: > I did not delete the caches. I guess I assumed that things like that > would be done during the restore. Please let me know how to do that > and I will give it a shot. There's a otrs.deleteCaches.pl script shipped with otrs. Run it. ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Re: [dev] OTRS Ajax/JSON Issues
On 01/02/2014 04:54 PM, Dan Stover wrote: I did not delete the caches. I guess I assumed that things like that would be done during the restore. Please let me know how to do that and I will give it a shot. There's a otrs.deleteCaches.pl script shipped with otrs. Run it. ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Re: [dev] OTRS Ajax/JSON Issues
I did not delete the caches. I guess I assumed that things like that would be done during the restore. Please let me know how to do that and I will give it a shot. Thanks...Dan. -Original Message- From: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] On Behalf Of Moritz Lenz Sent: Thursday, January 02, 2014 9:33 AM To: dev@otrs.org Subject: Re: [dev] OTRS Ajax/JSON Issues On 01/02/2014 03:58 PM, Dan Stover wrote: > Thank you, Moritz, for your response. Sorry for the delayed response > on my part. > > More information: > > This problem cropped up (perhaps coincidentally) when I was trying to > move a work flow process from beta to live. Some of this had to be > manual and some export/import. There was also some customized code > that is used in certain situations. When this problem occurred, I > tried to solve it and was unsuccessful. I then went back to a previous > backup of OTRS and the problem was still there. I then restored from a > week before I did anything (when it was working fine) and the problem was still there. Did you delete all caches during the restore? OTRS is very eager to use the caches for performance reasons, and invalidates the caches whenever you change anything in the database through the OTRS code. When you change the database directly, you have to also invalidate the caches yourself. Also as Renee said, please look into your web server's error log (plus into the OTRS logs, if it logs into another location. Cheers, Moritz ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Re: [dev] OTRS Ajax/JSON Issues
On 01/02/2014 03:58 PM, Dan Stover wrote: Thank you, Moritz, for your response. Sorry for the delayed response on my part. More information: This problem cropped up (perhaps coincidentally) when I was trying to move a work flow process from beta to live. Some of this had to be manual and some export/import. There was also some customized code that is used in certain situations. When this problem occurred, I tried to solve it and was unsuccessful. I then went back to a previous backup of OTRS and the problem was still there. I then restored from a week before I did anything (when it was working fine) and the problem was still there. Did you delete all caches during the restore? OTRS is very eager to use the caches for performance reasons, and invalidates the caches whenever you change anything in the database through the OTRS code. When you change the database directly, you have to also invalidate the caches yourself. Also as Renee said, please look into your web server's error log (plus into the OTRS logs, if it logs into another location. Cheers, Moritz ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Re: [dev] OTRS Ajax/JSON Issues
On 02.01.2014 15:58, Dan Stover wrote: > Error during AJAX communication. Status: error, Error: Internal Server > Error What does the webserver error log say? You should find more information there. - Renée -- Perl / OTRS development: http://perl-services.de OTRS AddOn repository: http://opar.perl-services.de ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Re: [dev] OTRS Ajax/JSON Issues
Thank you, Moritz, for your response. Sorry for the delayed response on my part. More information: This problem cropped up (perhaps coincidentally) when I was trying to move a work flow process from beta to live. Some of this had to be manual and some export/import. There was also some customized code that is used in certain situations. When this problem occurred, I tried to solve it and was unsuccessful. I then went back to a previous backup of OTRS and the problem was still there. I then restored from a week before I did anything (when it was working fine) and the problem was still there. Not sure why that is the case. My only other option is restore the whole virtual machine, not just OTRS. I was rather not do that and instead solve the problem if possible so it won't happen again. I still need to put up the work flow into production. In regard to what you said about the user records being incomplete, I would think that a full restore from when everything was working would make that correct. I f you can tell me how to check that, I can do that. Here is the error message (generated when an item is selected from a dynamic field drop down list or multiselect box): Error during AJAX communication. Status: error, Error: Internal Server Error In the Net tab of firebug , it blows up when doing a POST against the index.pl of the server with a 500 Internal Server Error. It is going against port 80 and it shows 104ms. The headers tab shows the following: Connection close Content-Encodinggzip Content-Length 402 Content-Typetext/html; charset=iso-8859-1 DateFri, 27 Dec 2013 22:34:04 GMT Server Apache/2.2.22 (Ubuntu) VaryAccept-Encoding Request Headersview source Accept application/json, text/javascript, */*; q=0.01 Accept-Encoding gzip, deflate Accept-Language en-US,en;q=0.5 Cache-Control no-cache Connection keep-alive Content-Length 709 Content-Typeapplication/x-www-form-urlencoded; charset=UTF-8 Cookie __utma=195136568.708832505.1344630644.1386606342.1386775185.17; __utmz=195136568.1344630644.1.1.utmcsr=10.0.2.167:8080|utmccn=(referral)|u tmcmd=referral|utmcct=/web/blake/profile; SCREEN_NAME=6f41424a674c304a4358716239344b6937364e67486363793063732b753761 2b; OTRSAgentInterface=10e59a784de188e30b1a17be0a166fa882 Hostotrslamp.emacinc.com Pragma no-cache Referer http://otrslamp.emacinc.com/otrs/index.pl?Action=AgentTicketProcess User-Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 X-ClickOnceSupport ( .NET CLR 3.5.30729; .NET4.0E) X-Requested-WithXMLHttpRequest The Post Tab shows the following: TicketID ;ProcessEntityID=P7;ActivityDialogEntityID=AD2;Expand=;AJAXDialog=1;FormID =1388183642.11254158.1332558;DynamicField_EPN=;DynamicField_DepartmentRout edTo=DR1;DynamicField_RequestedCompletionDateMonth=12;DynamicField_Request edCompletionDateDay=27;DynamicField_RequestedCompletionDateYear=2013;Dynam icField_ItemChangeType=ICT2;DynamicField_RequestersComments=;DynamicField_ AssociatedOrder=;DynamicField_AssociatedProductStepInfo=APS3;DynamicField_ AssociatedProducts=;DynamicField_PartDesc=;DynamicField_AssociatedProductR oHSStatus=APR1;DynamicField_Status=Approval;;ChallengeToken=f96fa8bfb4c17e d248824cdf4c0a2b11;Action=AgentTicketProcess;Subaction=AJAXUpdate;ElementC hanged=DynamicField_ItemChangeType Source TicketID=;ProcessEntityID=P7;ActivityDialogEntityID=AD2;Expand=;AJAXDialog =1;FormID=1388183642.11254158.1332558;DynamicField_EPN=;DynamicField_Depar tmentRoutedTo=DR1;DynamicField_RequestedCompletionDateMonth=12;DynamicFiel d_RequestedCompletionDateDay=27;DynamicField_RequestedCompletionDateYear=2 013;DynamicField_ItemChangeType=ICT2;DynamicField_RequestersComments=;Dyna micField_AssociatedOrder=;DynamicField_AssociatedProductStepInfo=APS3;Dyna micField_AssociatedProducts=;DynamicField_PartDesc=;DynamicField_Associate dProductRoHSStatus=APR1;DynamicField_Status=Approval;;ChallengeToken=f96fa 8bfb4c17ed248824cdf4c0a2b11;Action=AgentTicketProcess;Subaction=AJAXUpdate ;ElementChanged=DynamicField_ItemChangeType The response tab shows the following: 500 Internal Server Error Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@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. Apache/2.2.22 (Ubuntu) Server at otrslamp.emacinc.com Port 80 Please let me know if I can provide further information. I need to get this resolved as soon as possible. Thanks in advance...Dan Stover. -Original Message- From: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] On Behalf Of Moritz Lenz Sent: Saturday, December 28, 2013 10:16 AM To: dev@otrs.org Subject: Re: [dev] OTRS Ajax/JSON Issues Hi Dan, On 12/28/2013 04:44 PM, Dan Stover wrote: &
Re: [dev] OTRS Ajax/JSON Issues
Hi Dan, On 12/28/2013 04:44 PM, Dan Stover wrote: I am running OTRS 3.2.7 and have a beta system running at the same time. A while back, I ran into an issue on the live system where, when a user selects an item from a dynamic field drop down list, an Ajax communications error is generated. This does not happen on the beta system on the same virtual machine. Could you please be more specific? What's that error message? If you do it in firefox with firebug enabled, what does the "Net" tab show? Are there any error messages in the log? FWIW I could imagine that an incomplete user record in the database causes server-side errors, and that would explain why you don't see the same error in beta (which hopefully uses a different database). It appears to be related to the following call in AgentTicketProcess.pm but is endemic through the entire live system (only with drop down lists and multiselect boxes); my $JSON = $Self->{LayoutObject}->BuildSelectionJSON( [@JSONCollector] ); Any advice would be appreciated. Thanks…Dan. Cheers, Moritz ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
[dev] OTRS Ajax/JSON Issues
I am running OTRS 3.2.7 and have a beta system running at the same time. A while back, I ran into an issue on the live system where, when a user selects an item from a dynamic field drop down list, an Ajax communications error is generated. This does not happen on the beta system on the same virtual machine. It appears to be related to the following call in AgentTicketProcess.pm but is endemic through the entire live system (only with drop down lists and multiselect boxes); my $JSON = $Self->{LayoutObject}->BuildSelectionJSON( [@JSONCollector] ); Any advice would be appreciated. Thanks…Dan. ___ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev