[Support] jj9987 - PostgreSQL


Recommended Posts

8 hours ago, Eddyall said:

Hello, recently made the error of deleting my Postgres11 docker instead of the pgAdmin 4 docker to which I lost the password for, I got the two dockers working again except I don't have my data it seems. I had two database for Szurubooru, one might be lost (lame but oh well) but the other shouldn't have been affected by me fumbling around with reinstalling the postgres docker. Post above for avlec were the solution basicly. However I'm not too sure about how to link/add the second database so the postgres docker can see it. Any simple way to add it back from pgAdmin? Or even not so simple ways

Edit: Suggestion on how to set up auto backup/snapshot for the docker image so I can more easily fix that kind of screw up in the future also welcome.

Howdy. Just deleting the Docker won't wipe your data, unless you specifically also delete the appdata folder (whether it is on the array or cache drive). So if the appdata is still there and you recreate the container (has to be the same major version of PostgreSQL), all the databases and the data should still be there. As for recovery, standard data recovery applies, but it is much harder to do with databases, since it is not just one file. And if part of it is missing, basically all is gone.

 

You can add additional databases when you log in as superuser `postgres` and run `CREATE DATABASE <name>;`. Security-wise I'd also recommend to have different users with the necessary permissions (e.g. one user can only access one database etc).

 

For auto-backups, you can run a cron job, that runs `pg_dump` or `pg_dumpall`. Alternatively you could use pgBackRest, but there is no template for it at this moment, it needs additional configuration and is more complicated.

 

---

 

Made some changes to the templates:

- BREAKING CHANGE: Database volume paths now include version tag, e.g. `/mnt/cache/appdata/postgresql10` so you can run multiple instances with different versions at the same time.

BREAKING CHANGE: PostgreSQL 10 template got changed, this could have broken stuff on old users. I am not familiar with the template changes on older versions.

- Added PostgreSQL 12, 13 and 14 templates.

- Container names changed to lowercase and includes version, e.g. `postgresql14`. This should make it easier for using in custom networks.

- Brought the templates up to date with current schema version.

 

Hopefully it is more user-friendly now. Feedback welcome. Sorry, it's been too long since I updated them.

Edited by jj9987
  • Thanks 1
Link to comment
On 1/23/2021 at 6:17 PM, hrv231 said:

Hello,

I'm running now this docker and I also can't access the folder.

I even created another folder and pointed to it, and after starting the docker, the folder gets inaccessible.

 

image.png.17648026ff2c5245ce7395cb8d41b29a.png

Hi, I too have just stumbled across this permission issue. When the docker container is restarted, the 'postgres' app data folder loses the correct permissions. I'm able to correct this by running chmod -R u-x,go-rwx,go+u,ugo+X '/mnt/user/appdata/postgres' then chown -R nobody:users '/mnt/user/appdata/postgres' but after I restart the container, the permissions are gone. Any help would be appreciated as this was not an issue before. 

Link to comment
  • 3 weeks later...
3 hours ago, spacezmonkey said:

Hello , I install postgres 11 and unable to login suing ip address. 

 

when i check the log, there is "invalid length of startup packet" . I tried different version, all of them give me same error.. may I know how should i preceed. 

 

What version of psql are you using to connect to it? What error is psql giving? Server logs do not give very much information what the error is.

Link to comment
  • 2 weeks later...

Hello,

 

I have pgsql install before. I have removed it and start new. I also cleaned up the appdata of it. But I get this error(below pic) for the new installation and I can't start the app.

 

image.png.9ca691f9ed473da9a32ff27ee4831ce8.png

 

I go to directory /var/lib/ but there is no postgresql directory on it. Where can I find it? How to fix this?

 

 

Link to comment
1 hour ago, HHUBS said:

Hello,

 

I have pgsql install before. I have removed it and start new. I also cleaned up the appdata of it. But I get this error(below pic) for the new installation and I can't start the app.

 

image.png.9ca691f9ed473da9a32ff27ee4831ce8.png

 

I go to directory /var/lib/ but there is no postgresql directory on it. Where can I find it? How to fix this?

 

 

Howdy

 

Docker works by mounting host paths to container paths. These are called volumes.

Check where /var/lib/postgresql/data is mounted to. Latest version of the template defaults to /mnt/cache/appdata/postgresql<version>, e.g. /mnt/cache/appdata/postgresql14. That directory either should not exist, be empty or only contain PostgreSQL own files.

Link to comment
  • 6 months later...

