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

postgresql container in CodeReadyWorkspace operator can't work behind proxy #418

Open
zhengxiaomei123 opened this issue Sep 2, 2021 · 1 comment
Assignees

Comments

@zhengxiaomei123
Copy link

zhengxiaomei123 commented Sep 2, 2021

The OpenShift Container Platform version:

Client Version: 4.6.6
Server Version: 4.6.8
Kubernetes Version: v1.19.0+7070803

The Red Hat CodeReady Workspaces version: 2.10.1
The image used for postgresql container : registry.redhat.io/rhel8/postgresql-96@sha256:33643fb4cafffacb277982c6098b561aa80c06210e77d2badebef405ee953e43

The log of postgresql container:

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/pgsql/data/userdata ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... Etc/UTC
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... 



pg_ctl: another server might be running; trying to start server anyway
waiting for server to start........LOG:  redirecting log output to logging collector process
HINT:  Future log output will appear in directory "pg_log".
............


cat pg_log



FATAL:  the database system is starting up
LOG:  could not send data to client: Broken pipe
FATAL:  the database system is starting up
LOG:  database system was interrupted; last known up at 2021-09-02 10:02:05 UTC
FATAL:  the database system is starting up
FATAL:  the database system is starting up
FATAL:  the database system is starting up
FATAL:  the database system is starting up
FATAL:  the database system is starting up

There is proxy configured for the container:


env:
      - name: HTTPS_PROXY
        value: 'http://ip:3128'
      - name: HTTP_PROXY
        value: 'http://ip:3128'
      - name: NO_PROXY
        value: >-
         9.0.0.0/8,.<$domain>,.cluster.local,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,172.30.0.0/16,192.168.20.0/24,localhost,api-int.<$domain>,etcd-0.<$domain>,etcd-1.<$domain>,etcd-2.<$domain>

Expect help :
let the postgresql container running. I don’t know why the pg_ctl start failed or why the postgresql server not running in this container.

@phracek
Copy link
Member

phracek commented Feb 23, 2023

@zhengxiaomei123 Hi, we are testing regularly our containers on OpenShift 4.12.3 and test are passing like can be seen here: #497 . It would be nice to provide a reproducer. We do not test containers in CRW and we do not plan it, as far as I know. Is the issue still valid on CRW? Also what kind of PostgreSQL version are you using?

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

No branches or pull requests

2 participants