Debian Update: tzdata different version

Hilfe zu OTRS Problemen aller Art
Post Reply
Simon74
Znuny newbie
Posts: 20
Joined: 11 Mar 2015, 10:29
Znuny Version: OTRS5

Debian Update: tzdata different version

Post by Simon74 »

Gestern wurde OTRS von 6.0.14 auf 6.0.15 aktualisiert, erfolgreich.
Heute wurde Debian Stretch aktualisiert. (apt update : apt upgrade), erfolgreich.

Seit dem Debian Update ist das OTRS Webinterface nicht mehr erreichbar.

Vom System wurde uns ein mail mit folgendem Inhalt gesendet:

Code: Select all

[Thu Dec 20 09:49:01 2018] otrs.Daemon.pl: Loaded DateTime::TimeZone::Europe::Vienna, which is from a different version (2018g) of the Olson database than this installation of DateTime::TimeZone (2018b).
Weitere Informationen:

Code: Select all

root@tic /opt/otrs/bin >  su -c "./otrs.CheckModules.pl" -s /bin/bash otrs
  o Apache::DBI......................ok (v1.12)
  o Apache2::Reload..................ok (v0.13)
  o Archive::Tar.....................ok (v2.04_01)
  o Archive::Zip.....................ok (v1.59)
  o Crypt::Eksblowfish::Bcrypt.......ok (v0.009)
  o Crypt::SSLeay....................ok (v0.73_04)
  o Date::Format.....................ok (v2.24)
  o DateTime.........................ok (v1.42)
  o DBI..............................ok (v1.636)
  o DBD::mysql.......................ok (v4.041)
  o DBD::ODBC........................ok (v1.56)
  o DBD::Oracle......................Not installed! (optional - Required to connect to a Oracle database.)
  o DBD::Pg..........................Not installed! Use: 'apt-get install -y libdbd-pg-perl' (optional - Required to connect to a PostgreSQL database.)
  o Digest::SHA......................ok (v5.95_01)
  o Encode::HanExtra.................ok (v0.23)
  o IO::Socket::SSL..................ok (v2.044)
  o JSON::XS.........................ok (v3.03)
  o List::Util::XS...................ok (v1.47)
  o LWP::UserAgent...................ok (v6.26)
  o Mail::IMAPClient.................ok (v3.38)
    o IO::Socket::SSL................ok (v2.044)
    o Authen::SASL...................ok (v2.16)
    o Authen::NTLM...................ok (v1.09)
  o ModPerl::Util....................ok (v2.000010)
  o Net::DNS.........................ok (v1.07)
  o Net::LDAP........................ok (v0.65)
  o Template.........................ok (v2.24)
  o Template::Stash::XS..............ok (undef)
  o Text::CSV_XS.....................ok (v1.26)
  o Time::HiRes......................ok (v1.9733)
  o XML::LibXML......................ok (v2.0128)
  o XML::LibXSLT.....................ok (v1.95)
  o XML::Parser......................ok (v2.44)
  o YAML::XS.........................ok (v0.63)

Code: Select all

root@tic /opt/otrs/bin >  su -c "./otrs.Daemon.pl status" -s /bin/bash otrs

Manage the OTRS daemon process.

Daemon running

Code: Select all

root@tic /opt/otrs/bin > date
Do 20. Dez 13:33:59 CET 2018

Code: Select all

