Ask Question Run Forever

I freshly install metabase with postgresql backend, but after adding the database (sync etc)
the query was ok, but after a while (maye 1 or 2 hours i didn’t get exact date), that query become run forever, and i do :

  • discard saved field values
  • sync database schema
  • rescan field values

and it work again for 1 or 2 hours and the error happened again

my diagnostic :

{
  "browser-info": {
    "language": "en-US",
    "platform": "Linux x86_64",
    "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36",
    "vendor": "Google Inc."
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.7+10",
    "java.vendor": "AdoptOpenJDK",
    "java.vendor.url": "https://adoptopenjdk.net/",
    "java.version": "11.0.7",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.7+10",
    "os.name": "Linux",
    "os.version": "4.15.0-45-generic",
    "user.language": "en",
    "user.timezone": "GMT"
  },
  "metabase-info": {
    "databases": [
      "postgres"
    ],
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "12.3 (Debian 12.3-1.pgdg100+1)"
      },
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.2.8"
      }
    },
    "run-mode": "prod",
    "version": {
      "date": "2020-11-16",
      "tag": "v0.37.2",
      "branch": "release-x.37.x",
      "hash": "25e5f70"
    },
    "settings": {
      "report-timezone": null
    }
  }
}

upstream conf

  location @metabase {
        proxy_redirect off;
        proxy_buffering off;
        proxy_headers_hash_max_size 1024;
        proxy_connect_timeout  600s;
        proxy_send_timeout  600s;
        proxy_read_timeout  600s;
       proxy_http_version 1.1;
        proxy_set_header Connection "";

    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;

    proxy_pass http://metabase;
  }

and when i press the save button after do re-sync , i got this error on log

.....
[0b60f218-3615-4cd6-ac8e-44dab851bd45] 2020-12-02T16:55:10+07:00 DEBUG metabase.middleware.log PUT /api/database/2 200 726.5 ms (4 DB calls) App DB connections: 0/13 Jetty threads: 4/50 (3 idle, 0 queued) (122 total active threads) Queries in flight: 4 (0 queued)
[0b60f218-3615-4cd6-ac8e-44dab851bd45] 2020-12-02T16:55:10+07:00 ERROR metabase.sync.util Error syncing Fields for Table 'Table 7 'public.orders_products''
org.postgresql.util.PSQLException: An I/O error occurred while sending to the backend.
	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:337)
...
...
..
[0b60f218-3615-4cd6-ac8e-44dab851bd45] 2020-12-02T16:55:11+07:00 WARN metabase.driver.sql-jdbc.sync.describe-table Don't know how to map column type '_text' to a Field base_type, falling back to :type/*.
[0b60f218-3615-4cd6-ac8e-44dab851bd45] 2020-12-02T16:55:11+07:00 ERROR metabase.query-processor.middleware.catch-exceptions Error processing query: null
{:database_id 2,
 :started_at #t "2020-12-02T09:43:41.326180Z[GMT]",
 :via
 [{:status :failed,
   :class org.postgresql.util.PSQLException,
   :error "An I/O error occurred while sending to the backend.",
   :stacktrace
....
...
...
[0b60f218-3615-4cd6-ac8e-44dab851bd45] 2020-12-02T16:55:11+07:00 ERROR metabase.query-processor.middleware.catch-exceptions Error processing query: null
{:database_id 2,
 :started_at #t "2020-12-02T09:43:55.002398Z[GMT]",
 :via
 [{:status :failed,
   :class org.postgresql.util.PSQLException,
   :error "An I/O error occurred while sending to the backend.",
   :stacktrace
.....

thank you

Hi @yusuf.404
The only time I’ve ever seen that error was when Metabase had connection problems with the application database (which is Postgres for your instance).
Check the Postgres logs for any details on what could be the cause.

1 Like

thank you, after i moving to other vps that same provider with the database and all, the connection seems stable and didn’t find any error, thank you for the suggestion…