Your message dated Wed, 4 Oct 2017 10:31:06 +0200 with message-id <[email protected]> and subject line Re: Bug#877675: otrs: Security upgrade leads to unusable OTRS system has caused the Debian Bug report #877675, regarding otrs: Security upgrade leads to unusable OTRS system to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 877675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877675 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: otrs Version: 3.1.7+dfsg1-8+deb7u5 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? The security upgrade for old version of OTRS 3.1.7+dfsg1-8+deb7u5 is currently 3.3.18-1~deb7u1 whoich leads to an unusable system. OTRS 3.1 and 3.3 differ in a way that for the upgrade to 3.3 also database tables should have been upgraded. As the security update does not alter the database structure, OTRS becomes unusable and throws errors like: Message: Unknown column 'f_not' in 'field list', SQL: 'SELECT f_type, f_key, f_value, f_name, f_stop, f_not FROM postmaster_filter WHERE f_name = ?' Traceback (25438): Module: Kernel::System::PostMaster::Filter::FilterGet (OTRS 3.3.18) Line: 208 Module: Kernel::System::PostMaster::Filter::MatchDBSource::Run (OTRS 3.3.18) Line: 54 Module: Kernel::System::PostMaster::Run (OTRS 3.3.18) Line: 230 Module: Kernel::System::MailAccount::POP3::Fetch (OTRS 3.3.18) Line: 208 Module: Kernel::System::MailAccount::MailAccountFetch (OTRS 3.3.18) Line: 450 Module: main::Fetch (unknown version) Line: 176 Module: /usr/share/otrs/bin/otrs.PostMasterMailbox.pl (unknown version) Line: 89 DBD::mysql::db do failed: Unknown column 'a_message_id_md5' in 'field list' at /usr/share/otrs/Kernel/System/DB.pm line 494. ERROR: OTRS-otrs.PostMasterMailbox.pl-10 Perl: 5.14.2 OS: linux Time: Tue Oct 3 13:20:03 2017 Message: Unknown column 'a_message_id_md5' in 'field list', SQL: 'INSERT INTO article (ticket_id, article_type_id, article_sender_type_id, a_from, a_reply_to, a_to, a_cc, a_subject, a_message_id, a_message_id_md5, a_in_reply_to, a_references, a_body, a_content_type, content_path, valid_id, incoming_time, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, '2017-10-03 13:20:03' , ?, '2017-10-03 13:20:03' , ?)' -- System Information: Debian Release: 7.11 APT prefers oldoldstable-updates APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages otrs depends on: ii otrs2 3.1.7+dfsg1-8+deb7u6 otrs recommends no packages. otrs suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Am 04.10.2017 um 09:37 schrieb Christof Thalhofer: > * What led up to the situation? > The security upgrade for old version of OTRS 3.1.7+dfsg1-8+deb7u5 is > currently 3.3.18-1~deb7u1 whoich leads to an unusable system. From your original mail to me you have stated, that you didn't upgraded / modified the database schema. This step is required if you are using MySQL with a default configuration and is impossible to be automated by the upgrade scripts. From README.Debian: 13 Upgrading to MySQL >= 5.5: 14 -------------------------- 15 16 Since MySQL 5.5 changed its default storage engine from MyISAM to InnoDB you 17 might encounter problems on upgrading OTRS from the 18 'otrs.Console.pl Maint::Database::Check' script. 19 20 Here you will find additional notes about this problem: 21 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707075 22 23 Here you will find a possible solution: 24 http://blog.otrs.org/2013/02/20/about-otrs-mysql-myisam-and-innodb-storage-engines/ Also have a look here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690306 Looks like upstream removed the old blog post > > OTRS 3.1 and 3.3 differ in a way that for the upgrade to 3.3 also > database tables should have been upgraded. As the security update > does not alter the database structure, OTRS becomes unusable and > throws errors like: > > Message: Unknown column 'f_not' in 'field list', SQL: 'SELECT f_type, > f_key, f_value, > f_name, f_stop, f_not FROM postmaster_filter WHERE f_name = ?' You have to upgrade the database schema, or OTRS could not work. That is not a bug. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: [email protected] [email protected] */
--- End Message ---
