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. Redash
  3. Has anyone used v10.1.0?

Has anyone used v10.1.0?

Scheduled Pinned Locked Moved Solved Redash
22 Posts 5 Posters 4.1k Views 5 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.
  • portfield-slashP portfield-slash

    @girish
    After uninstalling with Cloudron's GUI, I also installed with GUI.
    I have Cloudron installed on AWS EC2. Do I need to rebuild EC2?

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

    @portfield-slash no need to rebuild EC2/server. Are you able to reproduce this on our test server - https://my.demo.cloudron.io (username: cloudron password: cloudron) ?

    ChristopherMagC 1 Reply Last reply
    0
    • girishG girish

      @portfield-slash no need to rebuild EC2/server. Are you able to reproduce this on our test server - https://my.demo.cloudron.io (username: cloudron password: cloudron) ?

      ChristopherMagC Offline
      ChristopherMagC Offline
      ChristopherMag
      wrote on last edited by
      #13

      @girish When I try to create an instance of Redash on that demo cloudron instance it gets stuck in a starting state and never progresses past that and I can see in the log that the workers keep restarting:

      05b2eec0-81a1-40d0-a419-be72f625cdfd-image.png

      Not sure this is related to the problem at hand as I don't have this issue when install Redash on my own instance of cloudron.

      girishG 1 Reply Last reply
      0
      • ChristopherMagC ChristopherMag

        @girish When I try to create an instance of Redash on that demo cloudron instance it gets stuck in a starting state and never progresses past that and I can see in the log that the workers keep restarting:

        05b2eec0-81a1-40d0-a419-be72f625cdfd-image.png

        Not sure this is related to the problem at hand as I don't have this issue when install Redash on my own instance of cloudron.

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

        @christophermag indeed, I can see that as well. It looks like there is some difference between the Cloudron versions. I am installing on latest dev where it seems to work fine but not on the stable release (7.0.4) which the demo and you guys are on. I will test on 7.0.4.

        K 1 Reply Last reply
        0
        • girishG girish

          @christophermag indeed, I can see that as well. It looks like there is some difference between the Cloudron versions. I am installing on latest dev where it seems to work fine but not on the stable release (7.0.4) which the demo and you guys are on. I will test on 7.0.4.

          K Offline
          K Offline
          kallados
          wrote on last edited by
          #15

          @girish Yes, my fresh installation on 7.04 also don't work.

          1 Reply Last reply
          0
          • portfield-slashP Offline
            portfield-slashP Offline
            portfield-slash
            wrote on last edited by
            #16

            I think WORKER TIMEOUT is a gunicorn error.

            Add the --timeout parameter in the gunicorn settings and
            Avoided the timeout by reloading the supervisor inside the container.

            I don't think it is recommended to change the settings in the container, so I think it is necessary to deal with it as a separate matter.

            /etc/supervisor/conf.d/redash.conf

            [program:web]
            directory=/app/code/redash
            command=/app/code/redash/bin/run gunicorn -b 0.0.0.0:5000 --name redash -w 4 --max-requests 1000 --timeout 300 redash.wsgi:app
            process_name=server
            user=cloudron
            numprocs=1
            autostart=true
            autorestart=true
            
            stdout_logfile=/dev/stdout
            stdout_logfile_maxbytes=0
            stderr_logfile=/dev/stderr
            stderr_logfile_maxbytes=0
            

            run sudo supervisorctl reload command.

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

              @ChristopherMag @portfield-slash I get the WORKER TIMEOUT error as well.

              13:51:16 - [2022-01-11 21:51:16 +0000] [46] [CRITICAL] WORKER TIMEOUT (pid:64)
              

              It seems this is because the queries queue is not processed at all. Per https://github.com/getredash/redash/blob/d8d7c78992e44a4b6d7fdd4c39ccc1c35cd8c7a9/redash/worker.py#L20 , they are many named queues . The Cloudron package only processes "periodic emails default" queues. I am struggling to find any docs or deployment code in redash that will help understand what the correct fix is.

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

                Making some progress here:

                • https://github.com/getredash/redash/issues/5625
                • https://github.com/getredash/redash/issues/5620
                • https://discuss.redash.io/t/query-auto-update-does-not-work-redash-v10/9353

                The issue is that we don't even process scheduled_queries because of pacakge mis-configuration. What the fix is, I am investigating.

                1 Reply Last reply
                0
                • girishG girish referenced this topic on
                • girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by girish
                  #19

                  @ChristopherMag @portfield-slash I have pushed an update, can you please check? Atleast, I am now able to query sqlite files just fine. Also, seeing all the queued jobs being processed. The new package version is 4.0.0-1 (so, it has the same changelog as 4.0.0, in case you get confused)

                  ChristopherMagC 1 Reply Last reply
                  0
                  • portfield-slashP Offline
                    portfield-slashP Offline
                    portfield-slash
                    wrote on last edited by
                    #20

                    @girish
                    Thank you for your support. I will confirm.

                    portfield-slashP 1 Reply Last reply
                    0
                    • portfield-slashP portfield-slash

                      @girish
                      Thank you for your support. I will confirm.

                      portfield-slashP Offline
                      portfield-slashP Offline
                      portfield-slash
                      wrote on last edited by
                      #21

                      @girish

                      It was confirmed that the connection test was successful.
                      I have also confirmed that I can execute queries.

                      Thank you for your support.

                      If necessary, I will report on github that the event has been resolved.

                      スクリーンショット 2022-01-12 11.59.58.png

                      1 Reply Last reply
                      0
                      • girishG girish

                        @ChristopherMag @portfield-slash I have pushed an update, can you please check? Atleast, I am now able to query sqlite files just fine. Also, seeing all the queued jobs being processed. The new package version is 4.0.0-1 (so, it has the same changelog as 4.0.0, in case you get confused)

                        ChristopherMagC Offline
                        ChristopherMagC Offline
                        ChristopherMag
                        wrote on last edited by
                        #22

                        @girish I have updated and been using everything for the last two days and it has been working as expected. Good to go from me, thank you!

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