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.
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.)
Hello, I just finished doing a migration of a system with about 65000 tickets and I get the exact same issue. Everything seems to be there but not permissions are applied.
I migrated from latest OTRS 6 to OTOBO 10.1 latest. I fixed all invalid configs and stuff early during first migration attempt.
Should I migrate to OTOBO 10.0 and the to OTOBO 10.1? Is it ok to migrate directly to 10.1?
In fact I did follow the instructions several times until I got a successfull migration message, but it had what I described.
Afterwards I decided to go back and install 10.0 first and did the migration to that version firs, it indeed went a little bit smooth, but at the end, even though I can see all the roles, the data, the menus, still don’t have the groups, so what you said makes sense, I will redo the process again hopefully this afternoon and find out where the error is.
I can look into the database and all is there, the groups, the roles, the queues, the role_groups table, but it just can’t be seen in the interface.
I’ll let you guys know if I identify where the issue is.
In regards of what Stephan mentioned we reviewed the list of tables and found that in fact the groups_table existed and had all the new groups, but the ones coming from otrs where not inserted into this one, instead, the groups table from otrs was kept.
So we moved all the contents from groups into groups_table and it seems to be ok now.
Question? Should there be something into the migration script that merges those tables instead of keeping the old one?
Our website uses cookies. Cookies are tiny text files which are saved in your web browser or by your web browser on your device when you access websites. They contain a characteristic character sequence allowing to clearly identify your browser upon your next visit to the website.
You can prevent the setting of cookies at any time by making the appropriate setting in your internet browser. Cookies that have already been set can be deleted manually or automatically at any time. This is possible in all common internet browsers. If the setting of cookies is deactivated in the browser, not all functions of the website may be fully usable.
We deliberately use very little cookies.
Detailed information can be found in section 4 of our Privacy Policy.
Necessary cookies
Essential Cookies are necessary to deliver this website and some of its features correctly.
For this reason, we do not provide any opportunity here to disable them.
Notwithstanding this, you can deactivate all Cookies in your Browser Settings at any time. Please be aware, however, that this might have an impact on the functionality of this website.
More information about the cookies to be set and how long they will be stored can be found in section 4 of our Privacy Poliy: Privacy Policy.
Google Analytics' Cookies
When you visit this website, Google Analytics sets cookies on your system. This will help us analyse how you use our website ans tailor it to the needs of our visitors. Your IP address will be automatically anonymised (IP anonymisation and deactivation of your User ID). Therefore, we cannot trace which data a certain user is accessing. The data are not saved together with any other personal user data.
You can deactivate tracking in your browser if you do not want us to be able to track your visit on our website.
Privacy Policy
Detailed information on the usage of cookies as well as our Privacy Policy can be found here: