Gitlab auf Synology 'Website ist nicht erreichbar' nach Installation

[OliK]

Hallo zusammen,

über den Packet Manager habe ich Gitlab auf meiner DS415+ installiert. Die Installation erfolgt ohne Fehlermeldung. Auch MariaDB wird vorher installiert. Wenn ich dann auf das Gitlab Icon klicke und die URL <pfad_zu_meiner_nas>:30000 aufgerufen wird kommt die Meldung "Diese Website ist nicht erreichbar".

Laut Docker laufen die beiden Container synology_gitlab_redis mit CPU 0.05% und 10MB RAM und synology_gitlab mit CPU 2.05% und 556 MB RAM Verbrauch.

Im Container Protokoll für den synology_gitlab sehen alle Einträge okay aus:

21:05:51
Initializing datadir...
stdout
21:05:52
Generating OpenSSH host keys... RSA1 RSA DSA ECDSA ED25519
stdout
21:05:52
Installing configuration templates...
stdout
21:05:53
Configuring gitlab...
stdout
21:05:53
Configuring gitlab::database
stdout
21:05:53
Configuring gitlab::redis
stdout
21:05:54
Configuring gitlab::secrets...
stdout
21:05:54
Configuring gitlab::sidekiq...
stdout
21:05:54
Configuring gitlab::gitlab-workhorse...
stdout
21:05:54
Configuring gitlab::unicorn...
stdout
21:05:54
Configuring gitlab::timezone...
stdout
21:05:54
Configuring gitlab::rack_attack...
stdout
21:05:54
Configuring gitlab::ci...
stdout
21:05:54
Configuring gitlab::artifacts...
stdout
21:05:54
Configuring gitlab::lfs...
stdout
21:05:54
Configuring gitlab:roject_features...
stdout
21:05:54
Configuring gitlab:auth...
stdout
21:05:55
Configuring gitlab::ldap...
stdout
21:05:55
Configuring gitlab::backups...
stdout
21:05:55
Configuring gitlab-shell...
stdout
21:05:55
Configuring nginx...
stdout
21:05:55
Configuring nginx::gitlab...
stdout
21:05:55
Setting up GitLab for firstrun. Please be patient, this could take a while...
stdout
21:06:43
gitlab already exists
stdout
21:06:56
Migrating database...
stdout
21:08:06
Clearing cache...
stdout
21:08:41
2017-03-03 21:08:41,013 CRIT Supervisor running as root (no user in config file)
stdout
21:08:41
2017-03-03 21:08:41,013 WARN Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during parsing
stdout
21:08:41
2017-03-03 21:08:41,013 WARN Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing
stdout
21:08:41
2017-03-03 21:08:41,013 WARN Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing
stdout
21:08:41
2017-03-03 21:08:41,013 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
stdout
21:08:41
2017-03-03 21:08:41,013 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
stdout
21:08:41
2017-03-03 21:08:41,013 WARN Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing
stdout
21:08:41
2017-03-03 21:08:41,013 WARN Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing
stdout
21:08:41
2017-03-03 21:08:41,080 INFO RPC interface 'supervisor' initialized
stdout
21:08:41
2017-03-03 21:08:41,081 CRIT Server 'unix_http_server' running without any HTTP authentication checking
stdout
21:08:41
2017-03-03 21:08:41,081 INFO supervisord started with pid 1
stdout
21:08:42
2017-03-03 21:08:42,084 INFO spawned: 'sidekiq' with pid 469
stdout
21:08:42
2017-03-03 21:08:42,087 INFO spawned: 'unicorn' with pid 470
stdout
21:08:42
2017-03-03 21:08:42,091 INFO spawned: 'gitlab-workhorse' with pid 471
stdout
21:08:42
2017-03-03 21:08:42,094 INFO spawned: 'cron' with pid 472
stdout
21:08:42
2017-03-03 21:08:42,097 INFO spawned: 'nginx' with pid 473
stdout
21:08:42
2017-03-03 21:08:42,100 INFO spawned: 'sshd' with pid 474
stdout
21:08:43
2017-03-03 21:08:43,840 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
stdout
21:08:43
2017-03-03 21:08:43,840 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
stdout
21:08:43
2017-03-03 21:08:43,840 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
stdout
21:08:43
2017-03-03 21:08:43,840 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
stdout
21:08:43
2017-03-03 21:08:43,841 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
stdout
21:08:43
2017-03-03 21:08:43,841 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)


Muss ich vielleicht eine andere URL benutzen?
Hat jemand eine Idee?

Danke im vor raus.

 

[OliK]

Hola,

ich habe die Lösung bzw. das Problem gefunden!! Die URL zum Gitlab <synology_identifier>.synology.me:30000 funktioniert nicht (vielleicht muss man im Router ein Forwarding einrichten, habe ich noch nicht getestet). Aber wenn man die IP Adresse der NAS oder den Netzwerknamen direkt angibt, dann klappt es nach einer kurzen Wartezeit bis im Docker Container alle Prozesse gestartet sind.

Also Problem gelöst.