Autor Zpráva
Chuchycek
Profil
Ahoj,
zkoušel jsem si udělat webserver apache + gitlab, všechno fungovalo super, ale když jsem chtěl, aby gitlab měl vlastní port :8080,tak mi přestal fungovat. vrací mi to viz obrázek


netstat


Log jen warningy, žádný error

Může mi někdo říct, co je špatně?
TomášK
Profil
Bylo by možné dávat ty logy jako texťáky, ne obrázky? Chybová stránka odpovídá stavu, kdy nefunguje přesměrování z apache na unicorn. Buď tedy unicorn vůbec neběží, nebo ho apache hledá na špatném socketu/adrese. Relevantní informace budou v logu apache a unicornu.
Chuchycek
Profil
Zkusím takto:
Log apache2
[Thu Aug 11 12:34:58.250310 2016] [mpm_event:notice] [pid 12316:tid 139936283158400] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Thu Aug 11 12:34:58.250382 2016] [core:notice] [pid 12316:tid 139936283158400] AH00094: Command line: '/usr/sbin/apache2'
[Thu Aug 11 12:50:10.756756 2016] [mpm_event:notice] [pid 12316:tid 139936283158400] AH00493: SIGUSR1 received.  Doing graceful restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Thu Aug 11 12:50:10.760232 2016] [mpm_event:notice] [pid 12316:tid 139936283158400] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Thu Aug 11 12:50:10.760239 2016] [core:notice] [pid 12316:tid 139936283158400] AH00094: Command line: '/usr/sbin/apache2'
[Thu Aug 11 13:16:17.783550 2016] [mpm_event:notice] [pid 12316:tid 139936283158400] AH00491: caught SIGTERM, shutting down
[Thu Aug 11 13:16:54.958399 2016] [mpm_event:notice] [pid 2662:tid 140047527815040] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Thu Aug 11 13:16:55.010670 2016] [core:notice] [pid 2662:tid 140047527815040] AH00094: Command line: '/usr/sbin/apache2'
[Thu Aug 11 15:08:45.590298 2016] [mpm_event:notice] [pid 2662:tid 140047527815040] AH00491: caught SIGTERM, shutting down
[Thu Aug 11 15:09:28.284450 2016] [mpm_event:notice] [pid 2748:tid 140213956900736] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Thu Aug 11 15:09:28.295445 2016] [core:notice] [pid 2748:tid 140213956900736] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 07:03:21.522591 2016] [mpm_event:notice] [pid 2748:tid 140213956900736] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 07:33:24.894226 2016] [mpm_event:notice] [pid 5901:tid 140152782874496] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 07:33:24.903083 2016] [core:notice] [pid 5901:tid 140152782874496] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 07:34:28.893071 2016] [mpm_event:notice] [pid 5901:tid 140152782874496] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 07:35:29.855876 2016] [mpm_event:notice] [pid 2783:tid 140278963222400] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 07:35:29.953840 2016] [core:notice] [pid 2783:tid 140278963222400] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 08:16:30.907091 2016] [mpm_event:notice] [pid 2783:tid 140278963222400] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 08:16:31.998573 2016] [mpm_event:notice] [pid 7371:tid 139917481822080] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 08:16:31.998599 2016] [core:notice] [pid 7371:tid 139917481822080] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 08:17:20.746756 2016] [mpm_event:notice] [pid 7371:tid 139917481822080] AH00493: SIGUSR1 received.  Doing graceful restart
[Fri Aug 12 08:17:20.753550 2016] [core:error] [pid 7371:tid 139917481822080] (EAI 2)Name or service not known: AH00547: Could not resolve host name *.80 -- ignoring!
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Fri Aug 12 08:17:20.754017 2016] [mpm_event:notice] [pid 7371:tid 139917481822080] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 08:17:20.754024 2016] [core:notice] [pid 7371:tid 139917481822080] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 08:20:43.864213 2016] [mpm_event:notice] [pid 7371:tid 139917481822080] AH00493: SIGUSR1 received.  Doing graceful restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Fri Aug 12 08:20:43.870699 2016] [mpm_event:notice] [pid 7371:tid 139917481822080] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 08:20:43.870707 2016] [core:notice] [pid 7371:tid 139917481822080] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 08:20:52.137592 2016] [mpm_event:notice] [pid 7371:tid 139917481822080] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 08:20:53.212991 2016] [mpm_event:notice] [pid 8061:tid 140681489356672] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 08:20:53.213066 2016] [core:notice] [pid 8061:tid 140681489356672] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 08:28:19.992547 2016] [mpm_event:notice] [pid 8061:tid 140681489356672] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 08:28:21.067079 2016] [mpm_event:notice] [pid 8867:tid 139922062370688] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 08:28:21.067146 2016] [core:notice] [pid 8867:tid 139922062370688] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 08:31:20.732179 2016] [mpm_event:notice] [pid 8867:tid 139922062370688] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 08:31:21.810965 2016] [mpm_event:notice] [pid 9250:tid 140621652662144] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 08:31:21.811034 2016] [core:notice] [pid 9250:tid 140621652662144] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 08:43:14.271419 2016] [mpm_event:notice] [pid 9250:tid 140621652662144] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 08:48:56.006533 2016] [mpm_event:notice] [pid 11130:tid 140284129929088] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 08:48:56.006605 2016] [core:notice] [pid 11130:tid 140284129929088] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 08:53:21.830273 2016] [mpm_event:notice] [pid 11130:tid 140284129929088] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 08:54:16.314886 2016] [mpm_event:notice] [pid 2799:tid 140061943420800] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 08:54:16.338856 2016] [core:notice] [pid 2799:tid 140061943420800] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 08:59:29.899687 2016] [mpm_event:notice] [pid 2799:tid 140061943420800] AH00493: SIGUSR1 received.  Doing graceful restart
[Fri Aug 12 08:59:29.903518 2016] [mpm_event:notice] [pid 2799:tid 140061943420800] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 08:59:29.903531 2016] [core:notice] [pid 2799:tid 140061943420800] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 08:59:35.620284 2016] [mpm_event:notice] [pid 2799:tid 140061943420800] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 08:59:36.690437 2016] [mpm_event:notice] [pid 4018:tid 139999937742720] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 08:59:36.690505 2016] [core:notice] [pid 4018:tid 139999937742720] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 09:05:49.478513 2016] [mpm_event:notice] [pid 4018:tid 139999937742720] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 09:05:50.548694 2016] [mpm_event:notice] [pid 4724:tid 140604709054336] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 09:05:50.548766 2016] [core:notice] [pid 4724:tid 140604709054336] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 09:27:43.385733 2016] [core:warn] [pid 4724:tid 140604709054336] AH00045: child process 4727 still did not exit, sending a SIGTERM
[Fri Aug 12 09:27:43.385780 2016] [core:warn] [pid 4724:tid 140604709054336] AH00045: child process 4728 still did not exit, sending a SIGTERM
[Fri Aug 12 09:27:45.387853 2016] [core:warn] [pid 4724:tid 140604709054336] AH00045: child process 4727 still did not exit, sending a SIGTERM
[Fri Aug 12 09:27:45.388393 2016] [core:warn] [pid 4724:tid 140604709054336] AH00045: child process 4728 still did not exit, sending a SIGTERM
[Fri Aug 12 09:27:47.389559 2016] [core:warn] [pid 4724:tid 140604709054336] AH00045: child process 4727 still did not exit, sending a SIGTERM
[Fri Aug 12 09:27:47.389589 2016] [core:warn] [pid 4724:tid 140604709054336] AH00045: child process 4728 still did not exit, sending a SIGTERM
[Fri Aug 12 09:27:49.391681 2016] [core:error] [pid 4724:tid 140604709054336] AH00046: child process 4727 still did not exit, sending a SIGKILL
[Fri Aug 12 09:27:49.391715 2016] [core:error] [pid 4724:tid 140604709054336] AH00046: child process 4728 still did not exit, sending a SIGKILL
[Fri Aug 12 09:27:50.392811 2016] [mpm_event:notice] [pid 4724:tid 140604709054336] AH00491: caught SIGTERM, shutting down
[Fri Aug 12 09:27:51.139335 2016] [mpm_event:notice] [pid 8734:tid 139689671108480] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Fri Aug 12 09:27:51.139410 2016] [core:notice] [pid 8734:tid 139689671108480] AH00094: Command line: '/usr/sbin/apache2'
[Fri Aug 12 10:33:09.317391 2016] [mpm_event:notice] [pid 8734:tid 139689671108480] AH00491: caught SIGTERM, shutting down

sites-available/gitlab.conf
<VirtualHost *:80>
  ServerName localhost
  ServerSignature Off

  ProxyPreserveHost On

  <Location />
    Order deny,allow
    Allow from all

    ProxyPassReverse http://127.0.0.1:8080
    ProxyPassReverse http://localhost/
  </Location>

  # needed for downloading attachments
  DocumentRoot /opt/gitlab/embedded/service/gitlab-rails/public

</VirtualHost>
TomášK
Profil
Chtělo by to log pro ten konkrétní VirtualHost, přidej ErrorLog. Co je tam za verzi gitlabu? Relativně nedávno se změnilo trasování (dřív apache -> unicorn, nově apache -> gitlab-workhorse -> unicorn). Co se stane, když se připojíš přímo na port 8080? Možná něco řeknou i nástroje, které poskytuje samotný gitlab:
sudo gitlab-ctl status
sudo gitlab-rake gitlab:check
Log unicornu je na /var/log/gitlab/unicorn/unicorn_stderr.log
Chuchycek
Profil
No mám tam poslední verzi, když přidám k ip přesně port 8080, tak mi to vrací ten obrázek viz nahoře. Než jsem začal řešit, ten port, tak mi gitlab normálně fungoval přes apache na 80.

status:
run: gitlab-workhorse: (pid 18078) 7562s; run: log: (pid 2437) 14118s
run: logrotate: (pid 29277) 362s; run: log: (pid 2447) 14118s
run: nginx: (pid 18092) 7562s; run: log: (pid 2440) 14118s
run: postgresql: (pid 18100) 7561s; run: log: (pid 2435) 14118s
run: redis: (pid 18108) 7561s; run: log: (pid 2439) 14118s
run: sidekiq: (pid 18128) 7559s; run: log: (pid 2438) 14118s
run: unicorn: (pid 29779) 15s; run: log: (pid 2436) 14118s

