Your message dated Thu, 19 Jan 2017 12:55:35 +0100
with message-id <1827335.InSDzF7FHs@libor-nb>
and subject line Re: gitlab: git operations over web causes 502 error
has caused the Debian Bug report #851570,
regarding gitlab: git operations over web causes 502 error
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
851570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851570
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gitlab
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
we have problem with git operations over web interface, all leads to error 502.
I have just upgraded two instances of gitlab to 8.13.6+dfsg2-2, our from 8.10.x
, customers from 8.9.x.
Before update, git operations did not work either
I don't know, how to debug, production.log doesn't contain any error.
We have gitlab on apache not on nginx on both instantions
Any clue?
Libor
-----BEGIN PGP SIGNATURE-----
iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlh8uWcVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOaJAP/2jcw4A04X2gERyFNKRKxkUbfOni
KJlt9wHMwIlJzv2Jmcf9fbHUEMUe4Ug4DT3AG0e6hMoPThK9AuUIdUrDff1W1GZh
8xr52TRcKq3izcv+n9ou8djuvtL5L3UoDIXFN+e7z14kDb09eypnEwmagr+siKPh
+/ohXuVvszW4nY1DMWd2cBXxIhMOP20tKykqls6zqX6MpFTGqrpsve4h3JbRXdYs
ksn6Vs4JfLu7uuQBSA8hjX3ZLsCJhYx1/A78/imWT/1X+JDy1bT97oJ9YqIgV5dQ
1zqvEdFVnnLHczCvMBSu00Tgwv0A5yBzD60PPAqDv5dUB+kLJEsaeEt3Xq3dAYrv
NwKEPdz0vDIgpuKXBlL5xyFfII7OkB0E8udd1GMDt3ik4be7eB3pJkR0Dt9XENNH
/hhhVJxnOwxyMc8AX4ombpPgNBpwYwxJ+021WQLnbwhxJbyRssIbuegSNfNPDygw
jz/OMH9pk0E2F9TQ2vQEBRSDodjyaEXdfib0RGZFXmRj/V4E9JsxForllSY05pV7
9FIZCMoRiV6v9gsSiJiLOuv2tQuZGkV6wsy19t5LDDxXPgj/cIiDDEX79mIa98m4
0YiReNGSP3EI2wZP7dU9h+kjzKM9Y18JRVX1sm6/Y6BuksISULWoFY5mlw1OiP3r
RzcWMq8NcR1+9u6O
=SDwH
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hi,
closing this, it was our configuration problem, it seems, that only one
unicorn worker cannot handle this
Libor
--- End Message ---