root@tic /opt/otrs/bin > cat /var/log/apache2/error.log
[Thu Dec 20 13:19:23.914103 2018] [mpm_prefork:notice] [pid 2032] AH00163: Apache/2.4.25 (Debian) OpenSSL/1.0.2q mod_perl/2.0.10 Perl/v5.24.1 configured -- resuming normal operations
[Thu Dec 20 13:19:23.914152 2018] [core:notice] [pid 2032] AH00094: Command line: '/usr/sbin/apache2'
[Thu Dec 20 13:19:40.932053 2018] [core:notice] [pid 2032] AH00052: child pid 2037 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:41.936144 2018] [core:notice] [pid 2032] AH00052: child pid 2038 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:41.936185 2018] [core:notice] [pid 2032] AH00052: child pid 2039 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:41.936199 2018] [core:notice] [pid 2032] AH00052: child pid 2040 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:41.936211 2018] [core:notice] [pid 2032] AH00052: child pid 2041 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:41.936220 2018] [core:notice] [pid 2032] AH00052: child pid 2064 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:42.943220 2018] [core:notice] [pid 2032] AH00052: child pid 2065 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:42.943256 2018] [core:notice] [pid 2032] AH00052: child pid 2066 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:43.955095 2018] [core:notice] [pid 2032] AH00052: child pid 2067 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:43.955130 2018] [core:notice] [pid 2032] AH00052: child pid 2068 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:49.961470 2018] [core:notice] [pid 2032] AH00052: child pid 2069 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:49.961516 2018] [core:notice] [pid 2032] AH00052: child pid 2070 exit signal Segmentation fault (11)
[Thu Dec 20 13:19:54.966758 2018] [core:notice] [pid 2032] AH00052: child pid 2072 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:22.296234 2018] [core:notice] [pid 2032] AH00052: child pid 2071 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:22.296307 2018] [core:notice] [pid 2032] AH00052: child pid 2073 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:22.296330 2018] [core:notice] [pid 2032] AH00052: child pid 2074 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:22.296357 2018] [core:notice] [pid 2032] AH00052: child pid 2075 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:22.296370 2018] [core:notice] [pid 2032] AH00052: child pid 2077 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:22.296384 2018] [core:notice] [pid 2032] AH00052: child pid 2078 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:23.300274 2018] [core:notice] [pid 2032] AH00052: child pid 2204 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:24.307296 2018] [core:notice] [pid 2032] AH00052: child pid 2205 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:24.307333 2018] [core:notice] [pid 2032] AH00052: child pid 2206 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:25.320263 2018] [core:notice] [pid 2032] AH00052: child pid 2207 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:25.320299 2018] [core:notice] [pid 2032] AH00052: child pid 2208 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:25.320306 2018] [core:notice] [pid 2032] AH00052: child pid 2209 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:25.320311 2018] [core:notice] [pid 2032] AH00052: child pid 2210 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:26.344458 2018] [core:notice] [pid 2032] AH00052: child pid 2211 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:26.344501 2018] [core:notice] [pid 2032] AH00052: child pid 2212 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:26.344507 2018] [core:notice] [pid 2032] AH00052: child pid 2213 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:26.344512 2018] [core:notice] [pid 2032] AH00052: child pid 2214 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:26.344517 2018] [core:notice] [pid 2032] AH00052: child pid 2215 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:26.344521 2018] [core:notice] [pid 2032] AH00052: child pid 2216 exit signal Segmentation fault (11)
[Thu Dec 20 13:25:26.344527 2018] [core:notice] [pid 2032] AH00052: child pid 2217 exit signal Segmentation fault (11)

Code: Select all

root@tic /opt/otrs/bin > l /etc/localtime
0 lrwxrwxrwx 1 root root 33 Dez 20 13:18 /etc/localtime -> /usr/share/zoneinfo/Europe/Vienna
Last edited by Simon74 on 13 Mar 2019, 18:04, edited 2 times in total.
wurzel
Znuny guru
Posts: 3224
Joined: 08 Jul 2010, 22:25
Znuny Version: x.x.x
Real Name: Florian

Re: Debian Update: Webinterface nicht mehr erreichbar

Post by wurzel »

Servus,

Rollback auf die Vorherige Version. Du hast ja sicher 'n Backup.


Oder starte den Daemon neu

viele Grüße
Flo
OTRS 8 SILVER (Prod)
OTRS 8 auf Debian 11 (Test)
Znuny 7.x latest version testing auf Debian 11

-- Ich beantworte keine Forums-Fragen PN - No PN please

I won't answer to unfriendly users any more. A greeting and regards are just polite.
Simon74
Znuny newbie
Posts: 20
Joined: 11 Mar 2015, 10:29
Znuny Version: OTRS5

Re: Debian Update: Webinterface nicht mehr erreichbar

Post by Simon74 »

Daemon stoppen, starten scheint nicht das Problem zu sein..

Code: Select all

root@tic /opt/otrs/bin >  su -c "./otrs.Daemon.pl start --debug" -s /bin/bash otrs

Manage the OTRS daemon process.

Daemon started

Debug information is stored in the daemon log files localed under: /opt/otrs/var/log/Daemon

Registered Daemon Kernel::System::Daemon::DaemonModules::SchedulerCronTaskManager with PID 2525
Registered Daemon Kernel::System::Daemon::DaemonModules::SchedulerFutureTaskManager with PID 2526
Registered Daemon Kernel::System::Daemon::DaemonModules::SchedulerGenericAgentTaskManager with PID 2527
Registered Daemon Kernel::System::Daemon::DaemonModules::SchedulerTaskWorker with PID 2528
Registered Daemon Kernel::System::Daemon::DaemonModules::SystemConfigurationSyncManager with PID 2529
root@tic /opt/otrs/bin >     Daemon: SystemConfigurationSyncManager Executes function: ConfigurationDeploySync
    Worker: Cron Executes task: ArticleSearchIndexRebuild
No indexing needed! Skipping...
Done.
    Worker: Cron Executes task: MailQueueSend

No messages available for sending.
Done.

    Daemon: SystemConfigurationSyncManager Executes function: ConfigurationDeploySync
    Worker: Cron Executes task: MailAccountFetch

Spawning child process to fetch incoming messages from mail accounts...

    Worker: Cron Executes task: ArticleSearchIndexRebuild
srvmail2.domain.at (POP3)...
No indexing needed! Skipping...
Done.
POP3: Connection to srvmail2.domain.at closed.

