Open link in a new tab

Content

Expand project menu

Instance not starting automatically? How to log in?

I tried installing OP on Ubuntu 14.04 with the packaged installation at

The configuration wizard seems to have gone fine, but then what?

The guide says:

After you have completed the configuration wizard, the OpenProject instance will be started automatically. You can log into the instance initially with the user/password combination admin/admin. You will be asked to change this password immediately after the first login.

What is the instance and how can I tell if it is running?
How do I log into it?

I tried the following commands:

~$ sudo service openproject start
openproject: unrecognized service

~$ sudo openproject
Usage:
  openproject run COMMAND [options]
  openproject scale TYPE=NUM
  openproject logs [--tail|-n NUMBER]
  openproject config:get VAR
  openproject config:set VAR=VALUE
  openproject configure
  openproject reconfigure
Message actions

It seems the service was not running and it could be started by typing

$sudo openproject run web

Now it works and I can access it on http://localhost:6000

Message actions

I do the command:sudo openproject run web
After a few seconds it aborts with the following error:bundler: failed to load command: unicorn (/opt/openproject/vendor/bundle/ruby/2.3.0/bin/unicorn)

Any idea what I am doing wrong? This is a clean install on Centos 7

Message actions

have got the same error, on a clean install on SLES 12.

Any help appreciated.

Edit :

I had to install imagemagick package first, then execute the “openproject configure” command again, so that it work.
The installer error I’ve mentionned in another topic (https://community.openproject.com/topics/7676) didn’t warned me that imagemagick had to be installed first.

Message actions

Just a comment for this topic. New install from installers on debian 9, after all was done, apache2 ran but openproject did not auto-start. So, running 'sudo openproject run web' helped a lot, thank you.

To keep it running, probably have to remember systemd is a 180 on how background processes work so set up the appropriate behaviour for running a background process, and ensure 'KillUserProcesses=no' in the /etc/systemd/logind.conf

Then I was able to reboot, login as a sudo user:

> sudo service apache2 start
> sudo openproject run web &
> exit

Then it seems things worked as expected on the default ports, thankfully.

  • I have to add, initially because we prefer init.d, we had removed systemd. Then the openproject install simply did not put an openproject into /etc/init.d/ - despite updating the APP_RUNNER config stuff and reinstalling.
    We reverted to systemd, purged everything, I mean everything, even manuallt rm openproject files, reinstalled and the above proved ok.
  • Alternatively add them all as startup services ;)