[DRE-maint] Bug#894272: More info about the error

David López Zajara (Er_Maqui) er_maqui at darkbolt.net
Mon Apr 2 15:36:11 BST 2018


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

> You will need to start gitaly manually. We are trying to do that
automatically, but facing some issues currently.

How can I start gitaly? I0ve installed gitaly package (it isn't installed
yet). Now I have this packages:

kanade:/home# dpkg -l | grep gitaly
ii  gitaly
0.91.0+debian-1                      amd64        Git RPC service for
handling all the git calls made by GitLab
ii  ruby-gitaly
0.89.0+dfsg-1                        all          Auto-generated gRPC
client for gitaly

But none of these packages included any service to start it. Gitaly package
includes a binary on /usr/bin but not configuration file "config.toml".
Also, I didn't have any service for gitaly.

- From init.d gitlab start script, I found this start line:

$app_root/bin/daemon_with_pidfile $gitaly_pid_path $gitaly_dir/gitaly
$gitaly_dir/config.toml >> $gitaly_log 2>&1 &

I understand I can run this line for starting service:
/usr/share/gitlab/bin/daemon_with_pidfile
/usr/share/gitlab/tmp/pids/gitaly.pid /usr/bin/gitaly
$gitaly_dir/config.toml >> /usr/share/gitlab/log/gitaly.log 2>&1 &

(I've redplaced $gitaly_dir on binary path because I didn't have also any
other binary for the package).
But, I need the config file for starting it.

Checking on original issue (https://gitlab.com/gitlab-org/gitaly/issues/1119),
/etc/gitaly folder does not exist on my system too.
I think there's a dependency problem on gitlab (It not requires gitaly
package installation). Also, another problem on gitaly package (config
folder is not created).


Also, about the other error, I've do some tests:
    - From Details view, I can read any file. But, if the file are
README.md (the file loaded on details view on the lower part of the page) I
got a 503 error. If I reload, I got a 500 error.
    - On Details view, the file README.md is not load at any moment.
    - On commits list, the error "An error occurred while loading commits"
only appears if at least one commit have a GPG signature. On repositories
without any signed commit, error message does not appear.
    - Two factor authentication does not work. I have a user with 2FA
enabled from 8.13 version, and when try to login, I got this error on
production.log:

Started POST "/users/sign_in" for x.x.x.x at 2018-04-02 12:52:53 +0200
Processing by SessionsController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]",
"user"=>{"remember_me"=>"0", "otp_attempt"=>"[FILTERED]"}}
Completed 500 Internal Server Error in 15ms (ActiveRecord: 0.5ms)

OpenSSL::Cipher::CipherError (bad decrypt):
  app/controllers/sessions_controller.rb:141:in `valid_otp_attempt?'
  app/controllers/concerns/authenticates_with_two_factor.rb:54:in
`authenticate_with_two_factor_via_otp'
  app/controllers/concerns/authenticates_with_two_factor.rb:43:in
`authenticate_with_two_factor'
  lib/gitlab/middleware/multipart.rb:95:in `call'
  lib/gitlab/request_profiler/middleware.rb:14:in `call'
  lib/gitlab/middleware/go.rb:17:in `call'
  lib/gitlab/etag_caching/middleware.rb:11:in `call'
  lib/gitlab/middleware/read_only/controller.rb:28:in `call'
  lib/gitlab/middleware/read_only.rb:16:in `call'
  lib/gitlab/request_context.rb:18:in `call'
  lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'
  lib/gitlab/middleware/release_env.rb:10:in `call'

(As a workaround, I've disabled 2FA for this user with admin account)

Another error (I don't know if this is am error):
- -With an admin account:

On Groups, on "Your Groups", I can see groups who I aren't a member. Also,
on "Explore public groups" I can see all groups on the server (even if the
groups are private).
On Projects -> Explore procjects -> all, I can see all projects, even
personal projects from users, and without permission on these projects.

If I remember correctly, on 8.13 version, even with an admin account, I
can't see this.
NOTE: I report this as a informative report. I'm not afraid about this (at
least at this moment), but maybe this is a problem for some people. If this
is a default behavior of gitlab 10, maybe is a good moment for suggest at
least a configuration parameter for it.


Thanks for all your help on these issues.

https://maqui.darkbolt.net/
Linux registered user ~#363219
PGP keys avaiables at KeyServ. ID: 0x4233E9F2
Los hombres somos esclavos de la historia
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEYf0F71OtDykDsKZdCU2zE9sy6H8FAlrCOmUACgkQCU2zE9sy
6H80AhAAmZ9icDofLrDSel9yZQRFCopLBs7Z3Oxg094toEncMBf3l+8Jrsj9RBpK
K0c7Y9osswH+XU5RrkTCpZk01LkwmsfouRsKW7EhJ/ArgEl6iw3+k6OsXnFZs+i0
fts/Y+z9iETbLvMpfv8Raln+JEMu5307OmtU4gUW10aVnX/dRiOMpm8rMslrGfdq
AUl4CKLtql8W8YH0uyIA7NJ6zgJLEXR6euXh4E3QFZdlZw0xLVn8Qxu5Pq2BF5U5
tlFkqpO2D6B46JIpoCwsIfK/zULT8++56DRzR/zBKNq6uKhsx79Q41Ee5ZmI4/5W
jIbk7lEZYTWqrAcvqUUhGwE+si2Y6NgaS4Kz9/M/uHUouDnjZP/hr5hrg0ZWuPHo
5r1rWibDvfDHMawh8C46TslfsUKGBWr++U0KZiFQ1VGNiXi7/bc00r4RLHCzjnkw
qlQqz3NFXLqPp4VFt9BNc7VSvSGZNSLeT4Qu183zXLnpm+mzYUuMhgiU82eDnD/0
HXsYMF21i+nM4PVYBMQ2rvUtUPrORGVCsMZQJXN/JgCakx+RKmYR3GMK+h7VKYnW
BboJXzHGVTAINPbC/+mRC6w0gTjavC3gWXUp+7tG1J4lR7AHJRnckEDmBWNO5mbS
b1Z1+vffvEMDAq7VaCJ5eHkvaJc2F1ZsQ1redufhXvpQ4JyQI40=
=s56R
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20180402/f5290a6d/attachment.html>


More information about the Pkg-ruby-extras-maintainers mailing list