| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | "Vijayan, Vipin" <Vipin(dot)Vijayan(at)unilever(dot)com> |
| Cc: | "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>, "P-N, Pradeep" <Pradeep(dot)P-N(at)unilever(dot)com>, "M, Kishore" <Kishore(dot)M(at)unilever(dot)com>, "Sivanandham, Vishnu" <Vishnu(dot)Sivanandham(at)unilever(dot)com> |
| Subject: | Re: sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) disk I/O error |
| Date: | 2026-10-02 09:15:03 |
| Message-ID: | CA+OCxowFHDuZi4Jx0THgAWV_2gte2+FFrbVAxqyS-MzbXwdEiw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Fri, 2 Oct 2026 at 09:36, Vijayan, Vipin <Vipin(dot)Vijayan(at)unilever(dot)com>
wrote:
> Hi,
>
> Greetings.
>
>
>
> I looked into existing issues and couldn’t find the below issue also
> attempted to create an issue however was getting message Error unable to
> create issue, hence sending email.
>
>
>
> *While deploying pgadmin onto SAP BTP CF Subaccount getting attached
> error.*
>
>
>
> Here is the yml file content -
>
> ---
>
> applications:
>
> - name: pgadmin-web
>
> memory: 1G
>
> disk_quota: 1G
>
> health-check-type: process
>
> docker:
>
> image: dpage/pgadmin4:latest
>
> random-route: true
>
> env:
>
> PGADMIN_DEFAULT_EMAIL: admin(at)admin(dot)com
>
> PGADMIN_DEFAULT_PASSWORD: admin123
>
>
>
>
> *Anything I need to check please suggest and more than willing to make it
> work. *
> Regards,
>
> Vipin.
>
Hi Vipin,
The key line is sqlite3.OperationalError: disk I/O error, raised when
pgAdmin first writes to its SQLite configuration database in
/var/lib/pgadmin. The container's filesystem is refusing the write, so it
is an environment problem rather than a pgAdmin bug. You can ignore the
sudo warning: it only affects the mail relay.
A few things to try:
1. Raise disk_quota to 2G or more. On Cloud Foundry the quota has to hold
the unpacked Docker image as well as runtime data.
2. As a quick test, point SQLite at /tmp by adding
PGADMIN_CONFIG_SQLITE_PATH: "'/tmp/pgadmin4.db'" under env. Note the inner
quotes: the value is read as a Python literal. If it starts, the problem is
that particular path on that platform.
3. For a lasting fix, keep the configuration in PostgreSQL instead. Cloud
Foundry does not keep a container's local disk across restarts, so with
SQLite you would lose your users and saved servers every time the app
restarts. Bind a PostgreSQL service and
set PGADMIN_CONFIG_CONFIG_DATABASE_URI:
"'postgresql://user:password(at)host:5432/pgadmin'".
See https://www.pgadmin.org/docs/pgadmin4/latest/container_deployment.html
Separately, please change PGADMIN_DEFAULT_PASSWORD from admin123 before
this goes anywhere reachable, since random-route puts the app on a public
URL.
Regards, Dave
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Ponsdomenech | 2026-10-02 13:50:47 | Errors detected in pgAdmin 4 v9.16 with PostgreSQL 10.23 |
| Previous Message | Andrew Holub | 2026-09-29 16:54:47 | Bug list request |