I had to recreate my my docker image and after reinstalling the postgres14 container, I get this in the logs when attempting to start the container. No containers are able to connect to Postgres and all connections are refused. I'm at a loss on how to fix this or what is causing it. Any help would be greatly appreciated. 

 

text  error  warn  system  array  login  

2022-07-05 23:07:28.736 MDT [1] LOG:  starting PostgreSQL 14.4 (Debian 14.4-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2022-07-05 23:07:28.737 MDT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-07-05 23:07:28.737 MDT [1] LOG:  listening on IPv6 address "::", port 5432
2022-07-05 23:07:28.743 MDT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-07-05 23:07:28.748 MDT [26] LOG:  database system was interrupted; last known up at 2022-07-05 23:06:49 MDT
2022-07-05 23:07:28.761 MDT [26] LOG:  database system was not properly shut down; automatic recovery in progress
2022-07-05 23:07:28.764 MDT [26] LOG:  redo starts at 1/34FC9FD8
2022-07-05 23:07:28.764 MDT [26] LOG:  invalid record length at 1/34FCA028: wanted 24, got 0
2022-07-05 23:07:28.764 MDT [26] LOG:  redo done at 1/34FC9FD8 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2022-07-05 23:07:28.782 MDT [1] LOG:  database system is ready to accept connections

PostgreSQL Database directory appears to contain a database; Skipping initialization
 

Link to comment
1 hour ago, Snack_Ears said:

I had to recreate my my docker image and after reinstalling the postgres14 container, I get this in the logs when attempting to start the container. No containers are able to connect to Postgres and all connections are refused. I'm at a loss on how to fix this or what is causing it. Any help would be greatly appreciated. 

 

text  error  warn  system  array  login  

2022-07-05 23:07:28.736 MDT [1] LOG:  starting PostgreSQL 14.4 (Debian 14.4-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2022-07-05 23:07:28.737 MDT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-07-05 23:07:28.737 MDT [1] LOG:  listening on IPv6 address "::", port 5432
2022-07-05 23:07:28.743 MDT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-07-05 23:07:28.748 MDT [26] LOG:  database system was interrupted; last known up at 2022-07-05 23:06:49 MDT
2022-07-05 23:07:28.761 MDT [26] LOG:  database system was not properly shut down; automatic recovery in progress
2022-07-05 23:07:28.764 MDT [26] LOG:  redo starts at 1/34FC9FD8
2022-07-05 23:07:28.764 MDT [26] LOG:  invalid record length at 1/34FCA028: wanted 24, got 0
2022-07-05 23:07:28.764 MDT [26] LOG:  redo done at 1/34FC9FD8 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2022-07-05 23:07:28.782 MDT [1] LOG:  database system is ready to accept connections

PostgreSQL Database directory appears to contain a database; Skipping initialization
 

These logs are normal, nothing alarming. It says it is ready to accept connections, so could it be something else? Wrong IP perhaps?

Link to comment
  • 2 weeks later...

I recently migrated from MariaDB to Postgres 14 for my nextcloud instance. After it working for a few hours it appears the database went down and I'm no longer able to start up the container.  Does anyone have an idea whats going on or how to fix it?

 

2022-07-15 19:28:41.617 PDT [1] LOG:  starting PostgreSQL 14.4 (Debian 14.4-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2022-07-15 19:28:41.617 PDT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-07-15 19:28:41.617 PDT [1] LOG:  listening on IPv6 address "::", port 5432
2022-07-15 19:28:41.618 PDT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-07-15 19:28:41.621 PDT [61] LOG:  database system was shut down at 2022-07-15 19:28:41 PDT
2022-07-15 19:28:41.628 PDT [1] LOG:  database system is ready to accept connections
2022-07-15 20:38:58.591 PDT [534] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:38:58.591 PDT [534] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-15 20:38:58.591 PDT [534] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:38:58.592 PDT [533] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:38:58.592 PDT [533] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-15 20:38:58.592 PDT [533] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:49:22.731 PDT [676] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:49:22.731 PDT [676] DETAIL:  Key (fileid)=(598104) already exists.
2022-07-15 20:49:22.731 PDT [676] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:51:15.567 PDT [721] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:51:15.567 PDT [721] DETAIL:  Key (fileid)=(617234) already exists.
2022-07-15 20:51:15.567 PDT [721] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:51:15.567 PDT [720] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:51:15.567 PDT [720] DETAIL:  Key (fileid)=(617151) already exists.
2022-07-15 20:51:15.567 PDT [720] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:51:15.603 PDT [722] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:51:15.603 PDT [722] DETAIL:  Key (fileid)=(617107) already exists.
2022-07-15 20:51:15.603 PDT [722] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:51:19.705 PDT [725] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:51:19.705 PDT [725] DETAIL:  Key (fileid)=(617230) already exists.
2022-07-15 20:51:19.705 PDT [725] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 21:25:24.379 PDT [1135] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 21:25:24.379 PDT [1135] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-15 21:25:24.379 PDT [1135] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 21:25:24.404 PDT [1136] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 21:25:24.404 PDT [1136] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-15 21:25:24.404 PDT [1136] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 21:28:46.939 PDT [1202] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 21:28:46.939 PDT [1202] DETAIL:  Key (fileid)=(598104) already exists.
2022-07-15 21:28:46.939 PDT [1202] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 22:01:31.796 PDT [1839] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 22:01:31.796 PDT [1839] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-15 22:01:31.796 PDT [1839] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 22:01:31.797 PDT [1840] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 22:01:31.797 PDT [1840] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-15 22:01:31.797 PDT [1840] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 22:29:43.628 PDT [2224] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 22:29:43.628 PDT [2224] DETAIL:  Key (fileid)=(617234) already exists.
2022-07-15 22:29:43.628 PDT [2224] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 22:31:47.146 PDT [2261] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 22:31:47.146 PDT [2261] DETAIL:  Key (fileid)=(598104) already exists.
2022-07-15 22:31:47.146 PDT [2261] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 23:42:54.219 PDT [2883] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 23:42:54.219 PDT [2883] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-15 23:42:54.219 PDT [2883] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 23:42:54.221 PDT [2884] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 23:42:54.221 PDT [2884] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-15 23:42:54.221 PDT [2884] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-16 02:48:26.223 PDT [4045] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-16 02:48:26.223 PDT [4045] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-16 02:48:26.223 PDT [4045] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-16 02:48:26.235 PDT [4044] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-16 02:48:26.235 PDT [4044] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-16 02:48:26.235 PDT [4044] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-16 03:37:21.562 PDT [4367] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-16 03:37:21.562 PDT [4367] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-16 03:37:21.562 PDT [4367] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-16 03:37:21.562 PDT [4368] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-16 03:37:21.562 PDT [4368] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-16 03:37:21.562 PDT [4368] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-16 05:00:16.151 PDT [62] PANIC:  could not open file "pg_commit_ts": No such file or directory
2022-07-16 05:00:16.162 PDT [1] LOG:  checkpointer process (PID 62) was terminated by signal 6: Aborted
2022-07-16 05:00:16.162 PDT [1] LOG:  terminating any other active server processes
2022-07-16 05:00:16.171 PDT [1] LOG:  all server processes terminated; reinitializing
2022-07-16 05:00:16.201 PDT [1] FATAL:  could not open directory "pg_notify": No such file or directory
2022-07-16 05:00:16.203 PDT [1] LOG:  database system is shut down
2022-07-16 09:36:58.772 PDT [1] FATAL:  could not open directory "pg_notify": No such file or directory
2022-07-16 09:36:58.774 PDT [1] LOG:  database system is shut down
2022-07-16 09:37:09.363 PDT [1] FATAL:  could not open directory "pg_notify": No such file or directory
2022-07-16 09:37:09.366 PDT [1] LOG:  database system is shut down
2022-07-16 10:04:43.220 PDT [1] FATAL:  could not open directory "pg_notify": No such file or directory
2022-07-16 10:04:43.222 PDT [1] LOG:  database system is shut down


PostgreSQL Database directory appears to contain a database; Skipping initialization


PostgreSQL Database directory appears to contain a database; Skipping initialization


PostgreSQL Database directory appears to contain a database; Skipping initialization

 

Link to comment

If someone hits the same issue it turns out that if you follow the template and directly put your data on a cache like /mnt/ssd_cache/appdata/ instead of /mnt/user/appdata whenever mover gets invoked it will move your files off the cache. To fix this you need to use the user path instead of the ssd cache directly. 

 

On 7/16/2022 at 10:12 AM, TapIt said:

I recently migrated from MariaDB to Postgres 14 for my nextcloud instance. After it working for a few hours it appears the database went down and I'm no longer able to start up the container.  Does anyone have an idea whats going on or how to fix it?

 

2022-07-15 19:28:41.617 PDT [1] LOG:  starting PostgreSQL 14.4 (Debian 14.4-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2022-07-15 19:28:41.617 PDT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-07-15 19:28:41.617 PDT [1] LOG:  listening on IPv6 address "::", port 5432
2022-07-15 19:28:41.618 PDT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-07-15 19:28:41.621 PDT [61] LOG:  database system was shut down at 2022-07-15 19:28:41 PDT
2022-07-15 19:28:41.628 PDT [1] LOG:  database system is ready to accept connections
2022-07-15 20:38:58.591 PDT [534] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:38:58.591 PDT [534] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-15 20:38:58.591 PDT [534] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:38:58.592 PDT [533] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:38:58.592 PDT [533] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-15 20:38:58.592 PDT [533] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:49:22.731 PDT [676] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:49:22.731 PDT [676] DETAIL:  Key (fileid)=(598104) already exists.
2022-07-15 20:49:22.731 PDT [676] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:51:15.567 PDT [721] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:51:15.567 PDT [721] DETAIL:  Key (fileid)=(617234) already exists.
2022-07-15 20:51:15.567 PDT [721] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:51:15.567 PDT [720] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:51:15.567 PDT [720] DETAIL:  Key (fileid)=(617151) already exists.
2022-07-15 20:51:15.567 PDT [720] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:51:15.603 PDT [722] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:51:15.603 PDT [722] DETAIL:  Key (fileid)=(617107) already exists.
2022-07-15 20:51:15.603 PDT [722] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 20:51:19.705 PDT [725] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 20:51:19.705 PDT [725] DETAIL:  Key (fileid)=(617230) already exists.
2022-07-15 20:51:19.705 PDT [725] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 21:25:24.379 PDT [1135] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 21:25:24.379 PDT [1135] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-15 21:25:24.379 PDT [1135] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 21:25:24.404 PDT [1136] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 21:25:24.404 PDT [1136] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-15 21:25:24.404 PDT [1136] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 21:28:46.939 PDT [1202] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 21:28:46.939 PDT [1202] DETAIL:  Key (fileid)=(598104) already exists.
2022-07-15 21:28:46.939 PDT [1202] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 22:01:31.796 PDT [1839] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 22:01:31.796 PDT [1839] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-15 22:01:31.796 PDT [1839] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 22:01:31.797 PDT [1840] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 22:01:31.797 PDT [1840] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-15 22:01:31.797 PDT [1840] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 22:29:43.628 PDT [2224] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 22:29:43.628 PDT [2224] DETAIL:  Key (fileid)=(617234) already exists.
2022-07-15 22:29:43.628 PDT [2224] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 22:31:47.146 PDT [2261] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 22:31:47.146 PDT [2261] DETAIL:  Key (fileid)=(598104) already exists.
2022-07-15 22:31:47.146 PDT [2261] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 23:42:54.219 PDT [2883] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 23:42:54.219 PDT [2883] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-15 23:42:54.219 PDT [2883] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-15 23:42:54.221 PDT [2884] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-15 23:42:54.221 PDT [2884] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-15 23:42:54.221 PDT [2884] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-16 02:48:26.223 PDT [4045] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-16 02:48:26.223 PDT [4045] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-16 02:48:26.223 PDT [4045] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-16 02:48:26.235 PDT [4044] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-16 02:48:26.235 PDT [4044] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-16 02:48:26.235 PDT [4044] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-16 03:37:21.562 PDT [4367] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-16 03:37:21.562 PDT [4367] DETAIL:  Key (fileid)=(669277) already exists.
2022-07-16 03:37:21.562 PDT [4367] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-16 03:37:21.562 PDT [4368] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-07-16 03:37:21.562 PDT [4368] DETAIL:  Key (fileid)=(617227) already exists.
2022-07-16 03:37:21.562 PDT [4368] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-07-16 05:00:16.151 PDT [62] PANIC:  could not open file "pg_commit_ts": No such file or directory
2022-07-16 05:00:16.162 PDT [1] LOG:  checkpointer process (PID 62) was terminated by signal 6: Aborted
2022-07-16 05:00:16.162 PDT [1] LOG:  terminating any other active server processes
2022-07-16 05:00:16.171 PDT [1] LOG:  all server processes terminated; reinitializing
2022-07-16 05:00:16.201 PDT [1] FATAL:  could not open directory "pg_notify": No such file or directory
2022-07-16 05:00:16.203 PDT [1] LOG:  database system is shut down
2022-07-16 09:36:58.772 PDT [1] FATAL:  could not open directory "pg_notify": No such file or directory
2022-07-16 09:36:58.774 PDT [1] LOG:  database system is shut down
2022-07-16 09:37:09.363 PDT [1] FATAL:  could not open directory "pg_notify": No such file or directory
2022-07-16 09:37:09.366 PDT [1] LOG:  database system is shut down
2022-07-16 10:04:43.220 PDT [1] FATAL:  could not open directory "pg_notify": No such file or directory
2022-07-16 10:04:43.222 PDT [1] LOG:  database system is shut down


PostgreSQL Database directory appears to contain a database; Skipping initialization


PostgreSQL Database directory appears to contain a database; Skipping initialization


PostgreSQL Database directory appears to contain a database; Skipping initialization

 

 

  • Like 1
  • Upvote 1
Link to comment
  • 2 weeks later...
On 7/17/2022 at 12:26 PM, TapIt said:

If someone hits the same issue it turns out that if you follow the template and directly put your data on a cache like /mnt/ssd_cache/appdata/ instead of /mnt/user/appdata whenever mover gets invoked it will move your files off the cache. To fix this you need to use the user path instead of the ssd cache directly. 

 

 

 

Thank you! I 100% had this issue. Didn't put together it was happening when mover hit.

Link to comment
  • 3 weeks later...
On 7/17/2022 at 7:26 PM, TapIt said:

If someone hits the same issue it turns out that if you follow the template and directly put your data on a cache like /mnt/ssd_cache/appdata/ instead of /mnt/user/appdata whenever mover gets invoked it will move your files off the cache. To fix this you need to use the user path instead of the ssd cache directly. 

 

 

If I understand you corretly, I have to change the Diretory in the template from /mnt/cache/appdata/postgresql14 to /mnt/user/appdata/postgresql14 ?

Link to comment
  • 2 weeks later...
On 7/17/2022 at 7:26 PM, TapIt said:

If someone hits the same issue it turns out that if you follow the template and directly put your data on a cache like /mnt/ssd_cache/appdata/ instead of /mnt/user/appdata whenever mover gets invoked it will move your files off the cache. To fix this you need to use the user path instead of the ssd cache directly. 

 

 

I have changed the Path in the template, but still gets this errors in the Logs, may someone could help?

 

 

2022-08-30 02:02:54.002 CEST [32368] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 02:02:54.002 CEST [32368] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 03:51:48.432 CEST [5383] ERROR:  duplicate key value violates unique constraint "fs_storage_path_hash"
2022-08-30 03:51:48.432 CEST [5383] DETAIL:  Key (storage, path_hash)=(22, 1112d78c0dc102e1c14400917b3ee4b7) already exists.
2022-08-30 03:51:48.432 CEST [5383] STATEMENT:  INSERT INTO "oc_filecache" ("mimepart", "mimetype", "mtime", "size", "etag", "storage_mtime", "permissions", "name", "parent", "checksum", "path_hash", "path", "storage") VALUES($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13)
2022-08-30 06:25:50.393 CEST [18511] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 06:25:50.393 CEST [18511] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 06:25:50.393 CEST [18511] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 06:26:13.339 CEST [18543] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 06:26:13.339 CEST [18543] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 06:26:13.339 CEST [18543] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 08:04:18.102 CEST [21370] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 08:04:18.102 CEST [21370] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 08:04:18.102 CEST [21370] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 08:05:43.673 CEST [21466] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 08:05:43.673 CEST [21466] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 08:05:43.673 CEST [21466] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 08:06:08.112 CEST [21511] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 08:06:08.112 CEST [21511] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 08:06:08.112 CEST [21511] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 17:36:49.465 CEST [23330] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 17:36:49.465 CEST [23330] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 17:36:49.465 CEST [23330] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 17:42:16.024 CEST [23459] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 17:42:16.024 CEST [23459] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 17:42:16.024 CEST [23459] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 17:42:41.089 CEST [23497] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 17:42:41.089 CEST [23497] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 17:42:41.089 CEST [23497] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 18:17:03.999 CEST [1] LOG:  received fast shutdown request
2022-08-30 18:17:04.015 CEST [1] LOG:  aborting any active transactions
2022-08-30 18:17:04.017 CEST [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2022-08-30 18:17:04.021 CEST [27] LOG:  shutting down
2022-08-30 18:17:04.228 CEST [1] LOG:  database system is shut down
2022-08-30 18:17:08.356 CEST [1] LOG:  starting PostgreSQL 14.5 (Debian 14.5-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2022-08-30 18:17:08.357 CEST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-08-30 18:17:08.357 CEST [1] LOG:  listening on IPv6 address "::", port 5432
2022-08-30 18:17:08.436 CEST [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-08-30 18:17:08.460 CEST [26] LOG:  database system was shut down at 2022-08-30 18:17:04 CEST
2022-08-30 18:17:08.473 CEST [1] LOG:  database system is ready to accept connections
2022-08-30 18:40:25.112 CEST [599] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 18:40:25.112 CEST [599] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 18:40:25.112 CEST [599] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 18:41:56.383 CEST [711] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 18:41:56.383 CEST [711] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 18:41:56.383 CEST [711] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 18:42:21.617 CEST [742] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 18:42:21.617 CEST [742] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 18:42:21.617 CEST [742] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 19:04:32.902 CEST [1659] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 19:04:32.902 CEST [1659] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 19:04:32.902 CEST [1659] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 19:06:13.354 CEST [1776] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 19:06:13.354 CEST [1776] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 19:06:13.354 CEST [1776] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 19:06:38.615 CEST [1806] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 19:06:38.615 CEST [1806] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 19:06:38.615 CEST [1806] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 19:11:24.655 CEST [2026] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 19:11:24.655 CEST [2026] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 19:11:24.655 CEST [2026] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 19:31:18.384 CEST [1] LOG:  received fast shutdown request
2022-08-30 19:31:18.390 CEST [1] LOG:  aborting any active transactions
2022-08-30 19:31:18.394 CEST [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2022-08-30 19:31:18.394 CEST [27] LOG:  shutting down
2022-08-30 19:31:18.646 CEST [1] LOG:  database system is shut down
2022-08-30 19:31:22.796 CEST [1] LOG:  starting PostgreSQL 14.5 (Debian 14.5-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2022-08-30 19:31:22.796 CEST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-08-30 19:31:22.796 CEST [1] LOG:  listening on IPv6 address "::", port 5432
2022-08-30 19:31:22.864 CEST [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-08-30 19:31:22.879 CEST [26] LOG:  database system was shut down at 2022-08-30 19:31:18 CEST
2022-08-30 19:31:22.888 CEST [1] LOG:  database system is ready to accept connections
2022-08-30 23:20:14.102 CEST [2521] ERROR:  duplicate key value violates unique constraint "fs_storage_path_hash"
2022-08-30 23:20:14.102 CEST [2521] DETAIL:  Key (storage, path_hash)=(22, fa5878d7e8273870e0757d725906ffec) already exists.
2022-08-30 23:20:14.102 CEST [2521] STATEMENT:  INSERT INTO "oc_filecache" ("mimepart", "mimetype", "mtime", "size", "etag", "storage_mtime", "permissions", "name", "parent", "checksum", "path_hash", "path", "storage") VALUES($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13)
2022-08-30 23:20:24.030 CEST [2528] ERROR:  duplicate key value violates unique constraint "fs_storage_path_hash"
2022-08-30 23:20:24.030 CEST [2528] DETAIL:  Key (storage, path_hash)=(22, 009c29e9815f32d5c1f4750bcc4bc30b) already exists.
2022-08-30 23:20:24.030 CEST [2528] STATEMENT:  INSERT INTO "oc_filecache" ("mimepart", "mimetype", "mtime", "size", "etag", "storage_mtime", "permissions", "name", "parent", "checksum", "path_hash", "path", "storage") VALUES($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13)
2022-08-30 23:20:50.330 CEST [2536] ERROR:  duplicate key value violates unique constraint "fs_storage_path_hash"
2022-08-30 23:20:50.330 CEST [2536] DETAIL:  Key (storage, path_hash)=(22, 3fe7adf03a9957a580ce3abfa226eb5c) already exists.
2022-08-30 23:20:50.330 CEST [2536] STATEMENT:  INSERT INTO "oc_filecache" ("mimepart", "mimetype", "mtime", "size", "etag", "storage_mtime", "permissions", "name", "parent", "checksum", "path_hash", "path", "storage") VALUES($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13)
2022-08-31 00:15:02.780 CEST [3291] ERROR:  duplicate key value violates unique constraint "fs_storage_path_hash"
2022-08-31 00:15:02.780 CEST [3291] DETAIL:  Key (storage, path_hash)=(1, 6b6b9afedd635268f0775b0b1f6d25ee) already exists.
2022-08-31 00:15:02.780 CEST [3291] STATEMENT:  INSERT INTO "oc_filecache" ("mimepart", "mimetype", "mtime", "size", "etag", "storage_mtime", "permissions", "name", "parent", "checksum", "path_hash", "path", "storage") VALUES($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13)

PostgreSQL Database directory appears to contain a database; Skipping initialization


PostgreSQL Database directory appears to contain a database; Skipping initialization

 

Link to comment
  • 4 weeks later...
On 8/31/2022 at 12:32 AM, backfmar said:

I have changed the Path in the template, but still gets this errors in the Logs, may someone could help?

 

 

2022-08-30 02:02:54.002 CEST [32368] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 02:02:54.002 CEST [32368] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 03:51:48.432 CEST [5383] ERROR:  duplicate key value violates unique constraint "fs_storage_path_hash"
2022-08-30 03:51:48.432 CEST [5383] DETAIL:  Key (storage, path_hash)=(22, 1112d78c0dc102e1c14400917b3ee4b7) already exists.
2022-08-30 03:51:48.432 CEST [5383] STATEMENT:  INSERT INTO "oc_filecache" ("mimepart", "mimetype", "mtime", "size", "etag", "storage_mtime", "permissions", "name", "parent", "checksum", "path_hash", "path", "storage") VALUES($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13)
2022-08-30 06:25:50.393 CEST [18511] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 06:25:50.393 CEST [18511] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 06:25:50.393 CEST [18511] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 06:26:13.339 CEST [18543] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 06:26:13.339 CEST [18543] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 06:26:13.339 CEST [18543] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 08:04:18.102 CEST [21370] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 08:04:18.102 CEST [21370] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 08:04:18.102 CEST [21370] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 08:05:43.673 CEST [21466] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 08:05:43.673 CEST [21466] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 08:05:43.673 CEST [21466] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 08:06:08.112 CEST [21511] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 08:06:08.112 CEST [21511] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 08:06:08.112 CEST [21511] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 17:36:49.465 CEST [23330] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 17:36:49.465 CEST [23330] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 17:36:49.465 CEST [23330] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 17:42:16.024 CEST [23459] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 17:42:16.024 CEST [23459] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 17:42:16.024 CEST [23459] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 17:42:41.089 CEST [23497] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 17:42:41.089 CEST [23497] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 17:42:41.089 CEST [23497] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 18:17:03.999 CEST [1] LOG:  received fast shutdown request
2022-08-30 18:17:04.015 CEST [1] LOG:  aborting any active transactions
2022-08-30 18:17:04.017 CEST [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2022-08-30 18:17:04.021 CEST [27] LOG:  shutting down
2022-08-30 18:17:04.228 CEST [1] LOG:  database system is shut down
2022-08-30 18:17:08.356 CEST [1] LOG:  starting PostgreSQL 14.5 (Debian 14.5-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2022-08-30 18:17:08.357 CEST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-08-30 18:17:08.357 CEST [1] LOG:  listening on IPv6 address "::", port 5432
2022-08-30 18:17:08.436 CEST [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-08-30 18:17:08.460 CEST [26] LOG:  database system was shut down at 2022-08-30 18:17:04 CEST
2022-08-30 18:17:08.473 CEST [1] LOG:  database system is ready to accept connections
2022-08-30 18:40:25.112 CEST [599] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 18:40:25.112 CEST [599] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 18:40:25.112 CEST [599] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 18:41:56.383 CEST [711] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 18:41:56.383 CEST [711] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 18:41:56.383 CEST [711] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 18:42:21.617 CEST [742] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 18:42:21.617 CEST [742] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 18:42:21.617 CEST [742] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 19:04:32.902 CEST [1659] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 19:04:32.902 CEST [1659] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 19:04:32.902 CEST [1659] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 19:06:13.354 CEST [1776] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 19:06:13.354 CEST [1776] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 19:06:13.354 CEST [1776] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 19:06:38.615 CEST [1806] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 19:06:38.615 CEST [1806] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 19:06:38.615 CEST [1806] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 19:11:24.655 CEST [2026] ERROR:  duplicate key value violates unique constraint "oc_filecache_extended_pkey"
2022-08-30 19:11:24.655 CEST [2026] DETAIL:  Key (fileid)=(1323025) already exists.
2022-08-30 19:11:24.655 CEST [2026] STATEMENT:  INSERT INTO "oc_filecache_extended" ("fileid", "upload_time") VALUES($1, $2)
2022-08-30 19:31:18.384 CEST [1] LOG:  received fast shutdown request
2022-08-30 19:31:18.390 CEST [1] LOG:  aborting any active transactions
2022-08-30 19:31:18.394 CEST [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2022-08-30 19:31:18.394 CEST [27] LOG:  shutting down
2022-08-30 19:31:18.646 CEST [1] LOG:  database system is shut down
2022-08-30 19:31:22.796 CEST [1] LOG:  starting PostgreSQL 14.5 (Debian 14.5-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2022-08-30 19:31:22.796 CEST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-08-30 19:31:22.796 CEST [1] LOG:  listening on IPv6 address "::", port 5432
2022-08-30 19:31:22.864 CEST [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-08-30 19:31:22.879 CEST [26] LOG:  database system was shut down at 2022-08-30 19:31:18 CEST
2022-08-30 19:31:22.888 CEST [1] LOG:  database system is ready to accept connections
2022-08-30 23:20:14.102 CEST [2521] ERROR:  duplicate key value violates unique constraint "fs_storage_path_hash"
2022-08-30 23:20:14.102 CEST [2521] DETAIL:  Key (storage, path_hash)=(22, fa5878d7e8273870e0757d725906ffec) already exists.
2022-08-30 23:20:14.102 CEST [2521] STATEMENT:  INSERT INTO "oc_filecache" ("mimepart", "mimetype", "mtime", "size", "etag", "storage_mtime", "permissions", "name", "parent", "checksum", "path_hash", "path", "storage") VALUES($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13)
2022-08-30 23:20:24.030 CEST [2528] ERROR:  duplicate key value violates unique constraint "fs_storage_path_hash"
2022-08-30 23:20:24.030 CEST [2528] DETAIL:  Key (storage, path_hash)=(22, 009c29e9815f32d5c1f4750bcc4bc30b) already exists.
2022-08-30 23:20:24.030 CEST [2528] STATEMENT:  INSERT INTO "oc_filecache" ("mimepart", "mimetype", "mtime", "size", "etag", "storage_mtime", "permissions", "name", "parent", "checksum", "path_hash", "path", "storage") VALUES($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13)
2022-08-30 23:20:50.330 CEST [2536] ERROR:  duplicate key value violates unique constraint "fs_storage_path_hash"
2022-08-30 23:20:50.330 CEST [2536] DETAIL:  Key (storage, path_hash)=(22, 3fe7adf03a9957a580ce3abfa226eb5c) already exists.
2022-08-30 23:20:50.330 CEST [2536] STATEMENT:  INSERT INTO "oc_filecache" ("mimepart", "mimetype", "mtime", "size", "etag", "storage_mtime", "permissions", "name", "parent", "checksum", "path_hash", "path", "storage") VALUES($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13)
2022-08-31 00:15:02.780 CEST [3291] ERROR:  duplicate key value violates unique constraint "fs_storage_path_hash"
2022-08-31 00:15:02.780 CEST [3291] DETAIL:  Key (storage, path_hash)=(1, 6b6b9afedd635268f0775b0b1f6d25ee) already exists.
2022-08-31 00:15:02.780 CEST [3291] STATEMENT:  INSERT INTO "oc_filecache" ("mimepart", "mimetype", "mtime", "size", "etag", "storage_mtime", "permissions", "name", "parent", "checksum", "path_hash", "path", "storage") VALUES($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13)

PostgreSQL Database directory appears to contain a database; Skipping initialization


PostgreSQL Database directory appears to contain a database; Skipping initialization

 

 

Anyone? Still get this Errors :/

Link to comment
  • 1 month later...
Just now, CryPt00n said:

Hi, i´m using Postgresql version 11 for nextcloud and want to upgrade to Version 14. already tried pg_dumpall and psql commands to migrate but nextcloud is not working then. Database got imported to the new container. Any ideas? What is the recommended way?

What are the errors you are seeing?

Link to comment

Not quite sure if i restored it the right way

 

Used for Backup

pg_dumpall -U nextcloud -s > bak.sql

 

Used for restore

psql -U nextcloud postgres < bak.sql

 

Set up the docker with same username/password and port configured.

 

 

Receive this in logs then

2022-11-17 22:15:13.463 CET [274] FATAL:  password authentication failed for user "oc_admin"
2022-11-17 22:15:13.463 CET [274] DETAIL:  User "oc_admin" does not have a valid SCRAM secret.
        Connection matched pg_hba.conf line 100: "host all all all scram-sha-256"

 

Link to comment
10 hours ago, CryPt00n said:

Not quite sure if i restored it the right way

 

Used for Backup

pg_dumpall -U nextcloud -s > bak.sql

 

Used for restore

psql -U nextcloud postgres < bak.sql

 

Set up the docker with same username/password and port configured.

 

 

Receive this in logs then

2022-11-17 22:15:13.463 CET [274] FATAL:  password authentication failed for user "oc_admin"
2022-11-17 22:15:13.463 CET [274] DETAIL:  User "oc_admin" does not have a valid SCRAM secret.
        Connection matched pg_hba.conf line 100: "host all all all scram-sha-256"

 

It's a password failure error. Have you tried resetting the password?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.