July 27, 20169 yr Post some logs. ==> /var/log/gitlab/sidekiq/current <== 2016-07-27_09:34:43.31811 2016-07-27T09:34:43.317Z 215 TID-1ze3w INFO: Cron Jobs - add job with name: stuck_ci_builds_worker 2016-07-27_09:34:43.32651 2016-07-27T09:34:43.326Z 215 TID-1ze3w INFO: Cron Jobs - add job with name: expire_build_artifacts_worker 2016-07-27_09:34:43.33989 2016-07-27T09:34:43.339Z 215 TID-1ze3w INFO: Cron Jobs - add job with name: repository_check_worker 2016-07-27_09:34:43.35012 2016-07-27T09:34:43.349Z 215 TID-1ze3w INFO: Cron Jobs - add job with name: admin_email_worker 2016-07-27_09:34:43.35752 2016-07-27T09:34:43.357Z 215 TID-1ze3w INFO: Cron Jobs - add job with name: repository_archive_cache_worker 2016-07-27_09:34:43.36504 2016-07-27T09:34:43.364Z 215 TID-1ze3w INFO: Cron Jobs - add job with name: gitlab_remove_project_export_worker ==> /var/log/gitlab/unicorn/unicorn_stderr.log <== I, [2016-07-27T09:34:56.989736 #255] INFO -- : listening on addr=127.0.0.1:8080 fd=15 I, [2016-07-27T09:34:56.991987 #255] INFO -- : unlinking existing socket=/var/opt/gitlab/gitlab-rails/sockets/gitlab.socket I, [2016-07-27T09:34:56.993435 #255] INFO -- : listening on addr=/var/opt/gitlab/gitlab-rails/sockets/gitlab.socket fd=16 I, [2016-07-27T09:34:57.039510 #269] INFO -- : worker=0 spawned pid=269 I, [2016-07-27T09:34:57.041104 #269] INFO -- : worker=0 ready I, [2016-07-27T09:34:57.045386 #272] INFO -- : worker=1 spawned pid=272 I, [2016-07-27T09:34:57.051558 #272] INFO -- : worker=1 ready I, [2016-07-27T09:34:57.087399 #255] INFO -- : master process ready I, [2016-07-27T09:34:57.102540 #275] INFO -- : worker=2 spawned pid=275 I, [2016-07-27T09:34:57.103259 #275] INFO -- : worker=2 ready ==> /var/log/gitlab/sidekiq/current <== 2016-07-27_09:34:57.58774 2016-07-27T09:34:57.587Z 215 TID-1ze3w INFO: Running in ruby 2.1.8p440 (2015-12-16 revision 53160) [x86_64-linux] 2016-07-27_09:34:57.58784 2016-07-27T09:34:57.587Z 215 TID-1ze3w INFO: See LICENSE and the LGPL-3.0 for licensing details. 2016-07-27_09:34:57.58848 2016-07-27T09:34:57.587Z 215 TID-1ze3w INFO: Upgrade to Sidekiq Pro for more features and support: http://sidekiq.org 2016-07-27_09:34:57.59041 2016-07-27T09:34:57.590Z 215 TID-1ze3w INFO: Starting processing, hit Ctrl-C to stop ==> /var/log/gitlab/unicorn/current <== 2016-07-27_09:34:58.16233 adopted new unicorn master 255 ==> /var/log/gitlab/gitlab-rails/production.log <== Started GET "/" for 10.0.0.191 at 2016-07-27 09:35:19 +0000 Processing by RootController#index as HTML Completed 401 Unauthorized in 45ms (ActiveRecord: 5.5ms) ==> /var/log/gitlab/gitlab-workhorse/current <== 2016-07-27_09:35:20.30715 nas:81 @ - - [2016-07-27 09:35:19.841154109 +0000 UTC] "GET / HTTP/1.1" 302 93 "" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36" 0.465872 /snip Password tokens removed Note when changing the external url whilst appending a new port number nginx listens on the new port number so please update your port mapping root@nas:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 695b06bc1388 gitlab/gitlab-ce "/assets/wrapper" 4 minutes ago Up 4 minutes 0.0.0.0:81->81/tcp, 80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:2222->22/tcp GitLab-CE I've also noticed the 1:1 mapping on port 80 this is clearly wrong you should not be exposing this ... Anyway this is working but I have bigger fish to fry ... will come back to this container later. ps Please link me to the Dockerfile so I can fix
July 27, 20169 yr Just had a look at your template. You should change the 80 port to something else as 80 is the default for unraid. Also change the ssh port as it's also the default unraid ssh port. You can still use those ports inside the container, but on the host side it should default to something else in the template.
July 27, 20169 yr Just had a look at your template. You should change the 80 port to something else as 80 is the default for unraid. Also change the ssh port as it's also the default unraid ssh port. You can still use those ports inside the container, but on the host side it should default to something else in the template. ^^^ This Bingo
July 27, 20169 yr Author Just had a look at your template. You should change the 80 port to something else as 80 is the default for unraid. Also change the ssh port as it's also the default unraid ssh port. You can still use those ports inside the container, but on the host side it should default to something else in the template. ^^^ This Bingo How is it working out for you? Are the url redirects also replaced with some random chars?
July 27, 20169 yr How is it working out for you? Are the url redirects also replaced with some random chars? Are you being serious ? They are not random characters it's the hostname of the container and as such you're being redirected to the hostname of the container which is the correct behaviour due to the default gitlab conf. 2 solutions -- 1 - As above modify gitlab.rb 2 - Set a static container hostname
July 27, 20169 yr Author How is it working out for you? Are the url redirects also replaced with some random chars? Are you being serious ? They are not random characters it's the hostname of the container and as such you're being redirected to the hostname of the container which is the correct behaviour due to the default gitlab conf. 2 solutions -- 1 - As above modify gitlab.rb 2 - Set a static container hostname I didn't realise. I didn't have to change anything in the previous versions of this docker. It started when they pushed an update a couple of days ago.
July 27, 20169 yr I didn't realise. I didn't have to change anything in the previous versions of this docker. It started when they pushed an update a couple of days ago. Oh ic so this app is simply pointing to https://hub.docker.com/r/gitlab/gitlab-ce/~/dockerfile/ '>https://hub.docker.com/r/gitlab/gitlab-ce/~/dockerfile/ - well there's a new release that you could try https://packages.gitlab.com/gitlab/gitlab-ce https://gitlab.com/gitlab-org/gitlab-ce/tags ps Not sure how it had ever worked for you to be honest ! Do you have logs ? If you need to revert the gitlab version create your own version of https://hub.docker.com/r/gitlab/gitlab-ce/~/dockerfile/
August 3, 20169 yr Hello. I want to use the gitlab docker, but cannot get it started. It will start up and try to configure but shuts down a few minutes later. The log looks like this: [0m ================================================================================[0m [31mError executing action `run` on resource 'execute[/opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8]'[0m ================================================================================[0m [0mMixlib::ShellOut::ShellCommandFailed[0m ------------------------------------[0m Expected process to exit with [0], but received '1' [0m---- Begin output of /opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8 ---- [0mSTDOUT: The files belonging to this database system will be owned by user "gitlab-psql". [0mThis user must also own the server process. [0m [0mThe database cluster will be initialized with locale "C.UTF-8". [0mThe default text search configuration will be set to "english". [0m [0mfixing permissions on existing directory /var/opt/gitlab/postgresql/data ... ok [0mcreating subdirectories ... ok [0mselecting default max_connections ... 100 [0mselecting default shared_buffers ... 32MB [0mcreating configuration files ... ok [0mcreating template1 database in /var/opt/gitlab/postgresql/data/base/1 ... [0mSTDERR: FATAL: could not open file "pg_xlog/000000010000000000000001" (log file 0, segment 1): No such file or directory [0mchild process exited with exit code 1 [0minitdb: removing contents of data directory "/var/opt/gitlab/postgresql/data" [0m---- End output of /opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8 ---- [0mRan /opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8 returned 1[0m [0mResource Declaration:[0m ---------------------[0m # In /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/postgresql.rb [0m [0m 84: execute "/opt/gitlab/embedded/bin/initdb -D #{postgresql_data_dir} -E UTF8" do [0m 85: user postgresql_user [0m 86: not_if { File.exists?(File.join(postgresql_data_dir, "PG_VERSION")) } [0m 87: end [0m 88: [0m [0mCompiled Resource:[0m ------------------[0m # Declared in /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/postgresql.rb:84:in `from_file' [0m [0mexecute("/opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8") do [0m action [:run] [0m retries 0 [0m retry_delay 2 [0m default_guard_interpreter :execute [0m command "/opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8" [0m backup 5 [0m returns 0 [0m user "gitlab-psql" [0m declared_type :execute [0m cookbook_name "gitlab" [0m recipe_name "postgresql" [0m not_if { #code block } [0mend [0m [0mPlatform:[0m ---------[0m x86_64-linux[0m [0m I assume there is something in the gitlab.rb file I need to change, but I do not even know where to begin. Thanks in advance for any help with this.
August 3, 20169 yr Author Hello. I want to use the gitlab docker, but cannot get it started. It will start up and try to configure but shuts down a few minutes later. The log looks like this: [0m ================================================================================[0m [31mError executing action `run` on resource 'execute[/opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8]'[0m ================================================================================[0m [0mMixlib::ShellOut::ShellCommandFailed[0m ------------------------------------[0m Expected process to exit with [0], but received '1' [0m---- Begin output of /opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8 ---- [0mSTDOUT: The files belonging to this database system will be owned by user "gitlab-psql". [0mThis user must also own the server process. [0m [0mThe database cluster will be initialized with locale "C.UTF-8". [0mThe default text search configuration will be set to "english". [0m [0mfixing permissions on existing directory /var/opt/gitlab/postgresql/data ... ok [0mcreating subdirectories ... ok [0mselecting default max_connections ... 100 [0mselecting default shared_buffers ... 32MB [0mcreating configuration files ... ok [0mcreating template1 database in /var/opt/gitlab/postgresql/data/base/1 ... [0mSTDERR: FATAL: could not open file "pg_xlog/000000010000000000000001" (log file 0, segment 1): No such file or directory [0mchild process exited with exit code 1 [0minitdb: removing contents of data directory "/var/opt/gitlab/postgresql/data" [0m---- End output of /opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8 ---- [0mRan /opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8 returned 1[0m [0mResource Declaration:[0m ---------------------[0m # In /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/postgresql.rb [0m [0m 84: execute "/opt/gitlab/embedded/bin/initdb -D #{postgresql_data_dir} -E UTF8" do [0m 85: user postgresql_user [0m 86: not_if { File.exists?(File.join(postgresql_data_dir, "PG_VERSION")) } [0m 87: end [0m 88: [0m [0mCompiled Resource:[0m ------------------[0m # Declared in /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/postgresql.rb:84:in `from_file' [0m [0mexecute("/opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8") do [0m action [:run] [0m retries 0 [0m retry_delay 2 [0m default_guard_interpreter :execute [0m command "/opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8" [0m backup 5 [0m returns 0 [0m user "gitlab-psql" [0m declared_type :execute [0m cookbook_name "gitlab" [0m recipe_name "postgresql" [0m not_if { #code block } [0mend [0m [0mPlatform:[0m ---------[0m x86_64-linux[0m [0m I assume there is something in the gitlab.rb file I need to change, but I do not even know where to begin. Thanks in advance for any help with this. Can you post a screenshot of how the docker is setup? I have made some modifications to the unRAID template so that it should startup withouth any needs to configure the gitlab.rb file.
August 3, 20169 yr Can you post a screenshot of how the docker is setup? I have made some modifications to the unRAID template so that it should startup withouth any needs to configure the gitlab.rb file. Good stuff.... I was going to point out the env settings from http://docs.gitlab.com/omnibus/docker/ Thanks
August 3, 20169 yr https://www.dropbox.com/s/j9mqlkej4doc1dj/gitlab%20config.png?dl=0 There you are, sir. I assume this is what you want.
August 4, 20169 yr Author https://www.dropbox.com/s/j9mqlkej4doc1dj/gitlab%20config.png?dl=0 There you are, sir. I assume this is what you want. You are using the old template where the port mappins are using already reserved ports by unraid. E.g. port 80. (I made a mistake in the initial template) Can you try to delete the docker container, the template and the mounted volume folders? This is how you delete the template: unRAID Menu --> Docker --> Add Container --> Choose my-Gitlab-CE --> Click on the red cross in the top. After this is done, try to reinstall it and it should be running on port: 9080
August 5, 20169 yr Author I reinstalled with the new template, but still got the same error as before. /mnt/user/appdata - is that a cache drive in your case? If it is indeed a cache drive, you need to use /mnt/cache/appdata instead.
August 5, 20169 yr I do not currently have a cache drive in my system. Then set it to /mnt/disk1/appdata (or whatever disk you want it to be on). Gitlab's appdata currently uses some features that are not available on a user share, but will work on a disk share
November 8, 20169 yr Author Anyone had any luck running it with apache reverse proxy? I'm running it behind nginx. Works fine, so i guess it should work with Apache as well.
November 14, 20169 yr I had installed, configured, and migrated all of my data to GitLab to get off of bitbucket and github. I had to restart my unraid box after installing an unraid update and everything was gone in gitlab. It started up and asked me to configure my password like it was a new install. After I set the password and got in the account had been reset to defualt and all of the data was gone. I do have access to copies of the repos since they are checked out. My concern is what did I do wrong that would have caused this? Any thoughts?
November 14, 20169 yr Author I had installed, configured, and migrated all of my data to GitLab to get off of bitbucket and github. I had to restart my unraid box after installing an unraid update and everything was gone in gitlab. It started up and asked me to configure my password like it was a new install. After I set the password and got in the account had been reset to defualt and all of the data was gone. I do have access to copies of the repos since they are checked out. My concern is what did I do wrong that would have caused this? Any thoughts? Where is your Application Data Storage Path mounted? Could it be some docker issue upgrades with unRAID?
November 14, 20169 yr I had installed, configured, and migrated all of my data to GitLab to get off of bitbucket and github. I had to restart my unraid box after installing an unraid update and everything was gone in gitlab. It started up and asked me to configure my password like it was a new install. After I set the password and got in the account had been reset to defualt and all of the data was gone. I do have access to copies of the repos since they are checked out. My concern is what did I do wrong that would have caused this? Any thoughts? Where is your Application Data Storage Path mounted? Could it be some docker issue upgrades with unRAID? As far as I know it is set to the default I did not change it. "/mnt/cache/appdata/gitlab-ce/data"
November 14, 20169 yr Author I had installed, configured, and migrated all of my data to GitLab to get off of bitbucket and github. I had to restart my unraid box after installing an unraid update and everything was gone in gitlab. It started up and asked me to configure my password like it was a new install. After I set the password and got in the account had been reset to defualt and all of the data was gone. I do have access to copies of the repos since they are checked out. My concern is what did I do wrong that would have caused this? Any thoughts? Where is your Application Data Storage Path mounted? Could it be some docker issue upgrades with unRAID? Did you have any other docker applications with issues? Which versions were you upgrading between? As far as I know it is set to the default I did not change it. "/mnt/cache/appdata/gitlab-ce/data"
December 28, 20169 yr All images uploaded into gitlab, like profile or a project image are trying to load from the internal url, not external: http://unraid:9080/uploads/user/avatar/2/avatar.png http://unraid:9080/uploads/project/avatar/1/RL_1308x1066.png That url should not be pointing to unraid. Is there a setting or something I need to change that will affect all urls? Even when looking at the SSH of my git project, it uses unraid. UPDATE: I fixed this by editing the external_url in the gitlab.rb file by SSH into the docker and editing that file manually: https://docs.gitlab.com/omnibus/settings/configuration.html#configuring-the-external-url-for-gitlab Is there any way to control this as a docker setting instead?
December 28, 20169 yr All images uploaded into gitlab, like profile or a project image are trying to load from the internal url, not external: http://unraid:9080/uploads/user/avatar/2/avatar.png http://unraid:9080/uploads/project/avatar/1/RL_1308x1066.png That url should not be pointing to unraid. Is there a setting or something I need to change that will affect all urls? Even when looking at the SSH of my git project, it uses unraid. Its a variable you need to add. Add a new variable as below. Key: GITLAB_OMNIBUS_CONFIG Value: external_url 'http://IP:PORT/'; gitlab_rails['lfs_enabled'] = true; Replace IP:PORT with your own. For ssh, I think there is a setting in some file. I'll try to find out what I did.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.