pg_ctl: command not found (And how to fix it)

[heratyian]

I've noticed codespaces sometimes has issues starting postgres server. any suggestions on resolving?

 $ bin/postgres-monitor 
bin/postgres-monitor: line 4: pg_ctl: command not found

[bpurinton]

We've fixed this recently. What project is this occurring on? It may be some of your students still working on the older version of of the Full Stack course, with some deprecated projects that we'll be cleaning up.

[heratyian]

this one specifically https://github.com/melhelow/RigRadar but I've seen it in other codespaces too. any debugging tips @bpurinton ?

[bpurinton]

This student generated from the template before our fix for the issue. The easiest solution is to have them delete and create a new codespace. But that's far from ideal, because it will keep happening (infrequently, but sometimes a few times in a row 😬 )

For forks, the update can be synced from upstream (we made the update to all projects)

The lagging issues should only be from template-generated repos like this one, which were generated after our fix a few weeks ago.

Hold on, let me see if I can find / make a clean commit for you / them to follow to make the update that will prevent this on future codespaces

[melhelow]

hi bpurinton, i did delete the code space many time on the last three days, i had to change in my devontainer.json and database.yaml also i did add some files ending with .sh it worked fine after these updated however it did crashed again this afternoon

i will add you as a collobrator now

[melhelow]

[bpurinton]

@melhelow, want to give it a try? Here is the .patch file with the full diff of the changes to make:

0001-Fix-database-in-Codespaces-and-on-Render-deployment.patch

If you copy that file into this viewer: https://megatops.github.io/PatchViewer/

You'll see a diff of all the files you need to change.

Once you carefully make the change, you will need to open a fresh codespace on your repository.

You can also apply the patch directly with:

git apply /path/to/your-patch-file.patch

Directly applying the patch is a safer bet than trying to read the diff and copy manually.

[melhelow]

ok thanks im working on it now..i'll let you know

[melhelow]

its working now..thank you