-
Notifications
You must be signed in to change notification settings - Fork 90
Cached server path fails to find PID on Unix #142
Comments
|
I do have the same issue. Did you guys found some workaround? Or the only option is to create pull request with fix? |
No I didn't. Tried to use the System setting |
We have just found the same issue in our setup. Caching the Postgres directory worked fine on our Macs (Sierra and High Sierra) but failed when we pushed our project to Jenkins (running Debian). Turning off the cache fixed it for us. (Obviously this isn’t ideal... but it works for now.) |
I'm getting the same error also without the cache, i.e. new EmbeddedPostgres(Version.V10_3).start(
EmbeddedPostgres.defaultRuntimeConfig(), "127.0.0.1", 5432,
"boot", "boot", "boot", Collections.emptyList());
|
I have the same issue with / without cache on an Ubuntu |
142: Cached server path fails to find PID on Unix Task-Url: yandex-qatools#142
I've noticed this issue, but I found it to be a postgres process that had been left running. You can validate this by either looking for the process issuing this command in linux:
Or try and find the running pid file in the same general area as the one that had been reported missing. For example (using your error above):
if you get a result not in the directory that's reported in the exception, then you have a rouge process. |
Having the same issue, is there a solution? java.io.FileNotFoundException: File '/tmp/postgresql-embed-d42a05e0-390c-47ff-ae4f-eb9a16909b83/db-content-cecf683a-033b-4b22-9393-db2dd7f798d4/postmaster.pid' does not exist |
The same error... |
I have used the embedded Postgres fine for a long time with the default temporary paths.
When I tried to switch to a cached server path it worked fine on OSX. But when I deployed the code to a unix machine it hang on the second subsequent call with the same path argument and could not find the postmaster.pid. This happens on the Ubuntu 16, 18 and CentOS 7.5
I have created a small test class to demo the behavior:
https://github.com/mdoering/pgembed-test
While debugging I noticed that the pid files created by the embedded postgres are kept in the bin folder of the postgres executables. The postmaster.pid file it is looking for when hanging is supposed to live in the data folder though. Is that expected?
The text was updated successfully, but these errors were encountered: