Pigsty
|
What happend? (REQUIRED) Pigsty Version & OS Version grep version pigsty.yml cat /etc/os-release Pigsty Config File: Don't forget to remove sensitive information like passwords, etc... How to reproduce it?
What did you expect to happend? able to create and test parquet table successfully Monitoring Screenshots Please copy and paste any RELEVANT log output. Do not paste something like "Failed to start xxx service" Syslog: /var/log/messages (rhel) or /var/log/syslog (debian)Postgres: /pg/log/postgres/* Patroni: /pg/log/patroni/* journalctl -u |
Replies: 1 comment 3 replies
|
Could you please confirm that Installing A quick check would be: pgrep -a pgduck_server
stat -c "%A %U:%G %n" /tmp/.s.PGSQL.5332 2>&1If you already started it, please also share its startup output; it may have exited before creating the socket. |
|
I've started it per pg_lake guide: pgduck_server --cache_dir /var/cache/pg_lake It is running, the quick check command output shows: pgrep -a pgduck_server while the startup output shows: user@testnode:~$ pgduck_server --cache_dir /var/cache/pg_lake |
|
Thanks — this confirms the root cause. Please stop the current process and restart it as sudo install -d -o postgres -g postgres -m 0700 \
/var/lib/pg_lake /var/lib/pg_lake/extensions
sudo install -d -o postgres -g postgres -m 0750 /var/cache/pg_lake
sudo -u postgres -H /usr/lib/postgresql/18/bin/pgduck_server \
--duckdb_database_file_path /var/lib/pg_lake/pgduck_server.db \
--extensions_dir /var/lib/pg_lake/extensions \
--cache_dir /var/cache/pg_lakeThen verify the connection from another terminal: sudo -u postgres psql -X \
"host=/tmp port=5332 dbname=postgres connect_timeout=2" \
-c "SELECT version();"Once this succeeds, please retry the Iceberg operation. We have reproduced and verified this flow with the PIGSTY Ubuntu 24.04 / PostgreSQL 18 package. The package-specific Thanks again for the detailed information! |
|
thank you! that solved it, also in my case i add i need to delete the lock files too in /tmp/.s.PGSQL.5332 and /tmp/.s.PGSQL.5332.lock too to resolve it. |
Thanks — this confirms the root cause.
pgduck_serveris running as the OS useruser, while PostgreSQL runs aspostgres. Since the socket is0770 user:user, the PostgreSQL backend cannot access it, resulting incould not start query engine.Please stop the current process and restart it as
postgres:Then verify the conne…