since CentOS 6.9 is End-of-Life we tried to migrate our OTRS 5.0.20 installation to a fresh Debian 10 installation with the same version number. Everything works fine, except the CalendarOverview "index.pl?Action=AgentAppointmentCalendarOverview" does not show any of the entries. If we look into the Database, these entries are still there, adding new entries also works and the agent agenda list these items properly.
I threw on Firefox Developer Tools on the test-migration-vm and on the currently-in-production-vm and found a difference. When the site loads up, it does a POST request to the otrs server to get the calendar information as json. However, on the new installation, the same request returns the login page of the server.
We have two snapshots at the moment for trying this issue out, the current otrs 5.0.20 and a znuny 6.0.35 updated from the former.
I have several leads on this topic and might be able to get to the answer myself with a small nudge:
1. The perl module versions. The new VM is on Perl 5.28, the production VM is on Perl 5.10.1. The Calendar supposedly uses libdatetime-perl and libdatetime-timezone-perl which are installed. This could result in the relevant code to fail, but I cannot find any hint that perl code might be running into errors
2. The request for the AgentAppointmentList doesn't go through / it doesn't start the module.
I wanted to see if I could debug the module myself and resolve the version. To start off, I edited the file /opt/otrs/Kernel/Modules/AgendAppointmentList.pm and added log statements at the start of Run and New as a sanity check if these functions are relevant.
Code: Select all
# --
# Copyright (C) 2001-2021 xxx, https://otrs.com/
# Copyright (C) 2021 Znuny GmbH, https://znuny.org/
# --
# This software comes with ABSOLUTELY NO WARRANTY. For details, see
# the enclosed file COPYING for license information (GPL). If you
# did not receive this file, see https://www.gnu.org/licenses/gpl-3.0.txt.
# --
package Kernel::Modules::AgentAppointmentList;
use strict;
use warnings;
use Kernel::System::VariableCheck qw(:all);
our $ObjectManagerDisabled = 1;
sub new {
$Kernel::OM->Get('Kernel::System::Log')->Log(
Priority => 'error',
Message => 'AgentAppointmentList::new started',
);
(...)
}
sub Run {
$Kernel::OM->Get('Kernel::System::Log')->Log(
Priority => 'error',
Message => 'AgentAppointmentList::run started',
);
(...)
The concrete questions I have right now are:
a) Where would be the settings that tells Znuny which requests are meant to run which .pm file?
b) The way I just edited the Kernel/Modules/AgentAppointmentList.pm, would that work in the first place, or do I have to do it differently?
c) Where can I see the required perl package versions / perl version for otrs5/ znuny6? otrs.CheckModules.pl returns OK for all packages on both versions.
Edit: I also already searched for similar help requests: viewtopic.php?f=62&t=40072 has the same origin os, but I mention more information here. There is also a german topic viewtopic.php?p=138425 that mentions clearing ZZZAuto.pm and incrementally adding the config back piecewise, but I do not know how that would apply to a Znuny 6 installation.