GitLab Shell version >= 3.2.1 ? ... OK (3.2.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... no
  User id for git: 998. Groupd id for git: 998
  Try fixing it:
  sudo chown -R git:git /var/opt/gitlab/git-data/repositories
  For more information see:
  doc/install/installation.md in section "GitLab Shell"
  Please fix the error above and rerun the checks.
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ... can't check, you have no projects
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: FAILED. code: 502
gitlab-shell self-check failed
  Try fixing it:
  Make sure GitLab is running;
  Check the gitlab-shell configuration file:
  sudo -u git -H editor /opt/gitlab/embedded/service/gitlab-shell/config.yml
  Please fix the error above and rerun the checks.

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Reply by email ...

Reply by email is disabled in config/gitlab.yml

Checking Reply by email ... Finished

Checking LDAP ...

LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab ...

Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... skipped (no tmp uploads folder yet)
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
projects have namespace: ... can't check, you have no projects
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.1.8)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.7.4)
Active users: 2

Checking GitLab ... Finished

do logu unicormu mě to nepustít
TomášK
Profil
Na tom výpisu mi přijde divné, že unicorn běží jen 15s, ostatní ~7 500s. Může to být tím, že nenaběhne, ale zkouší to pořád dokola. Taky tam vidím nginx, jak je to vlastně instalované? Gitlab-omnibus předpokládá, že na serveru jiný webserver není a nainstaluje vlastní webserver - nginx. Nevím, co to udělá, pokud už tam jiný server je, čekal bych, že se poperou, ale zdá se, že ti tam běží oba. Pokud apache nepotřebuješ, vyhodil bych ho. Pokud apache chceš, vyhodil bych nginx (mohl byt jít vypnout v konfiguraci gitlabu) a nastavil apache pomocí konfiguráku pro gitlab, viz gitlab.com/gitlab-org/gitlab-recipes/tree/master/web-server/apache. Taky je možné, že gitlab-omnibus podporuje instalaci s apache. Vyvíjí se to celkem rychle, nestíhám to sledovat.
Chuchycek
Profil
TomášK:
status:
root@reporting:/etc/apache2$ sudo gitlab-ctl status
run: gitlab-workhorse: (pid 11425) 1110s; run: log: (pid 2437) 255936s
run: logrotate: (pid 11433) 1109s; run: log: (pid 2447) 255936s
run: postgresql: (pid 11441) 1109s; run: log: (pid 2435) 255936s
run: redis: (pid 11449) 1108s; run: log: (pid 2439) 255936s
run: sidekiq: (pid 11453) 1107s; run: log: (pid 2438) 255936s
run: unicorn: (pid 11458) 1107s; run: log: (pid 2436) 255936s

