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

Infinite loop by "Could not run the following programs, are they installed? psql" #16

Closed
monaka opened this issue Jul 22, 2016 · 2 comments

Comments

@monaka
Copy link

monaka commented Jul 22, 2016

This is just FYI for now as I use the patched version of deis/wal-e.
But I guess other people will get similar issue.

My postgres was fallen into the infinite loop. The error message is like this.

server is still starting up
Performing an initial backup...
wal_e.main   INFO     MSG: starting WAL-E
        DETAIL: The subcommand is "wal-fetch".
        STRUCTURED: time=2016-07-22T22:25:46.577414-00 pid=8781
wal_e.operator.backup INFO     MSG: promoted prefetched wal segment
        STRUCTURED: time=2016-07-22T22:25:46.906001-00 pid=8781 action=wal-fetch key=wabs://database/wal_005
/000000050000000400000067.lzo prefix= seg=000000050000000400000067
LOG:  restored log file "000000050000000400000067" from archive
wal_e.main   INFO     MSG: starting WAL-E
        DETAIL: The subcommand is "backup-push".
        STRUCTURED: time=2016-07-22T22:25:48.787899-00 pid=8789
FATAL:  the database system is starting up
psql: FATAL:  the database system is starting up
wal_e.main   ERROR    MSG: could not run one or more external programs WAL-E depends upon
        DETAIL: Could not get a connection to the database: note that superuser access
        is required
        Could not run the following programs, are they installed? psql
        STRUCTURED: time=2016-07-22T22:25:49.501372-00 pid=8789

The similar issue was reported at the issue tracker in the upstream.
Like wal-e#234

@monaka
Copy link
Author

monaka commented Jul 22, 2016

This issue will be occurred randomly. Seems indepentent on content in log.lzo files.

The log is from same pod, same WALs.
In this time it failed at 000000050000000400000089.
Not 000000050000000400000067 (differ from previous).

wal_e.operator.backup INFO     MSG: promoted prefetched wal segment
        STRUCTURED: time=2016-07-22T23:14:37.926357-00 pid=9423 action=wal-fetch key=wabs://database/wal_005/000000050000000400000089.lzo prefix= seg=000000050000000400000089
FATAL:  the database system is starting up
LOG:  restored log file "000000050000000400000089" from archive
psql: FATAL:  the database system is starting up
wal_e.main   ERROR    MSG: could not run one or more external programs WAL-E depends upon
        DETAIL: Could not get a connection to the database: note that superuser access
        is required
        Could not run the following programs, are they installed? psql
        STRUCTURED: time=2016-07-22T23:14:38.132915-00 pid=9396

@monaka
Copy link
Author

monaka commented Jul 22, 2016

I forgot I've already reported the same issue at deis/postgres#123, sorry.
I close this and keep inspecting there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant