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. Support
  3. Updates failing (v7.3.6)

Updates failing (v7.3.6)

Scheduled Pinned Locked Moved Solved Support
updates
7 Posts 2 Posters 866 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.
    • robiR Offline
      robiR Offline
      robi
      wrote on last edited by girish
      #1

      I have a server that had some backup issues, which are not resolved, however Cloudron updates kept failing.

      There is no show log button in the UI/#/settings view, so that would be a nice feature request.. while the update is running show a log button as well as if it errors.

      Another issue was try to look at the log from the log viewer UI, by replacing the taskid=xxxxx number, but it just shows a blank page for some reason.

      Finally finding the log by getting on the console of the server showed an odd error that the cloudron-updater service was still running. Checking the services it said it was from a month+ ago!

      Stopping the service manually allowed the update process to continue past the error, but now it's been stuck for 10+m.

      2023-06-02T02:09:23.404Z box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds

      Meanwhile box logs show checking for autoupdate but it's locked due to box_update.

      Conscious tech

      girishG 1 Reply Last reply
      0
      • robiR robi

        I have a server that had some backup issues, which are not resolved, however Cloudron updates kept failing.

        There is no show log button in the UI/#/settings view, so that would be a nice feature request.. while the update is running show a log button as well as if it errors.

        Another issue was try to look at the log from the log viewer UI, by replacing the taskid=xxxxx number, but it just shows a blank page for some reason.

        Finally finding the log by getting on the console of the server showed an odd error that the cloudron-updater service was still running. Checking the services it said it was from a month+ ago!

        Stopping the service manually allowed the update process to continue past the error, but now it's been stuck for 10+m.

        2023-06-02T02:09:23.404Z box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds

        Meanwhile box logs show checking for autoupdate but it's locked due to box_update.

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

        @robi update logs in UI were just added for next release (7.5) - https://git.cloudron.io/cloudron/box/-/commit/db1fa84936ab08df093f43e0f581d70bfee60eb7

        Can you check what's going on in journalctl -u cloudron-updater ? Most likely some apt issue.

        1 Reply Last reply
        1
        • girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #3

          (Following up from support@)

          Seems like IPv6 connectivity issue.

          2023-06-02T02:06:54 ==> installer: Could not pull cloudron/base:4.0.0@sha256:31b195ed0662bdb06a6e8a5ddbedb6f191ce92e8bee04c03fb02dd4e9d0286df
          Error response from daemon: Get "https://registry.ipv6.docker.com/v2/": dial tcp [2600:1f18:2148:bc01:c4:4967:28eb:1824]:443: connect: network is unreachable
          
          1 Reply Last reply
          1
          • girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #4

            Indeed:

            # curl -6 https://ipv6.api.cloudron.io/api/v1/helper/public_ip
            curl: (7) Couldn't connect to server
            

            Something is up with the network. Very slow...

            # wget https://releases.cloudron.io/box-354eff93b7-354eff93b7-7.4.1.tar.gz
            --2023-06-02 08:13:52--  https://releases.cloudron.io/box-354eff93b7-354eff93b7-7.4.1.tar.gz
            Resolving releases.cloudron.io (releases.cloudron.io)... 165.227.67.76, 2604:a880:800:10::b66:f001
            Connecting to releases.cloudron.io (releases.cloudron.io)|165.227.67.76|:443... connected.
            HTTP request sent, awaiting response... 200 OK
            Length: 34594778 (33M) [application/octet-stream]
            Saving to: ‘box-354eff93b7-354eff93b7-7.4.1.tar.gz’
            
            box-354eff93b7-354eff93b7-7.4.1.ta  25%[===============>                                                 ]   8.48M   319KB/s    eta 4m 18s 
            

            In my server, it takes 1.5 sec for the above download. So far, it's taking 8mins in yours...

            1 Reply Last reply
            1
            • girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #5

              OK, was network related.

              1 Reply Last reply
              1
              • girishG girish marked this topic as a question on
              • girishG girish has marked this topic as solved on
              • robiR Offline
                robiR Offline
                robi
                wrote on last edited by
                #6

                Can you make other logs referenced in log files clickable? That would simplify troubleshooting from the UI bigtime!

                Conscious tech

                1 Reply Last reply
                0
                • girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #7

                  @robi instead of clickable, the logs are unified now into a single stream (similar to app logs).

                  1 Reply Last reply
                  1
                  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