Systemlog filled with "Need Querystring!"

Moderator: crythias

Post Reply
PhyrePhoX
OTRS expert
Posts: 86
Joined: 05 Dec 2007, 10:56

Systemlog filled with "Need Querystring!"

Post by PhyrePhoX » 18 Jan 2018, 11:33

Hi, my systemlog shows this message repeatedly: "Need QueryString!"
Google does not seem to help here, how can i find out where this error comes from? Is it a userquery or a misconfigured view/template?

Thanks in advance,
PhoX
Screenshot from 2018-01-18 10-30-32.png
You do not have the required permissions to view the files attached to this post.

fcasal
OTRS wizard
Posts: 148
Joined: 21 Apr 2014, 16:14
OTRS Version?: 6.0.7

Re: Systemlog filled with "Need Querystring!"

Post by fcasal » 18 Jan 2018, 17:45

Check the apache logs for more information

PhyrePhoX
OTRS expert
Posts: 86
Joined: 05 Dec 2007, 10:56

Re: Systemlog filled with "Need Querystring!"

Post by PhyrePhoX » 25 Jan 2018, 10:41

thank you, i will try that :)

PhyrePhoX
OTRS expert
Posts: 86
Joined: 05 Dec 2007, 10:56

Re: Systemlog filled with "Need Querystring!"

Post by PhyrePhoX » 29 Mar 2018, 13:38

Now i found through apache logs & "reverse engineering", that this error is produced when i am in the "change customer" dialog, when i enter a string that does not match a customer (from one of my several backends). There is no error message in the gui/webfrontend, such as "didnt find the customer you were looking for", instead i am getting the "Need Querystring!" in the errorlogs.

Can this be prevented somehow? It is spamming my error log, and to me (personally), it is not really an error?
Is there a config option somewhere?


Apache Log Entry:
ERROR: OTRS-CGI-12 Perl: 5.24.1 OS: linux Time: Thu Mar 29 13:25:49 2018

Message: Need QueryString!

RemoteAddress: 192.168.XY.XY
RequestURI: /otrs/index.pl?Action=AgentTicketCustomer;TicketID=123

Traceback (15991):
Module: Kernel::System::DB::QueryStringEscape Line: 1593
Module: Kernel::Output::HTML::CustomerUser::GenericTicket::Run Line: 150
Module: Kernel::Output::HTML::Layout::Ticket::AgentCustomerViewTable Line: 308
Module: Kernel::Modules::AgentTicketCustomer::Form Line: 272
Module: Kernel::Modules::AgentTicketCustomer::Run Line: 230
Module: Kernel::System::Web::InterfaceAgent::Run Line: 1055
Module: ModPerl::ROOT::ModPerl::Registry::usr_share_otrs_bin_cgi_2dbin_index_2epl::handler Line: 40
Module: (eval) (v1.99) Line: 12
Module: ModPerl::RegistryCooker::run (v1.99) Line: 12
Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 173
Module: ModPerl::Registry::handler (v1.99) Line: 32

[Thu Mar 29 13:25:49 2018] -e: Use of uninitialized value in concatenation (.) or string at /usr/share/otrs//Kernel/Output/HTML/CustomerUser/GenericTicket.pm line 153.
[Thu Mar 29 13:25:49 2018] -e: Use of uninitialized value in concatenation (.) or string at /usr/share/otrs//Kernel/Output/HTML/CustomerUser/GenericTicket.pm line 135.
[Thu Mar 29 13:25:49 2018] -e: Use of uninitialized value in concatenation (.) or string at /usr/share/otrs//Kernel/Output/HTML/CustomerUser/GenericTicket.pm line 135.
ERROR: OTRS-CGI-12 Perl: 5.24.1 OS: linux Time: Thu Mar 29 13:25:49 2018

reneeb
OTRS guru
Posts: 4650
Joined: 13 Mar 2011, 09:54
OTRS Version?: 3.3.x
Company: Perl-Services.de
Contact:

Re: Systemlog filled with "Need Querystring!"

Post by reneeb » 29 Mar 2018, 13:51

Which OTRS version?
Perl / OTRS development: http://perl-services.de
Free OTRS add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de

PhyrePhoX
OTRS expert
Posts: 86
Joined: 05 Dec 2007, 10:56

Re: Systemlog filled with "Need Querystring!"

Post by PhyrePhoX » 29 Mar 2018, 13:53

5.0.24

fcasal
OTRS wizard
Posts: 148
Joined: 21 Apr 2014, 16:14
OTRS Version?: 6.0.7

Re: Systemlog filled with "Need Querystring!"

Post by fcasal » 01 Apr 2018, 20:51

Have you personalizated the GenericTicket.pm file? If not, you can update your installation to the last patch level, the 27.

PhyrePhoX
OTRS expert
Posts: 86
Joined: 05 Dec 2007, 10:56

Re: Systemlog filled with "Need Querystring!"

Post by PhyrePhoX » 05 Apr 2018, 13:38

i checked the changelog, didnt find a change that would reflect in stopping the "spam" in the log. Can you point me in the right direction? Since we have a tight update policy, i would like to manually patch the file, instead of updating. Thank you :)

Post Reply