[Bug] on openEuler 22.03 (LTS-SP4) system, cloudberrydb-1.6.0 install with source code ,error occured when gpinitsystem
@Baowen648 ci sta già lavorando.
Dal 9/9/2024.
- Lingua principale
- C
- Stelle
- 1.4k
- Fork
- 248
- Merge medio
- 4g 3h
- PR unite (30g)
- 39
Descrizione
Cloudberry Database version
cloudberrydb-1.6.0
What happened
20240906:18:23:28:112430 gpinitsystem:cloudberrydb1:gpadmin-[INFO]:-No errors generated from parallel processes
20240906:18:23:28:112430 gpinitsystem:cloudberrydb1:gpadmin-[INFO]:-Restarting the CloudberryDB instance in production mode
Traceback (most recent call last):
File "/usr/local/cloudberrydb/bin/gpstop", line 9, in
from gppylib.mainUtils import *
File "/usr/local/cloudberrydb/lib/python/gppylib/mainUtils.py", line 31, in
from gppylib.commands import gp, unix
File "/usr/local/cloudberrydb/lib/python/gppylib/commands/gp.py", line 22, in
from gppylib.db import dbconn
File "/usr/local/cloudberrydb/lib/python/gppylib/db/dbconn.py", line 15, in
from gppylib.commands.unix import UserId
File "/usr/local/cloudberrydb/lib/python/gppylib/commands/unix.py", line 17, in
from gppylib.commands.base import *
File "/usr/local/cloudberrydb/lib/python/gppylib/commands/base.py", line 32, in
from pg import DB
File "/usr/local/lib/python3.9/site-packages/pg/init.py", line 3
async,
^
SyntaxError: invalid syntax
20240906:18:23:28:112430 gpinitsystem:cloudberrydb1:gpadmin-[FATAL]:-Error from CloudberryDB instance shutdown, check log files Script Exiting!
What you think should happen instead
No response
How to reproduce
The err is the same as 1.5.4 with rpm/source . now 1.6.0rpm is repaired,but 1.6.0 install with source code is still same error
Operating System
openEuler 22.03 (LTS-SP4)
Anything else
No response
Are you willing to submit PR?
- Yes, I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct.
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.