gitlab check
root@reporting:/etc/apache2$ sudo gitlab-rake gitlab:check
Checking GitLab Shell ...

GitLab Shell version >= 3.2.1 ? ... OK (3.2.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... no
  User id for git: 998. Groupd id for git: 998
  Try fixing it:
  sudo chown -R git:git /var/opt/gitlab/git-data/repositories
  For more information see:
  doc/install/installation.md in section "GitLab Shell"
  Please fix the error above and rerun the checks.
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ... can't check, you have no projects
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Check directories and files:
        /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Reply by email ...

Reply by email is disabled in config/gitlab.yml

Checking Reply by email ... Finished

Checking LDAP ...

LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab ...

Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... skipped (no tmp uploads folder yet)
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
projects have namespace: ... can't check, you have no projects
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.1.8)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.7.4)
Active users: 2

Checking GitLab ... Finished
udělal jsem vše dle návodu a stále to nefunguje, apache mám 2.4
Aktuálně se už nedostanu přes 8080 port na gitlab, apache (80) stále jede bez problémů.
TomášK
Profil
Z toho výpisu to vypadá, že gitlab běží a nefunguje komunikace gitlab <-> apache. Chtělo by to log pro ten konkrétní VirtualHost, přidej ErrorLog.

Taky jsem našel tento návod, četl jsi ho? docs.gitlab.com/omnibus/settings/nginx.html#using-a-non-bundled-web-server

Aktuálně se už nedostanu přes 8080 port na gitlab, apache (80) stále jede bez problémů.
A do vypnutí nginxu na tom portu gitlab fungoval (bez chybové stránky)?
Chuchycek
Profil
TomášK:
dělal jsem to přesně podle návodu.

