frame

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

problem installation about gitlab

Hello,

I'm trying to install GITLAB on Debian 8 but blocking in exporting

The repository is setup! You can now install packages.
[email protected]:~# sudo EXTERNAL_URL="http://gitlab.caygri.eu" apt-get install gitlab-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  gitlab-ce
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 394 MB of archives.
After this operation, 1188 MB of additional disk space will be used.
Get:1 https://packages.gitlab.com/gitlab/gitlab-ce/debian/ jessie/main gitlab-ce amd64 10.3.5-ce.0 [394 MB]
Fetched 394 MB in 26s (14.9 MB/s)
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> line 1.)
debconf: falling back to frontend: Readline
Selecting previously unselected package gitlab-ce.
(Reading database ... 93688 files and directories currently installed.)
Preparing to unpack .../gitlab-ce_10.3.5-ce.0_amd64.deb ...
Unpacking gitlab-ce (10.3.5-ce.0) ...

​​​​​​​Can someone help me?

Comments

  • after 15 minutes show this 

    @
        +# This file is managed by gitlab-ctl. Manual changes will be
        +# erased! To change the contents below, edit /etc/gitlab/gitlab.rb
        +# and run `sudo gitlab-ctl reconfigure`.
        +
         # PostgreSQL Client Authentication Configuration File
         # ===================================================
         #
        -# Refer to the "Client Authentication" section in the PostgreSQL
        -# documentation for a complete description of this file.  A short
        -# synopsis follows.
        +# Refer to the "Client Authentication" section in the
        +# PostgreSQL documentation for a complete description
        +# of this file.  A short synopsis follows.
         #
         # This file controls: which hosts are allowed to connect, how clients
         # are authenticated, which PostgreSQL user names they can use, which
         # databases they can access.  Records take one of these forms:
         #
        -# local      DATABASE  USER  METHOD  [OPTIONS]
        -# host       DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
        -# hostssl    DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
        -# hostnossl  DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
        +# local      DATABASE  USER  METHOD  [OPTION]
        +# host       DATABASE  USER  CIDR-ADDRESS  METHOD  [OPTION]
        +# hostssl    DATABASE  USER  CIDR-ADDRESS  METHOD  [OPTION]
        +# hostnossl  DATABASE  USER  CIDR-ADDRESS  METHOD  [OPTION]
         #
         # (The uppercase items must be replaced by actual values.)
         #
        -# The first field is the connection type: "local" is a Unix-domain
        -# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
        -# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
        -# plain TCP/IP socket.
        +# The first field is the connection type: "local" is a Unix-domain socket,
        +# "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an
        +# SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.
         #
        -# DATABASE can be "all", "sameuser", "samerole", "replication", a
        -# database name, or a comma-separated list thereof. The "all"
        -# keyword does not match "replication". Access to replication
        -# must be enabled in a separate record (see example below).
        +# DATABASE can be "all", "sameuser", "samerole", a database name, or
        +# a comma-separated list thereof.
         #
        -# USER can be "all", a user name, a group name prefixed with "+", or a
        -# comma-separated list thereof.  In both the DATABASE and USER fields
        -# you can also write a file name prefixed with "@ to include names
        -# from a separate file.
        +# USER can be all", a user name, a group name prefixed with "+", or
        +# a comma-separated list thereof.  In both the DATABASE and USER fields
        +# you can also write a file name prefixed with "@
        +psql_user='gitlab-psql'
        +psql_host='/var/opt/gitlab/postgresql'
        +psql_port='5432'
        - change owner from '' to 'root'
        - change group from '' to 'root'
      * postgresql_user[gitlab] action create
        * execute[create gitlab postgresql user] action run (skipped due to not_if)
         (up to date)
      * execute[create gitlabhq_production database] action run (skipped due to not_if)
      * postgresql_user[gitlab_replicator] action create
        * execute[create gitlab_replicator postgresql user] action run (skipped due to not_if)
        * execute[set options for gitlab_replicator postgresql user] action run (skipped due to not_if)
         (up to date)
      * execute[enable pg_trgm extension] action run (skipped due to not_if)
      * execute[reload postgresql] action nothing (skipped due to action :nothing)
      * execute[start postgresql] action nothing (skipped due to action :nothing)
    Recipe: gitlab::database_migrations
      * bash[migrate gitlab-rails database] action run
        [execute] rake aborted!
                  PG::ConnectionBad: could not connect to server: No such file or directory
                    Is the server running locally and accepting
                    connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"?
                  /opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:49:in `block (3 levels) in <top (required)>'
                  /opt/gitlab/embedded/bin/bundle:23:in `load'
                  /opt/gitlab/embedded/bin/bundle:23:in `<main>'
                  Tasks: TOP => gitlab:db:configure
                  (See full trace by running task with --trace)
    
        ================================================================================
        Error executing action `run` on resource 'bash[migrate gitlab-rails database]'
        ================================================================================
    
        Mixlib::ShellOut::ShellCommandFailed
        ------------------------------------
        Expected process to exit with [0], but received '1'
        ---- Begin output of "bash"  "/tmp/chef-script20180122-10405-i5q3kq" ----
        STDOUT: rake aborted!
        PG::ConnectionBad: could not connect to server: No such file or directory
            Is the server running locally and accepting
            connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"?
        /opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:49:in `block (3 levels) in <top (required)>'
        /opt/gitlab/embedded/bin/bundle:23:in `load'
        /opt/gitlab/embedded/bin/bundle:23:in `<main>'
        Tasks: TOP => gitlab:db:configure
        (See full trace by running task with --trace)
        STDERR:
        ---- End output of "bash"  "/tmp/chef-script20180122-10405-i5q3kq" ----
        Ran "bash"  "/tmp/chef-script20180122-10405-i5q3kq" returned 1
    
        Resource Declaration:
        ---------------------
        # In /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/database_migrations.rb
    
         51: bash "migrate gitlab-rails database" do
         52:   code <<-EOH
         53:     set -e
         54:     log_file="#{node['gitlab']['gitlab-rails']['log_directory']}/gitlab-rails-db-migrate-$(date +%Y-%m-%d-%H-%M-%S).log"
         55:     umask 077
         56:     /opt/gitlab/bin/gitlab-rake gitlab:db:configure 2>& 1 | tee ${log_file}
         57:     STATUS=${PIPESTATUS[0]}
         58:     echo $STATUS > #{db_migrate_status_file}
         59:     exit $STATUS
         60:   EOH
         61:   environment env_variables unless env_variables.empty?
         62:   notifies :run, "execute[clear the gitlab-rails cache]", :immediately
         63:   dependent_services.each do |svc|
         64:     notifies :restart, svc, :immediately
         65:   end
         66:   not_if "(test -f #{db_migrate_status_file}) && (cat #{db_migrate_status_file} | grep -Fx 0)"
         67:   only_if { node['gitlab']['gitlab-rails']['auto_migrate'] }
         68: end
    
        Compiled Resource:
        ------------------
        # Declared in /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/database_migrations.rb:51:in `from_file'
    
        bash("migrate gitlab-rails database") do
          action [:run]
          retries 0
          retry_delay 2
          default_guard_interpreter :default
          command "migrate gitlab-rails database"
          backup 5
          returns 0
          code "    set -e\n    log_file=\"/var/log/gitlab/gitlab-rails/gitlab-rails-db-migrate-$(date +%Y-%m-%d-%H-%M-%S).log\"\n    umask 077\n    /opt/gitlab/bin/gitlab-rake gitlab:db:configure 2>& 1 | tee ${log_file}\n    STATUS=${PIPESTATUS[0]}\n    echo $STATUS > /var/opt/gitlab/gitlab-rails/upgrade-status/db-migrate-873248b1f0d3a7a5535771a3a1635803-7c30d48\n    exit $STATUS\n"
          interpreter "bash"
          declared_type :bash
          cookbook_name "gitlab"
          recipe_name "database_migrations"
          not_if "(test -f /var/opt/gitlab/gitlab-rails/upgrade-status/db-migrate-873248b1f0d3a7a5535771a3a1635803-7c30d48) && (cat /var/opt/gitlab/gitlab-rails/upgrade-status/db-migrate-873248b1f0d3a7a5535771a3a1635803-7c30d48 | grep -Fx 0)"
          only_if { #code block }
        end
    
        Platform:
        ---------
        x86_64-linux
    
    Recipe: gitlab::gitlab-rails
      * execute[clear the gitlab-rails cache] action run
        - execute /opt/gitlab/bin/gitlab-rake cache:clear
    Recipe: gitlab::redis
      * ruby_block[reload redis svlogd configuration] action create
        - execute the ruby block reload redis svlogd configuration
    Recipe: gitlab::postgresql
      * ruby_block[reload postgresql svlogd configuration] action create
        - execute the ruby block reload postgresql svlogd configuration
    
    Running handlers:
    There was an error running gitlab-ctl reconfigure:
    
    bash[migrate gitlab-rails database] (gitlab::database_migrations line 51) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
    ---- Begin output of "bash"  "/tmp/chef-script20180122-10405-i5q3kq" ----
    STDOUT: rake aborted!
    PG::ConnectionBad: could not connect to server: No such file or directory
            Is the server running locally and accepting
            connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"?
    /opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:49:in `block (3 levels) in <top (required)>'
    /opt/gitlab/embedded/bin/bundle:23:in `load'
    /opt/gitlab/embedded/bin/bundle:23:in `<main>'
    Tasks: TOP => gitlab:db:configure
    (See full trace by running task with --trace)
    STDERR:
    ---- End output of "bash"  "/tmp/chef-script20180122-10405-i5q3kq" ----
    Ran "bash"  "/tmp/chef-script20180122-10405-i5q3kq" returned 1
    
    Running handlers complete
    Chef Client failed. 163 resources updated in 01 minutes 16 seconds
    dpkg: error processing package gitlab-ce (--configure):
     subprocess installed post-installation script returned error exit status 1
    Errors were encountered while processing:
     gitlab-ce
    E: Sub-process /usr/bin/dpkg returned an error code (1)
  • Hey,

    we have tried the official installation tutorial and it worked like a charm:

    https://about.gitlab.com/installation/#debian

    We would recommend you recreating the server if possible fresh and try the above instruction. As it seems some other changes were done on your server that may cause the issue.

Sign In or Register to comment.

Learn how to install a web and database server, email, FTP client or other applications. Discover and share information on server security or optimization recommendations.
Feel free to join our constantly expanding community, participate in discussions, strengthen your knowledge on Linux and Windows server management!
© 2013 - 2019 Time4VPS. All rights reserved.

Get In Touch