New project error 500 on Raspberry Pi 2

Hi,

I've installed a Gitlab using the following instructions: https://about.gitlab.com/2015/04/21/gitlab-on-raspberry-pi-2/

With the following package: https://downloads-packages.s3.amazonaws.com/raspberry-pi/gitlab-ce_7.12.0~omnibus%2B20150622131235-1_armhf.deb

When I try to create a new project, from the Gitlab Web interface, I recive the following error:

500
Whoops, something went wrong on our end.
Try refreshing the page, or going back and attempting the action again.
Please contact your GitLab administrator if this problem persists.

I only have changed the following parameter on /etc/gitlab/gitlab.rb: git_data_dir "/home/pi/gitlab/git-data"

A 32GB Usb memory stick is mounted under this directory and format as ext4.

Thanks for your help.

I can confirm the same problem with not edited gitlab.rb config file (all parammeters by default).

Added ~15383 label

Can you include any error messages found in /var/log/gitlab/gitlab-rails/production.log?

production.log

This is the full log file. Thanks!

I wonder if you need to install nodejs. Try:

sudo apt-get install nodejs-legacy

@marin, do you know the latest Raspberry Pi 2 package needs nodejs? Another user is running into this:

https://github.com/gitlabhq/gitlabhq/issues/9408

If so, perhaps the .deb should contain a dependency for it?

@stanhu All packages are built with nodejs, this includes the Rpi2 packages.

The error messages are:

ActionView::Template::Error ():
  (execjs):1
  execjs (2.5.2) lib/execjs/external_runtime.rb:214:in `exec_runtime'
  execjs (2.5.2) lib/execjs/external_runtime.rb:39:in `exec'
  execjs (2.5.2) lib/execjs/external_runtime.rb:14:in `initialize'
  execjs (2.5.2) lib/execjs/runtime.rb:44:in `new'
  execjs (2.5.2) lib/execjs/runtime.rb:44:in `compile'
  execjs (2.5.2) lib/execjs/module.rb:27:in `compile'
  coffee-script (2.4.1) lib/coffee_script.rb:50:in `context'
  coffee-script (2.4.1) lib/coffee_script.rb:78:in `compile'
  tilt (1.4.1) lib/tilt/coffee.rb:46:in `evaluate'
  tilt (1.4.1) lib/tilt/template.rb:103:in `render'
  (eval):5:in `render_with_options'
  haml (4.0.5) lib/haml/filters.rb:184:in `block in compile'
  haml (4.0.5) lib/haml/filters.rb:162:in `instance_eval'
  haml (4.0.5) lib/haml/filters.rb:162:in `compile'
  haml (4.0.5) lib/haml/filters.rb:141:in `internal_compile'
  haml (4.0.5) lib/haml/compiler.rb:273:in `compile_filter'

It looks to me like ExecJS is having difficulty executing a runtime. Is nodejs supposed to be in a Gemfile? I extracted the Raspberry Pi .deb and did not find any traces of it:

$ find . -name Gemfile | xargs grep nodejs

Any ideas?

The execjs module should look for nodejs or node in PATH variable - see details here.

So maybe the PATH variable is not properly set for the GitLab user at runtime.

But I'm trying to reproduce this error on my Raspberry PI 2 in the next days :)

When I understand the Debian package site for nodejs-legacy correctly, that package just adds a symlink to /usr/bin/node - so after installing it there should be:

• /usr/bin/node and
• /usr/bin/nodejs

I have installed the "nodejs-legacy" package as @stanhu recommend to me. Now It looks that Gitlab is working correctly... at least I can create new projects ;) I'll check the new Gitlab installation deeply on my Raspberry Pi 2 tomorrow. You can close this ticket if you want. Thanks all for your help!

@stefan-it Thanks for the information! That is quite useful.

@jgm1986 Glad this workaround fixed the issue. It looks like node is available in /opt/gitlab/embedded/bin, but perhaps PATH isn't set up right to use it. Sounds like an issue should be filed under omnibus-gitlab, so I'll close this one for now.

Status changed to closed

Issue in omnibus-gitlab is in https://gitlab.com/gitlab-org/omnibus-gitlab/issues/635 so any help and debugging can go in there.

mentioned in issue #1859 (closed)

Can someone try this omnibus-gitlab package?

mentioned in merge request !14785