Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. GitLab
  3. GitLab Upgrade Error

GitLab Upgrade Error

Scheduled Pinned Locked Moved Solved GitLab
3 Posts 2 Posters 740 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    DualOSWinWiz
    wrote on last edited by girish
    #1

    Git Lab Update Issues

    Hi Cloudron Team getting error while upgrading the Gitlab from GitLab 16.6.4 to latest version.

    i restarted the system even checked all the services but its not updating below is the summary of errors. i even restarted the ubuntu server 22.04.

    Database Migration Issues: The error PG::FeatureNotSupported: ERROR: DROP INDEX CONCURRENTLY must be first action in transaction suggests that there's a problem with the way a database migration is being executed. In PostgreSQL, the DROP INDEX CONCURRENTLY command must be run outside of a transaction block because it cannot be executed inside a multi-statement transaction. To resolve this, ensure that the migration script is correctly set up to execute this command outside of any transaction blocks.

    File Permission Issues: The error /home/git is not writable indicates a file permission issue. The user under which the GitLab process is running does not have write access to the /home/git directory. You need to check and update the permissions of this directory to make sure that the GitLab process has the necessary access.

    Repeated Health Check Errors: The Healtheck error: Error: connect ECONNREFUSED 172.18.18.240:80 suggests that GitLab is trying to connect to a service (possibly a web service or database) at 172.18.18.240 on port 80, but the connection is being refused. This could be due to the service not running, the service not listening on the expected port, network issues, or firewall rules blocking the connection.

    URI Gem Warnings: The warnings about constants in the URI module being already initialized suggest that there might be conflicting versions of the URI gem, or the gem is being required multiple times in a way that causes these warnings. This might not be critical, but it's worth checking your gem dependencies and require statements to ensure there's no conflict or unnecessary duplication.

    girishG 1 Reply Last reply
    1
    • D DualOSWinWiz

      Git Lab Update Issues

      Hi Cloudron Team getting error while upgrading the Gitlab from GitLab 16.6.4 to latest version.

      i restarted the system even checked all the services but its not updating below is the summary of errors. i even restarted the ubuntu server 22.04.

      Database Migration Issues: The error PG::FeatureNotSupported: ERROR: DROP INDEX CONCURRENTLY must be first action in transaction suggests that there's a problem with the way a database migration is being executed. In PostgreSQL, the DROP INDEX CONCURRENTLY command must be run outside of a transaction block because it cannot be executed inside a multi-statement transaction. To resolve this, ensure that the migration script is correctly set up to execute this command outside of any transaction blocks.

      File Permission Issues: The error /home/git is not writable indicates a file permission issue. The user under which the GitLab process is running does not have write access to the /home/git directory. You need to check and update the permissions of this directory to make sure that the GitLab process has the necessary access.

      Repeated Health Check Errors: The Healtheck error: Error: connect ECONNREFUSED 172.18.18.240:80 suggests that GitLab is trying to connect to a service (possibly a web service or database) at 172.18.18.240 on port 80, but the connection is being refused. This could be due to the service not running, the service not listening on the expected port, network issues, or firewall rules blocking the connection.

      URI Gem Warnings: The warnings about constants in the URI module being already initialized suggest that there might be conflicting versions of the URI gem, or the gem is being required multiple times in a way that causes these warnings. This might not be critical, but it's worth checking your gem dependencies and require statements to ensure there's no conflict or unnecessary duplication.

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      @DualOSWinWiz please upgrade to 7.6.4 (Settings -> Check For update -> Upgrade). It's listed as unstable but safe to update.

      1 Reply Last reply
      1
      • girishG girish moved this topic from Support on
      • D Offline
        D Offline
        DualOSWinWiz
        wrote on last edited by
        #3

        Yes after upgrading it solved

        1 Reply Last reply
        0
        • nebulonN nebulon marked this topic as a question on
        • nebulonN nebulon has marked this topic as solved on
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Bookmarks
        • Search