5. November 2020 at 17:29 - Views: 688 #9625
I have installed OTOBO using MySQL, and I am trying to migrate from OTRS 6, which is installed using Postgresql. I have followed all of the migration instructions. When I get to the point of checking the database, the migration program complains of network issues. There are no network issues that I am aware of. Postgresql is communicating on port 5432 normally. This is preventing me from continuing the migration process. What do I do?
9. November 2020 at 11:45 #9757Stefan RotherKeymaster
The migration itself should actually be quite simple, but there are various pitfalls in the environment and configuration.
Did you do the migration as described in the documentation https://doc.otobo.org/manual/installation/stable/en/content/migration-from-otrs-6.html?
If so, can you please post more information about your setup, procedures and log messages?
In the next step we can then take a closer look at the problems.
I wish you a nice day,
- This reply was modified 3 years ago by Stefan Rother.
9. November 2020 at 20:22 #9920
I made a mistake, and did not install the postgresql perl module. Once the perl module was installed migration is proceeding, if slowly. Thank you for your reply.
9. November 2020 at 18:08 #9891besParticipant
Hello Arbitrary String,
There are two common problems that can occur. First access to PostgreSQL can be denied from the new server. You can check this by calling something like
psql -U otrs –host=<postgres_server> otrs
on the server where Apache is running. Another cause can be that the Perl database driver DBD::Pg is not installed. You can check this with
perldoc -l DBD::Pg.
When testing I found that the diagnostics of the database check should be improved. I have added this to the upcoming release OTOBO 10.0.6, see https://github.com/RotherOSS/otobo/issues/627 .
If this problem still occurs, could you send me the relevant excerpt from the Apache logfile ?
9. November 2020 at 20:23 #9921
I did not have the postgresql perl module installed! The system did not make any attempt to tell me that however, just the generic „network issues“ message.
10. November 2020 at 9:10 #9922Sven OesterlingKeymaster
That’s the case, if an ajax request of the client browser does not receive an answer from the server (in this case, because the server ran into an error, and not because of network loss). One could try to catch errors like this, and send more meaningful error messages. On the other hand, in this case the user has to be working on the server anyways, so there is always the possibility to just consult the log files… (One has to know, though…)
12. November 2020 at 19:01 #10010
- You must be logged in to reply to this topic.