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. Chatwoot
  3. Chatwoot 1.36.1 Upgrade Issue

Chatwoot 1.36.1 Upgrade Issue

Scheduled Pinned Locked Moved Solved Chatwoot
15 Posts 7 Posters 316 Views
  • 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.
  • C Offline
    C Offline
    cleveradmin
    wrote on Feb 28, 2025, 11:22 PM last edited by
    #1

    It appears the database crashes during upgrade from 1.35.0 to 1.36.1. Here is what we see:

    => Sourcing /app/data/env.sh
    Feb 28 16:21:22 => Starting chatwoot
    Feb 28 16:21:22 => Upgrading existing db
    Feb 28 16:21:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.20.35:3000
    Feb 28 16:21:36 I, [2025-02-28T23:21:36.197228 #10] INFO -- : [rake ip_lookup:setup] IP_LOOKUP_API_KEY empty. Skipping geoip database setup
    Feb 28 16:21:37 I, [2025-02-28T23:21:37.247106 #10] INFO -- : Migrating to CreateCaptainTables (20250104200055)
    Feb 28 16:21:37 == 20250104200055 CreateCaptainTables: migrating ==============================
    Feb 28 16:21:37 -- extension_enabled?("vector")
    Feb 28 16:21:37 -> 0.0176s
    Feb 28 16:21:37 -- enable_extension("vector")
    Feb 28 16:21:37 WARNING: terminating connection because of crash of another server process
    Feb 28 16:21:37 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
    Feb 28 16:21:37 HINT: In a moment you should be able to reconnect to the database and repeat your command.
    Feb 28 16:21:37 rails aborted!
    Feb 28 16:21:37 ActiveRecord::ConnectionNotEstablished: connection to server at "fd00:c107:d509::5", port 5432 failed: FATAL: the database system is in recovery mode (ActiveRecord::ConnectionNotEstablished)
    Feb 28 16:21:37 connection to server at "172.18.30.2", port 5432 failed: FATAL: the database system is in recovery mode
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>' Feb 28 16:21:37 2025-02-28T23:21:37Z Feb 28 16:21:37 Caused by: Feb 28 16:21:37 PG::ConnectionBad: connection to server at "fd00:c107:d509::5", port 5432 failed: FATAL: the database system is in recovery mode (PG::ConnectionBad) Feb 28 16:21:37 connection to server at "172.18.30.2", port 5432 failed: FATAL: the database system is in recovery mode Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>'
    Feb 28 16:21:37 2025-02-28T23:21:37Z
    Feb 28 16:21:37 Caused by:
    Feb 28 16:21:37 PG::ConnectionBad: connection to server at "fd00:c107:d509::5", port 5432 failed: FATAL: the database system is in recovery mode (PG::ConnectionBad)
    Feb 28 16:21:37 connection to server at "172.18.30.2", port 5432 failed: FATAL: the database system is in recovery mode
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>' Feb 28 16:21:37 2025-02-28T23:21:37Z Feb 28 16:21:37 Caused by: Feb 28 16:21:37 ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (ActiveRecord::StatementInvalid) Feb 28 16:21:37 This probably means the server terminated abnormally Feb 28 16:21:37 before or while processing the request. Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>'
    Feb 28 16:21:37 2025-02-28T23:21:37Z
    Feb 28 16:21:37 Caused by:
    Feb 28 16:21:37 PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (PG::ConnectionBad)
    Feb 28 16:21:37 This probably means the server terminated abnormally
    Feb 28 16:21:37 before or while processing the request.
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>' Feb 28 16:21:37 2025-02-28T23:21:37Z Feb 28 16:21:37 Caused by: Feb 28 16:21:37 ActiveRecord::ConnectionNotEstablished: connection to server at "fd00:c107:d509::5", port 5432 failed: FATAL: the database system is in recovery mode (ActiveRecord::ConnectionNotEstablished) Feb 28 16:21:37 connection to server at "172.18.30.2", port 5432 failed: FATAL: the database system is in recovery mode Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>'
    Feb 28 16:21:37 2025-02-28T23:21:37Z
    Feb 28 16:21:37 Caused by:
    Feb 28 16:21:37 PG::ConnectionBad: connection to server at "fd00:c107:d509::5", port 5432 failed: FATAL: the database system is in recovery mode (PG::ConnectionBad)
    Feb 28 16:21:37 connection to server at "172.18.30.2", port 5432 failed: FATAL: the database system is in recovery mode
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>' Feb 28 16:21:37 2025-02-28T23:21:37Z Feb 28 16:21:37 Caused by: Feb 28 16:21:37 ActiveRecord::StatementInvalid: PG::ConnectionBad: PQsocket() can't get socket descriptor (ActiveRecord::StatementInvalid) Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>'
    Feb 28 16:21:37 2025-02-28T23:21:37Z
    Feb 28 16:21:37 Caused by:
    Feb 28 16:21:37 PG::ConnectionBad: PQsocket() can't get socket descriptor (PG::ConnectionBad)
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>' Feb 28 16:21:37 2025-02-28T23:21:37Z Feb 28 16:21:37 Caused by: Feb 28 16:21:37 StandardError: Failed to enable 'vector' extension. Read more at https://chwt.app/v4/migration (StandardError) Feb 28 16:21:37 /app/code/db/migrate/20250104200055_create_captain_tables.rb:30:in rescue in setup_vector_extension'
    Feb 28 16:21:37 /app/code/db/migrate/20250104200055_create_captain_tables.rb:27:in setup_vector_extension' Feb 28 16:21:37 /app/code/db/migrate/20250104200055_create_captain_tables.rb:5:in up'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>' Feb 28 16:21:37 2025-02-28T23:21:37Z Feb 28 16:21:37 Caused by: Feb 28 16:21:37 ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (ActiveRecord::StatementInvalid) Feb 28 16:21:37 This probably means the server terminated abnormally Feb 28 16:21:37 before or while processing the request. Feb 28 16:21:37 /app/code/db/migrate/20250104200055_create_captain_tables.rb:28:in setup_vector_extension'
    Feb 28 16:21:37 /app/code/db/migrate/20250104200055_create_captain_tables.rb:5:in up' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in block (2 levels) in <main>'
    Feb 28 16:21:37 2025-02-28T23:21:37Z
    Feb 28 16:21:37 Caused by:
    Feb 28 16:21:37 PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (PG::ConnectionBad)
    Feb 28 16:21:37 This probably means the server terminated abnormally
    Feb 28 16:21:37 before or while processing the request.
    Feb 28 16:21:37 /app/code/db/migrate/20250104200055_create_captain_tables.rb:28:in setup_vector_extension' Feb 28 16:21:37 /app/code/db/migrate/20250104200055_create_captain_tables.rb:5:in up'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:26:in block (3 levels) in <main>' Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in each'
    Feb 28 16:21:37 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
    Feb 28 16:21:37 Tasks: TOP => db:migrate
    Feb 28 16:21:37 (See full trace by running task with --trace)

    1 Reply Last reply
    0
    • C Offline
      C Offline
      cleveradmin
      wrote on Feb 28, 2025, 11:27 PM last edited by
      #2

      We restored from backup to 1.35.0 and it is working again. Have not attempted the upgrade again.

      1 Reply Last reply
      0
      • B Offline
        B Offline
        BrutalBirdie
        Partner
        wrote on Feb 28, 2025, 11:35 PM last edited by
        #3

        Please format your logs in a code block like

        ```
        your code goes here
        ```

        Resulting in

        your code goes here

        Make it less difficult for me and everyone's eyes to read your logs 😉

        Like my work? Consider donating a drink. Cheers!

        1 Reply Last reply
        0
        • B Offline
          B Offline
          BrutalBirdie
          Partner
          wrote on Feb 28, 2025, 11:40 PM last edited by
          #4

          Feb 28 16:21:37 DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

          Did the app or the Postgres service maybe run out of memory? 🤔 resulting to this issue?

          Like my work? Consider donating a drink. Cheers!

          1 Reply Last reply
          0
          • nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on Mar 2, 2025, 4:23 PM last edited by
            #5

            @cleveradmin can you try to clone the app instance and then perform the update on the cloned one? This way we can see if it is reproducible.

            1 Reply Last reply
            0
            • M Offline
              M Offline
              mazarian
              wrote 21 days ago last edited by
              #6

              I am having a similar error in my logs, but it's happening well after the upgrade.

              Mar 18 10:06:07 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:06:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:06:23 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:06:33 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:06:43 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:06:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:06:54 => Sourcing /app/data/env.sh
Mar 18 10:06:54 => Starting chatwoot
Mar 18 10:06:54 => Upgrading existing db
Mar 18 10:06:56 I, [2025-03-18T17:06:56.956461 #10] INFO -- : [rake ip_lookup:setup] IP_LOOKUP_API_KEY empty. Skipping geoip database setup
Mar 18 10:06:57 2025-03-18T17:06:57Z
Mar 18 10:06:57 (See full trace by running task with --trace)
Mar 18 10:06:57 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:06:57 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:06:57 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:06:57 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:06:57 ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (ActiveRecord::StatementInvalid)
Mar 18 10:06:57 Caused by:
Mar 18 10:06:57 PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (PG::ConnectionBad)
Mar 18 10:06:57 Tasks: TOP => db:chatwoot_prepare
Mar 18 10:06:57 This probably means the server terminated abnormally
Mar 18 10:06:57 This probably means the server terminated abnormally
Mar 18 10:06:57 before or while processing the request.
Mar 18 10:06:57 before or while processing the request.
Mar 18 10:06:57 rails aborted!
Mar 18 10:07:07 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:07:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:07:26 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:07:33 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:07:43 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:07:43 BoxError: Unknown install command in apptask:error
Mar 18 10:07:43 BoxError: Unknown install command in apptask:error
Mar 18 10:07:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:07:57 => Starting chatwoot
Mar 18 10:07:57 => Sourcing /app/data/env.sh
Mar 18 10:07:57 => Upgrading existing db
Mar 18 10:08:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.185:3000
Mar 18 10:08:00 I, [2025-03-18T17:08:00.416259 #10] INFO -- : [rake ip_lookup:setup] IP_LOOKUP_API_KEY empty. Skipping geoip database setup
Mar 18 10:08:00 rails aborted!
Mar 18 10:08:00 ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (ActiveRecord::StatementInvalid)
Mar 18 10:08:00 This probably means the server terminated abnormally
Mar 18 10:08:00 before or while processing the request.
Mar 18 10:08:00 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:08:00 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:08:00 2025-03-18T17:08:00Z
Mar 18 10:08:00 Caused by:
Mar 18 10:08:00 PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (PG::ConnectionBad)
Mar 18 10:08:00 This probably means the server terminated abnormally
Mar 18 10:08:00 before or while processing the request.
Mar 18 10:08:00 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:08:00 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:08:00 Tasks: TOP => db:chatwoot_prepare
Mar 18 10:08:00 (See full trace by running task with --trace)
Mar 18 10:08:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:08:27 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:08:33 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:08:43 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:08:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:09:01 => Starting chatwoot
Mar 18 10:09:01 => Sourcing /app/data/env.sh
Mar 18 10:09:01 => Upgrading existing db
Mar 18 10:09:03 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.185:3000
Mar 18 10:09:03 I, [2025-03-18T17:09:03.629615 #10] INFO -- : [rake ip_lookup:setup] IP_LOOKUP_API_KEY empty. Skipping geoip database setup
Mar 18 10:09:04 rails aborted!
Mar 18 10:09:04 ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (ActiveRecord::StatementInvalid)
Mar 18 10:09:04 This probably means the server terminated abnormally
Mar 18 10:09:04 before or while processing the request.
Mar 18 10:09:04 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:09:04 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:09:04 2025-03-18T17:09:04Z
Mar 18 10:09:04 Caused by:
Mar 18 10:09:04 PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (PG::ConnectionBad)
Mar 18 10:09:04 This probably means the server terminated abnormally
Mar 18 10:09:04 before or while processing the request.
Mar 18 10:09:04 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:09:04 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:09:04 Tasks: TOP => db:chatwoot_prepare
Mar 18 10:09:04 (See full trace by running task with --trace)
Mar 18 10:09:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:09:27 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:09:33 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:09:43 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:09:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:10:03 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000

              I tried recovering from backup and cloning and am getting the following error:

              An error occurred during the clone operation: Addons Error: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/e2f314e0-389e-4c1b-8e80-9852e13db8e3/postgresqldump to http://172.18.30.2:3000/databases/dbe2f314e0389e4c1b8e809852e13db8e3/restore?access_token=b637659aed0a708f188d2902fc267163718b8c6777cd722433926b0654ff03c7c2fc782f7c39a559f0d1954f031c7215eb96ebf6bc759500e2419d84607396d249c157dc7a7db537926351f20ae6a23261db0a55c93e07a278161db6c2e7f4fdd04756ff7cc1cd30bd67096101d9b83b643ebf91abf5f2e3a2026dbd93d1ae6b&username=usere2f314e0389e4c1b8e809852e13db8e3: status 500 complete false

              Any help would greatly be appreciated!

              1 Reply Last reply
              0
              • nebulonN Offline
                nebulonN Offline
                nebulon
                Staff
                wrote 21 days ago last edited by
                #7

                Is your postgres service up and running? Since it returned a 500 status code during database import, it should have error messages in its logs.

                1 Reply Last reply
                0
                • M Offline
                  M Offline
                  mazarian
                  wrote 21 days ago last edited by
                  #8

                  I'm not quite sure how to check - I am only able to get into recovery mode and when going into the terminal and pressing the Postgres button, I see this:

                  root@fa89594f-7176-4a81-9c25-1686af1e50da:/app/code# PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} psql -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE} 
psql (14.9 (Ubuntu 14.9-0ubuntu0.22.04.1), server 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1))
WARNING: psql major version 14, server major version 16.
         Some psql features might not work.
Type "help" for help.

dbfa89594f71764a819c251686af1e50da=>
                  andreasduerenA 1 Reply Last reply 21 days ago
                  0
                  • M mazarian
                    21 days ago

                    I'm not quite sure how to check - I am only able to get into recovery mode and when going into the terminal and pressing the Postgres button, I see this:

                    root@fa89594f-7176-4a81-9c25-1686af1e50da:/app/code# PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} psql -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE} 
psql (14.9 (Ubuntu 14.9-0ubuntu0.22.04.1), server 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1))
WARNING: psql major version 14, server major version 16.
         Some psql features might not work.
Type "help" for help.

dbfa89594f71764a819c251686af1e50da=>
                    andreasduerenA Offline
                    andreasduerenA Offline
                    andreasdueren
                    wrote 21 days ago last edited by
                    #9

                    @mazarian Go to https://my.tld.com/#/services and increase memory if necessary and/or reboot that service

                    M 1 Reply Last reply 21 days ago
                    0
                    • andreasduerenA andreasdueren
                      21 days ago

                      @mazarian Go to https://my.tld.com/#/services and increase memory if necessary and/or reboot that service

                      M Offline
                      M Offline
                      mazarian
                      wrote 21 days ago last edited by
                      #10

                      @andreasdueren and @nebulon thank you both for your replies!

                      I just looked at my services, and things looked ok. Graphite was at 84% and I doubled the memory. I also doubled my Postgres memory and Redis memory (for the affected Chatwoot app) but none of those things seemed to help.

                      cefff62e-2183-4385-97eb-fa7a62bb8e65-image.png

                      1 Reply Last reply
                      0
                      • M Offline
                        M Offline
                        mazarian
                        wrote 21 days ago last edited by
                        #11

                        It's also odd- when I try switching between recovery mode off and on, Redis throws errors and I have to restart the service. But doing so doesn't allow me to start the application outside of recovery mode and still in the error logs, I see the same PG errors.

                        1 Reply Last reply
                        0
                        • M Offline
                          M Offline
                          mazarian
                          wrote 21 days ago last edited by
                          #12

                          Just wanted to add - it seems like I am having to restore from backup for many of my apps. All of the restores are working except for Chatwoot. It seems like something went wrong after the upgrade to Cloudron 8.3.

                          S 1 Reply Last reply 20 days ago
                          1
                          • J Offline
                            J Offline
                            joseph
                            Staff
                            wrote 21 days ago last edited by
                            #13

                            @mazarian if you can write to support@cloudron.io, we can take a look . it seems a few hit this issue with restoring chatwoot on the recent postgres. however, we haven't been to reproduce it.

                            1 Reply Last reply
                            0
                            • M mazarian
                              21 days ago

                              Just wanted to add - it seems like I am having to restore from backup for many of my apps. All of the restores are working except for Chatwoot. It seems like something went wrong after the upgrade to Cloudron 8.3.

                              S Offline
                              S Offline
                              stevespaw
                              wrote 20 days ago last edited by
                              #14

                              @mazarian said in Chatwoot 1.36.1 Upgrade Issue:

                              Just wanted to add - it seems like I am having to restore from backup for many of my apps. All of the restores are working except for Chatwoot. It seems like something went wrong after the upgrade to Cloudron 8.3.

                              Same issue here!

                              1 Reply Last reply
                              0
                              • S Offline
                                S Offline
                                stevespaw
                                wrote 20 days ago last edited by
                                #15

                                8.3.1 seems to have fixed this issue! Thanks team Cloudron!

                                1 Reply Last reply
                                0
                                • nebulonN nebulon marked this topic as a question 20 days ago
                                • nebulonN nebulon has marked this topic as solved 20 days ago
                                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