vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-20 12:37:04 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[GH-ISSUE #62] [Bug]: initdb: error: program "postgres" is needed by initdb but was not found in the same directory as "/usr/lib/postgresql/16/bin/initdb" #32

New Issue
Closed
opened 2026-06-06 22:08:08 -04:00 by yindo · 2 comments
yindo commented 2026-06-06 22:08:08 -04:00
Owner
Copy Link
Copy Source

Originally created by @TianT1209 on GitHub (Oct 10, 2025).
Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/62

Originally assigned to: @asdek on GitHub.

Affected Component

Core Services (Frontend UI/Backend API)

Describe the bug

When use docker-compose up -d, the container of the pgvector seems hava some mistakes.

Image

Steps to Reproduce

  1. docker-compose up -d
  2. docker logs xxx

System Configuration

no special setup

Logs and Artifacts

No response

Screenshots or Recordings

No response

Verification

  • I have checked that this issue hasn't been already reported
  • I have provided all relevant configuration files (with sensitive data removed)
  • I have included relevant logs and error messages
  • I am running the latest version of PentAGI
Originally created by @TianT1209 on GitHub (Oct 10, 2025). Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/62 Originally assigned to: @asdek on GitHub. ### Affected Component Core Services (Frontend UI/Backend API) ### Describe the bug When use docker-compose up -d, the container of the pgvector seems hava some mistakes. <img width="1350" height="284" alt="Image" src="https://github.com/user-attachments/assets/0038a9d1-0dc8-4a49-809f-5698185f60cb" /> ### Steps to Reproduce 1. docker-compose up -d 2. docker logs xxx ### System Configuration no special setup ### Logs and Artifacts _No response_ ### Screenshots or Recordings _No response_ ### Verification - [ ] I have checked that this issue hasn't been already reported - [ ] I have provided all relevant configuration files (with sensitive data removed) - [ ] I have included relevant logs and error messages - [ ] I am running the latest version of PentAGI
yindo added the bug label 2026-06-06 22:08:08 -04:00
yindo closed this issue 2026-06-06 22:08:08 -04:00
yindo commented 2026-06-06 22:08:09 -04:00
Author
Owner
Copy Link
Copy Source

@asdek commented on GitHub (Oct 18, 2025):

hello @TianT1209

thank you for reporting this issue. Based on the logs you provided, this appears to be a PostgreSQL/pgvector initialization problem rather than just a resource issue.

the errors show:

  • postgres is needed by initdb but was not found
  • Cannot allocate memory
  • popen failure

this could be caused by several factors and steps to fix:

  1. clean restart the database:

    docker-compose down -v
docker-compose up -d

  2. check system resources:
    please verify system requirements from README.

  3. check Docker resources:
    ensure Docker has sufficient memory allocated (at least 4GB recommended).

please provide additional information:

  • what OS and CPU architecture are you using?
  • what are your server hardware specifications (RAM, CPU)?
  • docker version: docker --version
  • docker Compose version: docker-compose --version
  • full logs from pgvector container: docker logs pgvector

let me know the results of the clean restart and your system information

<!-- gh-comment-id:3418146961 --> @asdek commented on GitHub (Oct 18, 2025): hello @TianT1209 thank you for reporting this issue. Based on the logs you provided, this appears to be a PostgreSQL/pgvector initialization problem rather than just a resource issue. the errors show: - `postgres is needed by initdb but was not found` - `Cannot allocate memory` - `popen failure` this could be caused by several factors and steps to fix: 1. **clean restart the database:** ```bash docker-compose down -v docker-compose up -d ``` 2. **check system resources:** please verify [system requirements from README](https://github.com/vxcontrol/pentagi?tab=readme-ov-file#system-requirements). 3. **check Docker resources:** ensure Docker has sufficient memory allocated (at least 4GB recommended). **please provide additional information:** - what OS and CPU architecture are you using? - what are your server hardware specifications (RAM, CPU)? - docker version: `docker --version` - docker Compose version: `docker-compose --version` - full logs from pgvector container: `docker logs pgvector` let me know the results of the clean restart and your system information
yindo commented 2026-06-06 22:08:09 -04:00
Author
Owner
Copy Link
Copy Source

@asdek commented on GitHub (Oct 23, 2025):

@TianT1209
I haven't received a response from you, issue was closed

<!-- gh-comment-id:3437868514 --> @asdek commented on GitHub (Oct 23, 2025): @TianT1209 I haven't received a response from you, issue was closed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#32
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?