Topic Resolution: Answered
Viewing 4 reply threads
  • Author
    Posts
    • #10849
      Answered
      crythias
      Participant

      I’m trying to locate where the hangup is with regard to the tickets.

      I can see them under my OTRSv6 dashboard, but they’re blank under OTOBO.

      I have these:

      [Wed Feb 10 20:30:34.250263 2021] [mpm_prefork:notice] [pid 2406121] AH00169: caught SIGTERM, shutting down
      [Wed Feb 10 20:30:35.073474 2021] [mpm_prefork:notice] [pid 2416610] AH00163: Apache/2.4.41 (Ubuntu) mod_perl/2.0.11 Perl/v5.30.0 configured — resuming normal operations
      [Wed Feb 10 20:30:35.073582 2021] [core:notice] [pid 2416610] AH00094: Command line: ‚/usr/sbin/apache2‘
      [Wed Feb 10 20:32:19 2021] -e: Use of uninitialized value within %Queues in hash element at /opt/otobo/Kernel/Output/HTML/Dashboard/TicketQueueOverview.pm line 171.
      [Wed Feb 10 20:32:19 2021] -e: Use of uninitialized value within %Queues in hash element at /opt/otobo/Kernel/Output/HTML/Dashboard/TicketQueueOverview.pm line 171.
      [Wed Feb 10 20:32:19 2021] -e: Use of uninitialized value within %Queues in hash element at /opt/otobo/Kernel/Output/HTML/Dashboard/TicketQueueOverview.pm line 171.

       

      But syslog and journalctl -r doesn’t show anything.

      I can’t connect to the admin portal, but reverting to OTRS v6 I can.

      When I try the admin portal in Otobo, I get kicked out and permission denied.

       

       

    • #10850
      crythias
      Participant

      The database has tickets and articles…

       

      • #10851
        Best Answer
        crythias
        Participant

        never mind at the moment. didn’t run migration.pl before posting.

    • #10852
      crythias
      Participant

      Migrate web service configuration.

      Failed – see the log!

       

      Where’s the log?

    • #10853
      crythias
      Participant

      found some things in /var/log/apache2/error.log

      ERROR: OTOBO-CGI-17 Perl: 5.30.0 OS: linux Time: Wed Feb 10 20:49:04 2021

      Message: Setting Ticket::Type::Default Effective value is not correct: Entity value is invalid(Support)!

      ERROR: OTOBO-CGI-17 Perl: 5.30.0 OS: linux Time: Wed Feb 10 20:50:15 2021

      Message: Duplicate entry ‚1‘ for key ‚PRIMARY‘, SQL: ‚INSERT INTO gi_webservice_config (id, name, config, valid_id, create_by, create_time, change_by, change_time)
      VALUES
      (1, ‚Elasticsearch‘, ‚—
      Debugger:

      Message: Could not execute INSERT INTO gi_webservice_config (id, name, config, valid_id, create_by, create_time, change_by, change_time)
      VALUES
      (1, ‚Elasticsearch‘, ‚—

       

      This I think

    • #10854
      Sven Oesterling
      Keymaster

      Hi Crythias,

      yes, this is the bug mentioned in my answer in the other topic. It will be resolved in OTOBO 10.0.8 which is planned to be released tomorrow. As you are almost done with the migration, though, you might want to download the current version of https://github.com/RotherOSS/otobo/blob/rel-10_0/Kernel/System/MigrateFromOTRS/OTOBOMigrateWebServiceConfiguration.pm (right click on raw and save it) and replace the file in your installation. It will work then.

      The error above the webservices could lead to some trouble. Invalid sysconfig settings have to be resolved by hand (and it’s better done before migration). But I’m not 100% sure that it won’t work, just from the logs. As mentioned in the other post, you should be able to just restart the migration where you left, after replacing the file.

      (If you run into errors regarding the Sysconfig, please try /opt/otrs/bin/otrs.Console.pl Admin::Config::ListInvalid on the source system. You can try fixing things on the otobo side, later, too – for me this worked in more than one cases, but I’m not sure about docker e.g.)

      Sven

Viewing 4 reply threads
  • You must be logged in to reply to this topic.