Home PC Games Linux Windows Database Network Programming Server Mobile  
           
  Home \ Linux \ Installation GitLab appears ruby_block supervise_redis_sleep action run     - Ubuntu Locale configuration problem solving Can not set LC_CTYPE (Linux)

- Ubuntu 14.04 Nvidia proprietary drivers for install two graphic cards (Linux)

- Sublime Text 3 shortcuts summary (Linux)

- Linux System Tutorial: Ubuntu on the desktop is disabled by default keyring to unlock tips (Linux)

- Linux install Maven and SVN client (Linux)

- MySQL in order by inaccurate results in problems and solutions (Database)

- Incremental garbage collection mechanism for Ruby 2.2 (Programming)

- MySQL use benchmarking tool sysbench (Database)

- PHP file upload methods exist in the database (Programming)

- Use FirewallD build dynamic firewall (Linux)

- How to configure MariaDB replication in CentOS Linux (Database)

- CentOS7 install MySQL 5.5 (Database)

- Docker container plaintext password problem-solving way (Server)

- Linux remote wake the computer original code [C] (Linux)

- Smooth upgrade to OpenSSH 6.7 Procedure (Linux)

- MongoDB Installation under CentOS 6.6 (Database)

- Ubuntu Tutorial: E: Failed to get lock / var / lib / apt / lists / lock - open (Linux)

- Bad name two variables (Linux)

- DOM event handlers add notes (Programming)

- Switching Virtual Machine + Ubuntu graphical interface and terminal interface (Linux)

 
         
  Installation GitLab appears ruby_block supervise_redis_sleep action run
     
  Add Date : 2018-11-21      
         
         
         
  To install GitLab reference to official website provides installation is very simple. However, when performing GitLab-ctl reconfigure may occur
ruby_block [supervise_redis_sleep] action run
Which stop, do not move the situation. What Causes Which?
My GitLab is CentOS7 virtual machine kvm will not be the problem of the virtual machine? Investigation for a long time not.
Finally, with reference to the official website to provide a method of execution:
Performed manually exec / opt / GitLab / embedded / bin / runsvdir-start
Then execute GitLab-ctl start
Installation back to normal, GitLab also provide normal service.


But this problem is simply too disgusting. You must manually start the server is restarted, and if this one can not connect to the server GitLab can not provide the service.
Look at the problems identified and ruby is a relationship.
Dead horse a living horse medicine, see if it is the source of the problem which gem to install.
gem sources -r https://rubygems.org/
gem sources -a http://ruby.taobao.org/
Then perform
GitLab-ctl reconfigure

Where the card is no longer. The reason turned out to be another installation source to solve the problem.
     
         
         
         
  More:      
 
- Android using shape drawable material production (Programming)
- Hadoop 2.0 Detailed Configuration Tutorial (Server)
- rsync server set up (Server)
- RedHat virtual machine to install VMware Tools (Linux)
- Install OpenGL development environment in Fedora and Ubuntu (Linux)
- How ONLYOFFICE collaborative editing document on Linux (Linux)
- Installation Strongswan: on a Linux IPsec-based VPN tool (Linux)
- CentOS terminal display Chinese (Linux)
- Spring Boot + Nginx + Tomcat + SSL configuration notes (Server)
- How to understand Python yield keyword (Programming)
- Shell Scripting Basics (Linux)
- Batch kill processes using awk command (Linux)
- OpenJDK7 source compiler installation on CentOS 6.5 (Linux)
- Using Lua implement various operations list (Programming)
- Single-node Hadoop environment to build (Server)
- Ubuntu 15.10 / 14.04 install subtitling software Aegisub (Linux)
- PostgreSQL 9.3.5 database installation under Ubuntu Server 14.04 (Database)
- Windows 8.1 and Ubuntu 14.04 dual system uninstall Ubuntu Tutorial (Linux)
- CentOS yum install LNMP PHP5.4 version (Server)
- Linux environmental performance data acquisition system (Linux)
     
           
     
  CopyRight 2002-2020 newfreesoft.com, All Rights Reserved.