[pgpool-general: 2687] Re: OTRS

[Tatsuo Ishii]

Humm.. there's no error messages in the pgpool log. Maybe the
replication lag? To make sure that if that is the cause of the
problem, you could set the slave's backend weight to 0 and restart
pgpool-II.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> We compiled the current stable pgPool 3.3.3 from source, as We're seeing it
> the OTRS is almost everywhere working fine.
> 
> Unfortunately we found the following errors in the OTRS log.  When we
> aren't using pgPool, everything is working well.
> 
> Mar 26 16:47:43 hera OTRS-CGI-10[11438]:
> [Error][Kernel::System::Ticket::HistoryAdd][Line:5066]: Need TicketID!
> Mar 26 16:47:43 hera OTRS-CGI-10[11438]:
> [Error][Kernel::System::Ticket::HistoryAdd][Line:5066]: Need TicketID!
> Mar 26 16:47:43 hera OTRS-CGI-10[11438]:
> [Error][Kernel::System::Ticket::HistoryAdd][Line:5066]: Need TicketID!
> Mar 26 16:47:43 hera OTRS-CGI-10[11438]:
> [Error][Kernel::System::Ticket::IndexAccelerator::StaticDB::TicketAcceleratorAdd][Line:147]:
> Need TicketID!
> Mar 26 16:47:43 hera OTRS-CGI-10[11438]:
> [Error][Kernel::System::Ticket::Event::TicketEscalationIndex::Run][Line:42]:
> Need TicketID in Data!
> Mar 26 16:47:43 hera OTRS-CGI-10[11438]:
> [Error][Kernel::System::Ticket::TicketNumberLookup][Line:747]: Need
> TicketID!
> Mar 26 16:47:43 hera OTRS-CGI-10[11438]:
> [Error][Kernel::System::Ticket::Article::ArticleSend][Line:2023]: Need
> TicketID!
> Mar 26 16:47:43 hera OTRS-CGI-10[11438]:
> [Error][Kernel::System::Ticket::Event::NotificationEvent::Run][Line:68]:
> Need TicketID in Data!
> Mar 26 16:47:43 hera OTRS-CGI-10[11438]:
> [Error][Kernel::System::Ticket::Event::GenericAgent::Run][Line:49]: Need
> TicketID! in Data
> Mar 26 16:47:43 hera OTRS-CGI-10[11438]:
> [Error][Kernel::System::Ticket::Event::TicketProcessTransitions::Run][Line:55]:
> Need TicketID in Data!
> 
> 
> We're sending our pgPool config and detailed pgPool log files as attachment.
> 
> 
> Have you got some ideas, how can we solve this problem?
> 
> Thx,
> Csaba
> 
> 
> 2014-03-20 0:41 GMT+01:00 Tatsuo Ishii <ishii at postgresql.org>:
> 
>> > We compiled the current code from git repo (version 3.4-alpha1
>> > (tataraboshi), and tested OTRS.
>> >
>> > As I seen the OTRS and working fine.
>>
>> Great!
>>
>> > Can we use the 3.4-alpha1 version in production area?
>> > Whats the planned release date of the stable 3.4 version?
>> > (We would like to use the official apt.postgres.org packages, if it
>> > possible)
>>
>> The release date of 3.4 is not determined yet. I do not recommend to
>> use 3.4-alpha1 for production use.
>>
>> However 3.3.3 will be released soon (24th of this month), which is a
>> bug fix version of 3.3.2. The same fix I reffered to is included in
>> 3.3.3 as well.
>>
>> You might want to try supposed-to-be-3.3.3 source at:
>>
>>
>> http://git.postgresql.org/gitweb/?p=pgpool2.git;a=shortlog;h=refs/heads/V3_3_STABLE
>>
>> Best regards,
>> --
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>> Japanese: http://www.sraoss.co.jp
>>
>> > Thx,
>> > Csaba
>> >
>> >
>> >
>> > 2014-03-12 6:25 GMT+01:00 Tatsuo Ishii <ishii at postgresql.org>:
>> >
>> >> Seems the bug fixed in
>> >>
>> >>
>> >>
>> http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=35437fa5eada74e181a7940b4917ea6560a75ade
>> >>
>> >> Can you please try it out?
>> >>
>> >> Best regards,
>> >> --
>> >> Tatsuo Ishii
>> >> SRA OSS, Inc. Japan
>> >> English: http://www.sraoss.co.jp/index_en.php
>> >> Japanese: http://www.sraoss.co.jp
>> >>
>> >> > Hello,
>> >> >
>> >> > Thanks for your answer.
>> >> > A tried it with log_per_node_statement. I'm sending more detailed log.
>> >>
>>