error.log apache, error log gitlabu je prázdný
[Mon Aug 15 07:29:38.256412 2016] [mpm_event:notice] [pid 8604:tid 139754883155840] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 07:29:38.256487 2016] [core:notice] [pid 8604:tid 139754883155840] AH00094: Command line: '/usr/sbin/apache2'
[Mon Aug 15 07:29:55.928426 2016] [mpm_event:notice] [pid 8604:tid 139754883155840] AH00491: caught SIGTERM, shutting down
[Mon Aug 15 07:29:56.999974 2016] [mpm_event:notice] [pid 8742:tid 140081058064256] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 07:29:57.000039 2016] [core:notice] [pid 8742:tid 140081058064256] AH00094: Command line: '/usr/sbin/apache2'
[Mon Aug 15 07:30:14.950346 2016] [mpm_event:notice] [pid 8742:tid 140081058064256] AH00491: caught SIGTERM, shutting down
[Mon Aug 15 07:30:16.018987 2016] [mpm_event:notice] [pid 8877:tid 140709628090240] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 07:30:16.019055 2016] [core:notice] [pid 8877:tid 140709628090240] AH00094: Command line: '/usr/sbin/apache2'
[Mon Aug 15 07:31:00.300909 2016] [mpm_event:notice] [pid 8877:tid 140709628090240] AH00491: caught SIGTERM, shutting down
[Mon Aug 15 07:31:01.379537 2016] [mpm_event:notice] [pid 9056:tid 139836309342080] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 07:31:01.379600 2016] [core:notice] [pid 9056:tid 139836309342080] AH00094: Command line: '/usr/sbin/apache2'
[Mon Aug 15 07:37:12.935330 2016] [mpm_event:notice] [pid 9056:tid 139836309342080] AH00491: caught SIGTERM, shutting down
[Mon Aug 15 07:37:14.018902 2016] [mpm_event:notice] [pid 10120:tid 139741509326720] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 07:37:14.018975 2016] [core:notice] [pid 10120:tid 139741509326720] AH00094: Command line: '/usr/sbin/apache2'
[Mon Aug 15 07:40:39.787301 2016] [mpm_event:notice] [pid 10120:tid 139741509326720] AH00491: caught SIGTERM, shutting down
[Mon Aug 15 07:40:40.859008 2016] [mpm_event:notice] [pid 10995:tid 140173164771200] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 07:40:40.859071 2016] [core:notice] [pid 10995:tid 140173164771200] AH00094: Command line: '/usr/sbin/apache2'
[Mon Aug 15 07:49:24.809437 2016] [core:warn] [pid 10995:tid 140173164771200] AH00045: child process 10998 still did not exit, sending a SIGTERM
[Mon Aug 15 07:49:24.809473 2016] [core:warn] [pid 10995:tid 140173164771200] AH00045: child process 10999 still did not exit, sending a SIGTERM
[Mon Aug 15 07:49:26.811636 2016] [core:warn] [pid 10995:tid 140173164771200] AH00045: child process 10998 still did not exit, sending a SIGTERM
[Mon Aug 15 07:49:26.811676 2016] [core:warn] [pid 10995:tid 140173164771200] AH00045: child process 10999 still did not exit, sending a SIGTERM
[Mon Aug 15 07:49:28.813843 2016] [core:warn] [pid 10995:tid 140173164771200] AH00045: child process 10998 still did not exit, sending a SIGTERM
[Mon Aug 15 07:49:28.813881 2016] [core:warn] [pid 10995:tid 140173164771200] AH00045: child process 10999 still did not exit, sending a SIGTERM
[Mon Aug 15 07:49:30.816044 2016] [core:error] [pid 10995:tid 140173164771200] AH00046: child process 10998 still did not exit, sending a SIGKILL
[Mon Aug 15 07:49:30.816077 2016] [core:error] [pid 10995:tid 140173164771200] AH00046: child process 10999 still did not exit, sending a SIGKILL
[Mon Aug 15 07:49:31.817266 2016] [mpm_event:notice] [pid 10995:tid 140173164771200] AH00491: caught SIGTERM, shutting down
[Mon Aug 15 07:49:32.569222 2016] [mpm_event:notice] [pid 12224:tid 139668163876736] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 07:49:32.569290 2016] [core:notice] [pid 12224:tid 139668163876736] AH00094: Command line: '/usr/sbin/apache2'
[Mon Aug 15 07:52:09.053541 2016] [mpm_event:notice] [pid 12224:tid 139668163876736] AH00491: caught SIGTERM, shutting down
[Mon Aug 15 07:52:52.344488 2016] [mpm_event:notice] [pid 12673:tid 140239738496896] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 07:52:52.344561 2016] [core:notice] [pid 12673:tid 140239738496896] AH00094: Command line: '/usr/sbin/apache2'
[Mon Aug 15 08:05:17.515590 2016] [mpm_event:notice] [pid 12673:tid 140239738496896] AH00491: caught SIGTERM, shutting down
[Mon Aug 15 08:05:18.615084 2016] [mpm_event:notice] [pid 14104:tid 140424803063680] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 08:05:18.615149 2016] [core:notice] [pid 14104:tid 140424803063680] AH00094: Command line: '/usr/sbin/apache2'
[Mon Aug 15 08:40:46.359233 2016] [mpm_event:notice] [pid 14104:tid 140424803063680] AH00491: caught SIGTERM, shutting down
[Mon Aug 15 08:41:23.732623 2016] [mpm_event:notice] [pid 2778:tid 139698561963904] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 08:41:23.775595 2016] [core:notice] [pid 2778:tid 139698561963904] AH00094: Command line: '/usr/sbin/apache2'
[Mon Aug 15 11:52:05.194678 2016] [mpm_event:notice] [pid 2778:tid 139698561963904] AH00491: caught SIGTERM, shutting down
[Mon Aug 15 11:52:06.271572 2016] [mpm_event:notice] [pid 16351:tid 139893142280064] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Mon Aug 15 11:52:06.271639 2016] [core:notice] [pid 16351:tid 139893142280064] AH00094: Command line: '/usr/sbin/apache2'

