Schlagwörter: Docker volumes installation
-
AutorBeiträge
-
-
11. September 2024 um 14:26 Uhr - Views: 196 #32019
Hi,
I’m having trouble installing OTOBO 10.1 using docker on my freshly installed Rocky linux 9 server.
I did everything according to the instructions https://doc.otobo.org/manual/installation/10.1/en/content/installation-docker.html (I did not configure HTTPS) all my containers are healthy:
> docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bb641e39e11b rotheross/otobo:latest-10_1 "/opt/otobo_install/…" 45 seconds ago Up 43 seconds (healthy) otobo-daemon-1
7a4d10d7636a rotheross/otobo:latest-10_1 "/opt/otobo_install/…" 45 seconds ago Up 44 seconds (healthy) 0.0.0.0:80->5000/tcp otobo-web-1
e8ea09eb7fc5 redis:6.0-alpine "docker-entrypoint.s…" 47 seconds ago Up 44 seconds (healthy) 6379/tcp otobo-redis-1
417ce3c8e08f mariadb:10.5 "docker-entrypoint.s…" 47 seconds ago Up 44 seconds (healthy) 3306/tcp otobo-db-1
7e3cbdb865e0 rotheross/otobo-elasticsearch:latest-10_1 "/bin/tini -- /usr/l…" 47 seconds ago Up 44 seconds (healthy) 9200/tcp, 9300/tcp otobo-elastic-1
but when I go to http://otobo-test/otobo/installer.pl I get the error „Internal Server Error“ :((
This is the log of the web container:
[root@otobo-test otobo-docker]# docker logs --tail 50 --follow --timestamps 7a4d10d7636a
2024-09-11T09:53:22.652115876Z Kernel::System::Loader could not be loaded: at /opt/otobo/bin/psgi-bin/../../Kernel/System/ObjectManager.pm line 294.
2024-09-11T10:01:25.515358246Z Kernel::System::Loader could not be loaded: at /opt/otobo/bin/psgi-bin/../../Kernel/System/ObjectManager.pm line 294.
2024-09-11T10:08:23.920054164Z Kernel::System::Loader could not be loaded: at /opt/otobo/bin/psgi-bin/../../Kernel/System/ObjectManager.pm line 294.
2024-09-11T10:08:24.655826745Z Kernel::System::Loader could not be loaded: at /opt/otobo/bin/psgi-bin/../../Kernel/System/ObjectManager.pm line 294.
2024-09-11T10:08:25.006150758Z Kernel::System::Loader could not be loaded: at /opt/otobo/bin/psgi-bin/../../Kernel/System/ObjectManager.pm line 294.
2024-09-11T10:08:25.500830854Z Kernel::System::Loader could not be loaded: at /opt/otobo/bin/psgi-bin/../../Kernel/System/ObjectManager.pm line 294.
2024-09-11T10:08:25.606939386Z Kernel::System::Loader could not be loaded: at /opt/otobo/bin/psgi-bin/../../Kernel/System/ObjectManager.pm line 294.
2024-09-11T10:08:26.386330048Z Kernel::System::Loader could not be loaded: at /opt/otobo/bin/psgi-bin/../../Kernel/System/ObjectManager.pm line 294.
What is different from the manual is that I am using the latest versions of docker, docker-compose and GIT and that could be a problem.
And there are a lot of problems with installing versions from the manual on Rocky Linux 9 because they are much older versions.
Can anyone help? What to do?
-
Dieses Thema wurde geändert vor 7 Monaten, 1 Woche von
AnteIde Marić.
-
Dieses Thema wurde geändert vor 7 Monaten, 1 Woche von
-
11. September 2024 um 18:16 Uhr #32021
Hello Anteide,
strange, this does not sound familiar to me. I just tried it on my Ubuntu 22.04 box. There I get the expected response when fetching otobo/installer.pl . This should also work with Rocky Linux as the Docker host.
First, which versions of Docker and Docker compose are you using?
Secondly, the line number 294 of the message looks suspicious. In OTOBO 10.1.10 the line number should be around 273, https://github.com/RotherOSS/otobo/blob/c075367a404e514be1cd9a0ac9cd6ea998e0df5b/Kernel/System/ObjectManager.pm#L273 . The line number fits much better to OTOBO 11.0.5, https://github.com/RotherOSS/otobo/blob/cdb825b2a8ec505c437f2c400ae0b72bd2397ed2/Kernel/System/ObjectManager.pm#L290 .
Therefore I think that there is some mixup with a previous installation of OTOBO 11.1.x. My approach would be to inspect the volume with
docker volume inspect otobo_opt_otobo
. Take a look at Kernel/System/ObjectManager.pm and of RELEASE in that volume. If you are absolutely sure that you don’t need any data from that volume you can remove it and try starting anew. -
12. September 2024 um 10:28 Uhr #32024
Somehow, OTOBO 11 left on the server. After cleaning everything, now everything works as it should. Thank you very much for the answer!
-
-
AutorBeiträge
- Das Thema „ Migration from OTRS 6 community edition to OTOBO 10.1“ ist für neue Antworten geschlossen.