srvmail2.domain.at (POP3)...
POP3: Connection to srvmail2.domain.at closed.

    Worker: Cron Executes task: MailQueueSend

No messages available for sending.
Done.

Done.
Problem scheint das zu sein ?

Code: Select all

otrs.Daemon.pl: Loaded DateTime::TimeZone::Europe::Vienna, which is from a different version (2018g) of the Olson database than this installation of DateTime::TimeZone (2018b).
wurzel
Znuny guru
Posts: 3224
Joined: 08 Jul 2010, 22:25
Znuny Version: x.x.x
Real Name: Florian

Re: Debian Update: Webinterface nicht mehr erreichbar

Post by wurzel »

Hi,

also bei mir ging's immer mitm Daemon Neustart. Dann weiß ich auch nicht.


viele Grüße
Flo
OTRS 8 SILVER (Prod)
OTRS 8 auf Debian 11 (Test)
Znuny 7.x latest version testing auf Debian 11

-- Ich beantworte keine Forums-Fragen PN - No PN please

I won't answer to unfriendly users any more. A greeting and regards are just polite.
Simon74
Znuny newbie
Posts: 20
Joined: 11 Mar 2015, 10:29
Znuny Version: OTRS5

Re: Debian Update: Webinterface nicht mehr erreichbar

Post by Simon74 »

Backup von gestern zurückgespielt.
Diesmal gleich zuerst das Debian-Stretch Update gemacht (otrs 6.0.14).

Und wieder dasselbe Problem, Ergebniss nach Update: Mail kommt und OTRS WEBIF geht nicht mehr:

Code: Select all

otrs.Daemon.pl: Loaded DateTime::TimeZone::Europe::Vienna, which is from a different version (2018g) of the Olson database than this installation of DateTime::TimeZone (2018b)

Code: Select all

root@tic ~ > cat /etc/timezone
Europe/Vienna
Im OTRS ist das stimmig:

Code: Select all

UserDefaultTimeZone: Europe/Vienna
OTRSTimeZone: Europe/Vienna
Ein Hinweis wäre schön..
root
Administrator
Posts: 3934
Joined: 18 Dec 2007, 12:23
Znuny Version: Znuny and Znuny LTS
Real Name: Roy Kaldung
Company: Znuny
Contact:

Re: Debian Update: Webinterface nicht mehr erreichbar

Post by root »

Hi,

Es gibt da wohl ein Problem/Bug mit dem tzdata in Berbindung mit OTRS. Einfach mal das entsprechende Debian Paket eine Version zurück.

- Roy
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO

Use a test system - always.

Do you need professional services? Check out https://www.znuny.com/

Do you want to contribute or want to know where it goes ?
Simon74
Znuny newbie
Posts: 20
Joined: 11 Mar 2015, 10:29
Znuny Version: OTRS5

Re: Debian Update: Webinterface nicht mehr erreichbar

Post by Simon74 »

Vielen Dank.

ich werde mit Updates mal abwarten bis 6.0.16..
Simon74
Znuny newbie
Posts: 20
Joined: 11 Mar 2015, 10:29
Znuny Version: OTRS5

Re: Debian Update: Webinterface nicht mehr erreichbar

Post by Simon74 »

Ich habe jetzt auf OTRS 6.0.17 aktualisiert, und läuft.
Sobald ich jedoch das Debian darunter aktualisiere, kommt wieder dasselbe Problem:

Code: Select all

OTRS-otrs.Console.pl-Maint::Email::MailQueue-74[19566]: [Error][Kernel::System::Daemon::DaemonModules::BaseTaskWorker::_HandleError][Line:52]: There was an error executing Execute() in Kernel::System::Console::Command::Maint::Email::MailQueue: [Wed Mar 13 16:24:13 2019] otrs.Daemon.pl: Loaded DateTime::TimeZone::Europe::Vienna, which is from a different version (2018i) of the Olson database than this installation of DateTime::TimeZone (2018b)
Vor dem Debian Update hat tzdata die Version:

Code: Select all

root@tic ~ > dpkg -l | grep tzdata
ii  tzdata                            2018c-0+deb9u1                 all          time zone and daylight-saving time data
Jemand eine Idee wie dieses Problem zu lösen ist ?
root
Administrator
Posts: 3934
Joined: 18 Dec 2007, 12:23
Znuny Version: Znuny and Znuny LTS
Real Name: Roy Kaldung
Company: Znuny
Contact:

Re: Debian Update: tzdata different version

Post by root »

Hi,

soweit ich mich erinnere gibt es da en Problem mit dem aktuellsten Paket der tzdata. Ich empfehle mal die Vorversion einzuspielen bzw. eine zu DateTime::TimeZone passende.

- Roy
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO

Use a test system - always.

Do you need professional services? Check out https://www.znuny.com/

Do you want to contribute or want to know where it goes ?
Post Reply