Content
You are here:
[Solved]Install OP via Docker on Synlogy NAS
Added by Marc Burk over 7 years ago
Hello folks,
i’ve tried to install OP on my NAS Server (Synology DS216+). But this wont work.. I’ve attached the log file.
Database setup seems to work.
-----> Database setup finished. On first installation, the default admin credentials are login: admin, password: admin -----> Launching supervisord... /usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2017-06-07 19:05:07,542 CRIT Supervisor running as root (no user in config file) 2017-06-07 19:05:07,542 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2017-06-07 19:05:07,667 INFO RPC interface 'supervisor' initialized 2017-06-07 19:05:07,667 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2017-06-07 19:05:07,668 INFO supervisord started with pid 1 2017-06-07 19:05:08,672 INFO spawned: 'postgres' with pid 172 2017-06-07 19:05:08,702 INFO spawned: 'apache2' with pid 173 2017-06-07 19:05:08,707 INFO spawned: 'web' with pid 174 2017-06-07 19:05:08,712 INFO spawned: 'worker' with pid 175 2017-06-07 19:05:08,734 INFO spawned: 'postfix' with pid 176 2017-06-07 19:05:08,738 INFO spawned: 'memcached' with pid 177 2017-06-07 19:05:09,742 INFO success: postgres entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-06-07 19:05:09,742 INFO success: apache2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-06-07 19:05:09,742 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-06-07 19:05:09,742 INFO success: worker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-06-07 19:05:09,742 INFO success: postfix entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-06-07 19:05:09,743 INFO success: memcached entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-06-07 19:05:11,893 INFO exited: postfix (exit status 0; expected)
What could be the problem?
Replies (6)
Hi Marc,
strange - I don’t see any errors regarding OpenProject in your logs. Migrations and seeds ran through, and the
raw process output
only contains some warnings.Could you check the syslog for any OOM messages? It might happen that the system kills the master worker if it’s completely out of memory.
Best,
Oliver
Hi Oliver,
problem is solved. I’ve upgraded my NAS to 8GB RAM. Now it works :)
1GB was too less for the System and OP.
Thanks
with kind regards
Marc
Hi, i also installed OP on my synology NAS.It worked but I couldn’t figure how out to get it to open. Can you tell me how I open it? Thanks
Hello Max tim, hello All,
I’m also interested in lauching it, i don’t understand how to do that ?
Also, is it possible to access it outside ? (VPN ?)
I just don’t know what to launch, there seems to be a kind of terminal in the docker image properties
Thank you all,
I'm actually stuck on how to start it up after installing and running it via docker.
How do I run the openproject after installing?
Did anyone find a solution to running openproject after installing on Synology? I get The following error when trying to run it from a browser via port 8080 on the Synology NAS: