xvonabur

Hello! Could anyone help me? Gitlab from this repo doesn't start or at least I doesn't see GUI (Chrome says ERR_CONNECTION_REFUSED). Giltlab log: debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (This frontend requires a controlling tty.) debconf: falling back to frontend: Teletype Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... Creating SSH2 ECDSA key; this may take some time ... Creating SSH2 ED25519 key; this may take some time ... invoke-rc.d: policy-rc.d denied execution of restart. SSL keys and certificates were not found. Assuming that the container is running behind a HTTPS enabled load balancer. Waiting for database server to accept connections Setting up GitLab for firstrun. Please be patient, this could take a while... gitlabhq_production already exists Migrating database... Compiling assets. Please be patient, this could take a while... Starting supervisord... 2015-06-29 08:25:57,247 CRIT Supervisor running as root (no user in config file) 2015-06-29 08:25:57,247 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing 2015-06-29 08:25:57,247 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing 2015-06-29 08:25:57,247 WARN Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing 2015-06-29 08:25:57,247 WARN Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing 2015-06-29 08:25:57,247 WARN Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing 2015-06-29 08:25:57,266 INFO RPC interface 'supervisor' initialized 2015-06-29 08:25:57,266 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2015-06-29 08:25:57,267 INFO supervisord started with pid 1 2015-06-29 08:25:58,271 INFO spawned: 'sidekiq' with pid 576 2015-06-29 08:25:58,273 INFO spawned: 'unicorn' with pid 577 2015-06-29 08:25:58,275 INFO spawned: 'cron' with pid 578 2015-06-29 08:25:58,278 INFO spawned: 'nginx' with pid 579 2015-06-29 08:25:58,280 INFO spawned: 'sshd' with pid 580 2015-06-29 08:25:59,788 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-06-29 08:25:59,788 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-06-29 08:25:59,789 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-06-29 08:25:59,789 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-06-29 08:25:59,789 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) I also installed Postgres and Redis from the repo. All configs are default. Postgres log: Initializing database... Creating user "gitlab"... Creating database "gitlabhq_production"... Granting access to database "gitlabhq_production" for user "gitlab"... Starting PostgreSQL server... 2015-06-29 15:24:28 UTC [1-1] LOG: could not create IPv6 socket: Address family not supported by protocol 2015-06-29 15:24:28 UTC [72-1] LOG: database system was shut down at 2015-06-29 15:24:28 UTC 2015-06-29 15:24:28 UTC [72-2] LOG: MultiXact member wraparound protections are now enabled 2015-06-29 15:24:28 UTC [1-2] LOG: database system is ready to accept connections 2015-06-29 15:24:28 UTC [76-1] LOG: autovacuum launcher started 2015-06-29 15:25:12 UTC [81-1] gitlab@postgres ERROR: database "gitlabhq_production" already exists 2015-06-29 15:25:12 UTC [81-2] gitlab@postgres STATEMENT: CREATE DATABASE "gitlabhq_production" ENCODING = 'unicode' Redis log: [1] 29 Jun 08:24:45.696 # Server started, Redis version 2.8.4 [1] 29 Jun 08:24:45.697 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. [1] 29 Jun 08:24:45.697 * The server is now ready to accept connections on port 6379 [1] 29 Jun 08:24:45.697 * The server is now ready to accept connections at /var/run/redis/redis.sock [1] 29 Jun 08:29:46.057 * 10 changes in 300 seconds. Saving... [1] 29 Jun 08:29:46.063 * Background saving started by pid 13 [13] 29 Jun 08:29:46.079 * DB saved on disk [13] 29 Jun 08:29:46.079 * RDB: 4 MB of memory used by copy-on-write [1] 29 Jun 08:29:46.163 * Background saving terminated with success P.S. I'm using the latest Unraid 6.0.1 and 4Gb of RAM.

Hello, everyone! I have the same problem with cache_dirs on beta5 of unraid v6. It seems modifying ulimit back to 15360 doesn't help a lot. 'Cannot allocate memory' displays after free memory of dom0 is low (about 25-30 Mb). But I don't know who is actually eating so much memory. P.S. Btw, my dom0_memory is 2048M. Updated: Just commented out the ulimit string and limit the depth of scan by using "-d" flag. Now everything works fine.