do vypnutí nginxu mi to vracelo stále chybovou stránku.
TomášK
Profil
Tohle mi přijde jako log apache, ne toho konkrétního VirtualHostu. Nepamatuju si, jestli VirtualHost ve výchozím nastavením loguje do tohoto souboru nebo ne. Každopádně je potřeba nastavit error log a zvýšit úroveň logování natolik, aby pro požadavek v access logu, který skončí chybou (502), vzniknul i zápis do error logu.
Chuchycek
Profil
TomášK:
Ano, to je apache, jak jsem psal a ten log gitlabu je prázdný.

Logování mám zavedené:

ErrorLog /var/log/apache2/gitlab_error.log
CustomLog /var/log/apache2/gitlab_forwarded.log common_forwarded
CustomLog /var/log/apache2/gitlab_access.log combined env=!dontlog
CustomLog /var/log/apache2/gitlab.log combined
TomášK
Profil
Aha, špatně jsem pochopil, že jde o některý z logů služeb gitlabu. Tak zvyš loglevel, dokud nezačne apache něco vypisovat.LogLevel debug. Vrací-li ErrorDocument, mělo by ho jít přesvědčit, ať to zapíše do logu.
Chuchycek
Profil
Přidal jsem LogLevel debug, ale stále se nic nepropisuje
TomášK
Profil
Níž jsou ještě log levely trace1 - trace8. Už trace2 (LogLevel trace2) by měl zapsat pokus o navázání spojení s proxy, i když nic neselže. Pokud nic nezapíše, řekl bych, že to neloguje vůbec. Pokud se nepletu, do /var/log/apache2/gitlab.log by při současné nastavení měl zapsat každý přístup na apache. Je v tom souboru něco? Pokud ne, tak buď na apache ten požadavek nedojde nebo ho zpracuje jiný VirtualHost nebo apache nedokáže logovat.
Chuchycek
Profil
Tak je to přesně jak píšete, do logu se nic neukládá ani po povýšení na trace2, takže problém je tedy někde na straně virtualhostu jestli to dobře chápu.., jak tedy mám zjistit, co je špatně?
TomášK
Profil
Je potřeba rozchodit aspoň statickou Hello world! stránku, zkontrolovat, že se načte a že zapisuje do logů (do access.log, s dostatečně velkým trace i do error.log). Až bude fungovat, tak přidat nastavení proxy (třeba na nějaký nesmyslný port) a zkontrolovat, že to pořád loguje. Až to bude fungovat, tak spustit nějaký mini-webserver (třeba docs.python.org/2/library/simplehttpserver.html) a zkontrolovat, že proxy přes apache funguje. Pak to nasměrovat na GitLab a buď to půjde nebo v logu bude chyba.
Chuchycek
Profil
Tak to celé byla moje chyba.. Postup fungoval, ale jelikož v síti nemám dostupné doménové jméno, tak jsem to dělal celou dobu blbě, stačilo mi v apachi nastavit další port a již funguje.

Ale ještě mám takový technický dotaz, jak lze změnit adresu
gitlab.example:8181/root/test.git
na
172.168.0.1:8888/root/test.git

Vaše odpověď


Prosím používejte diakritiku a interpunkci.

Ochrana proti spamu. Napište prosím číslo dvě-sta čtyřicet-sedm: