Topic Resolution: Answered
Viewing 2 reply threads
  • Author
    Posts
    • #11326
      Answered
      Kyle F
      Participant

      Is there a best practices approach to migrating an existing OTRS install to Otobo? Any special way to install Otobo other than using the standard documentation?

      I have a fresh install of Otobo and am using the Migration.pl page to migration an existing OTRS install but keep running into user errors. I’ve created the same users on both systems. Even using the same MySql usernames. Any tips would be welcome. Thanks!

       

      [Error][Kernel::System::MigrateFromOTRS::OTOBOOTRSConnectionCheck::Run][Line:136]: Can’t open Kernel/Config.pm file from OTRSHome: /opt/otrs!
      [Error][Kernel::System::MigrateFromOTRS::CloneDB::Driver::Base::SanityChecks][Line:182]: Access denied for user ‚otrsdb’@’localhost‘ (using password: YES)
      [Error][Kernel::System::MigrateFromOTRS::CloneDB::Driver::Base::SanityChecks][Line:185]: Try database connect and sanity checks. Could not connect to the source database!
      [Error][Kernel::System::MigrateFromOTRS::CloneDB::Driver::Base::SanityChecks][Line:182]: Unknown database ‚otrs‘
      [Error][Kernel::System::MigrateFromOTRS::CloneDB::Driver::Base::SanityChecks][Line:185]: Try database connect and sanity checks. Could not connect to the source database!
      [Error][Kernel::System::MigrateFromOTRS::Base::MigrationLog][Line:1172]: Could not replace license header of /opt/otobo/Kernel/Config.pm.
      [Error][Kernel::System::Main::FileWrite][Line:515]: Can’t write ‚/opt/otobo/var/cron/otobo_daemon‘: Permission denied
      [Error][Kernel::System::SysConfig::SettingUpdate][Line:462]: Setting AdminEmail does not exist!
      [Error][Kernel::System::SysConfig::ConfigurationLoad][Line:4280]: Setting AdminEmail (global) was not correctly updated!
      [Error][Kernel::System::SysConfig::SettingUpdate][Line:462]: Setting FQDN does not exist!
      [Error][Kernel::System::SysConfig::ConfigurationLoad][Line:4280]: Setting FQDN (global) was not correctly updated!
      [Error][Kernel::System::SysConfig::SettingUpdate][Line:462]: Setting Organization does not exist!
      [Error][Kernel::System::SysConfig::ConfigurationLoad][Line:4280]: Setting Organization (global) was not correctly updated!
      [Error][Kernel::System::SysConfig::SettingUpdate][Line:462]: Setting SecureMode does not exist!
      [Error][Kernel::System::SysConfig::ConfigurationLoad][Line:4280]: Setting SecureMode (global) was not correctly updated!
      [Error][Kernel::System::SysConfig::SettingUpdate][Line:462]: Setting SystemID does not exist!
      [Error][Kernel::System::SysConfig::ConfigurationLoad][Line:4280]: Setting SystemID (global) was not correctly updated!
      [Error][Kernel::System::SysConfig::SettingGet][Line:201]: Setting SecureMode is invalid!
      [Error][Kernel::System::SysConfig::SettingUpdate][Line:462]: Setting SecureMode does not exist!
      [Error][Kernel::System::SysConfig::DB::DeploymentAdd][Line:4440]: EffectiveValueStrg is invalid!
      [Error][Kernel::System::SysConfig::ConfigurationDeploy][Line:3600]: Could not create the deployment in the DB!
      [Error][Kernel::System::SysConfig::DB::DefaultSettingLock][Line:1689]: Cannot add or update a child row: a foreign key constraint fails (otobo.sysconfig_default, CONSTRAINT FK_sysconfig_default_exclusive_lock_user_id_id FOREIGN KEY (exclusive_lock_user_id) REFERENCES users (id)), SQL: ‚
      [Error][Kernel::System::SysConfig::SettingUpdate][Line:442]: Need TargetUserID or ExclusiveLockGUID!
      [Error][Kernel::System::SysConfig::DB::DefaultSettingIsLockedByUser][Line:1864]: Need ExclusiveLockGUID!
      [Error][Kernel::System::SysConfig::SettingUpdate][Line:488]: Setting SecureMode is not locked to this user!
      [Error][Kernel::Modules::MigrateFromOTRS::_Finish][Line:573]: Can’t activate SecureMode: Setting SecureMode is not locked to this user!

    • #11331
      hilocz
      Participant

      I used OTOBO docker install, it´s little bit black box, but the migration was very quick and without any major problem.

    • #11338
      Best Answer
      Kyle F
      Participant

      I did end up figuring this out:

      1. Copied OTRS mysql database and imported into mysql install on Otobo server
      2. Copied /opt/otrs directory over to Otobo install and set otobo:www-data permissions
      3. Ran through the migration.pl pages again with local options.
Viewing 2 reply threads
  • You must be logged in to reply to this topic.