Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devnet Migration Error - validating initial migration fails - must be superuser or member of pg_write_server_files #15476

Closed
2 tasks done
jrwashburn opened this issue Apr 5, 2024 · 1 comment
Assignees

Comments

@jrwashburn
Copy link

Preliminary Checks

Description

Initial Migration fails with error because user cannot write to server files.
Command:
mina-berkeley-migration-script initial --genesis-ledger /var/lib/coda/devnet.json --source-db postgres://.../devnet-archive --target-db postgres://.../devnet-archive-berkeley --blocks-bucket mina_network_block_data --blocks-batch-size 5000 --network devnet

Result:

2024-04-05 02:14:41 UTC [Info] Checkpoint target was 442000, new target would be at noncanonical slot, set target to unreachable value
2024-04-05 02:14:41 UTC [Info] Writing checkpoint file
2024-04-05 02:15:06 UTC [Info] Writing checkpoint file
2024-04-05 02:15:06 UTC [Info] No target epoch ledger hash supplied, not writing output
Running verifications for incremental migration between 'postgres://.../devnet-archive' and 'postgres://.../devnet-archive-berkeley' schemas. It may take a couple of minutes... 
[1/6] D3.1) Migrated blocks are connected  ... ✅ 
[2/6] D3.2) No orphaned nor pending blocks in migrated db  ... ✅ 
(monitor.ml.Error
 (Failure
   "Error querying db, error: Request to <postgres://.../devnet-archive-berkeley> failed: ERROR:  must be superuser or a member of the pg_write_server_files role to COPY to a file\
  \nHINT:  Anyone can COPY to stdout or from stdin. psql's \\copy command also works for anyone.\
  \n Query: \"COPY (  \\n      ( \\n        WITH user_command_ids AS\\n        ( SELECT user_command_id, block_id, status FROM blocks_user_commands\\n          INNER JOIN blocks ON id = block_id\\n          WHERE chain_status = 'canonical'\\n        )\\n        SELECT account_identifiers.id, block_id FROM user_command_ids\\n        INNER JOIN user_commands ON id = user_command_id\\n        INNER JOIN account_identifiers ON (public_key_id = receiver_id AND status = 'applied')\\n                                       OR public_key_id = fee_payer_id \\n      )\\n        UNION\\n      (\\n        WITH internal_command_ids AS\\n        ( SELECT internal_command_id, block_id FROM blocks_internal_commands\\n          INNER JOIN blocks ON id = block_id\\n          WHERE chain_status = 'canonical'\\n          AND status = 'applied'\\n        ) \\n        SELECT account_identifiers.id, block_id FROM internal_command_ids\\n        INNER JOIN internal_commands ON id = internal_command_id\\n        INNER JOIN account_identifiers ON public_key_id = receiver_id\\n      ) ORDER BY block_id, id  ) TO '/tmp/user_and_internal_cmds.csv' DELIMITER ',' CSV HEADER \".")
 ("Raised at Stdlib.failwith in file \"stdlib.ml\", line 29, characters 17-33"
  "Called from Async_kernel__Deferred0.bind.(fun) in file \"src/deferred0.ml\", line 54, characters 64-69"
  "Called from Async_kernel__Job_queue.run_job in file \"src/job_queue.ml\" (inlined), line 128, characters 2-5"
  "Called from Async_kernel__Job_queue.run_jobs in file \"src/job_queue.ml\", line 169, characters 6-47"))

Steps to Reproduce

  1. Create a user with all rights to devnet and devnet berkeley databases
  2. Run initial migration as that user
  3. Fails with error reported above.
    ...

Expected Result

Migration will complete without error.

Actual Result

ERROR: must be superuser or a member of the pg_write_server_files role to COPY to a file

Daemon version

apt list --installed | grep mina

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

mina-archive-maintenance/unknown,now 1.4.0beta2-compatible-060f0a5 amd64 [installed,upgradable to: 1.5.0devnet-stop-slot-c18c750]
mina-archive-migration/unknown,now 3.0.0devnet-tooling-6e92017 amd64 [installed,upgradable to: 3.0.0devnet-tooling-5792b50]
mina-archive/unknown,now 1.5.0devnet-stop-slot-c18c750 amd64 [installed,upgradable to: 3.0.0devnet-tooling-5792b50]
mina-devnet/unknown,now 1.5.0devnet-stop-slot-c18c750 amd64 [installed]
mina-logproc/unknown,now 3.0.0devnet-tooling-5792b50 amd64 [installed,automatic]

How frequently do you see this issue?

Rarely

What is the impact of this issue on your ability to run a node?

Low

Status

not relevant

Additional information

running with local db on same physical hardware (postgres and migration script.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants