You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/01/26 11:20:13 UTC

[GitHub] [superset] pedro93 opened a new issue #18172: [Kubernetes] Superset worker /bin/sh: 1: celery: not found

pedro93 opened a new issue #18172:
URL: https://github.com/apache/superset/issues/18172


   Superset worker fails to start using superset oficial helm charts with apache/superset:1.4.0 docker image.
   This is the log of the worker pod:
   ```
   ▶ kubectl -n dc-superset logs superset-worker-5756d5d664-k29lv
   Collecting psycopg2-binary==2.9.1
     Downloading psycopg2_binary-2.9.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.4 MB)
   Requirement already satisfied: redis==3.5.3 in /usr/local/lib/python3.8/site-packages (3.5.3)
   Installing collected packages: psycopg2-binary
     Attempting uninstall: psycopg2-binary
       Found existing installation: psycopg2-binary 2.8.5
       Uninstalling psycopg2-binary-2.8.5:
         Successfully uninstalled psycopg2-binary-2.8.5
   Successfully installed psycopg2-binary-2.9.1
   WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
   WARNING: You are using pip version 21.2.4; however, version 21.3.1 is available.
   You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
   /bin/sh: 1: celery: not found
   ```
   
   #### How to reproduce the bug
   Deploy official helm chart (v0.5.4) with the following values.yaml:
   ```
   superset:
     enabled: true
     image:
       repository: apache/superset
       tag: 1.4.0
   
     supersetNode:
       command:
         - "/bin/bash"
         - "-c"
         - "{{ .Values.configMountPath }}/superset_bootstrap.sh; /usr/bin/run-server.sh"
      
   # For some reason the apache docker image does not include the script it tries to run...
     extraVolumes:
       - name: custom-config
         configMap:
           name: superset-startup-config
           defaultMode: 0777
           items:
             - key: run-server.sh
               path: run-server.sh
   
     extraVolumeMounts:
       - name: custom-config
         mountPath: /usr/bin
   
     postgresql:
       # Create postgres locally for development purposes only.
       enabled: true
   ```
   
   And this template:
   ```apiVersion: v1
   kind: ConfigMap
   metadata:
     name: superset-startup-config
     labels:
       release: "{{ .Release.Name }}"
       heritage: "{{ .Release.Service }}"
   data:
     run-server.sh: |
       #!/usr/bin/env sh
       #
       # Licensed to the Apache Software Foundation (ASF) under one
       # or more contributor license agreements.  See the NOTICE file
       # distributed with this work for additional information
       # regarding copyright ownership.  The ASF licenses this file
       # to you under the Apache License, Version 2.0 (the
       # "License"); you may not use this file except in compliance
       # with the License.  You may obtain a copy of the License at
       #
       # http://www.apache.org/licenses/LICENSE-2.0
       #
       # Unless required by applicable law or agreed to in writing,
       # software distributed under the License is distributed on an
       # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
       # KIND, either express or implied.  See the License for the
       # specific language governing permissions and limitations
       # under the License.
       #
       HYPHEN_SYMBOL='-'
   
       gunicorn \
           --bind "${SUPERSET_BIND_ADDRESS:-0.0.0.0}:${SUPERSET_PORT:-8088}" \
           --access-logfile "${ACCESS_LOG_FILE:-$HYPHEN_SYMBOL}" \
           --error-logfile "${ERROR_LOG_FILE:-$HYPHEN_SYMBOL}" \
           --workers ${SERVER_WORKER_AMOUNT:-1} \
           --worker-class ${SERVER_WORKER_CLASS:-gthread} \
           --threads ${SERVER_THREADS_AMOUNT:-20} \
           --timeout ${GUNICORN_TIMEOUT:-60} \
           --limit-request-line ${SERVER_LIMIT_REQUEST_LINE:-0} \
           --limit-request-field_size ${SERVER_LIMIT_REQUEST_FIELD_SIZE:-0} \
           "${FLASK_APP}"
   ---
   ```
   
   Execute `kubectl get po` and see that the worker node fails.
   
   ### Expected results
   
   Superset to be deployed and stable.
   
   ### Actual results
   
   ```
   $ kubectl -n dc-superset get po
   NAME                               READY   STATUS             RESTARTS   AGE
   superset-6d9ff785d7-mczf9          0/1     CrashLoopBackOff   6          7m13s
   superset-redis-master-0            1/1     Running            0          7m13s
   superset-worker-5756d5d664-k29lv   0/1     CrashLoopBackOff   6          7m13s
   ```
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
   - [x] I have reproduced the issue with at least the latest released version of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't found one similar.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] manisha-tanwar commented on issue #18172: [Kubernetes] In Superset 1.4 Superset worker /bin/sh: 1: celery: not found

Posted by GitBox <gi...@apache.org>.
manisha-tanwar commented on issue #18172:
URL: https://github.com/apache/superset/issues/18172#issuecomment-1028971411


   If anyone faces same issue and don't want to wait till v.1.4.1
   ``` 
   extraVolumeMounts:
     - name: custom-config
       mountPath: /mnt/configs
   ```
   ```
   supersetNode:
     command:
       - "/bin/sh"
       - "-c"
       - ". {{ .Values.configMountPath }}/superset_bootstrap.sh; /mnt/configs/run-server.sh"
   ```
   
   worked fine for me. Now I can also view the exact version on UI as well which isn't the case if I use latest tag. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] pedro93 closed issue #18172: [Kubernetes] In Superset 1.4 Superset worker /bin/sh: 1: celery: not found

Posted by GitBox <gi...@apache.org>.
pedro93 closed issue #18172:
URL: https://github.com/apache/superset/issues/18172


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] manisha-tanwar commented on issue #18172: [Kubernetes] In Superset 1.4 Superset worker /bin/sh: 1: celery: not found

Posted by GitBox <gi...@apache.org>.
manisha-tanwar commented on issue #18172:
URL: https://github.com/apache/superset/issues/18172#issuecomment-1028793081


   @pedro93 did you try mounting it somewhere else instead of /usr/bin
   ```
   extraVolumeMounts:
       - name: custom-config
         mountPath: /usr/bin
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] pedro93 commented on issue #18172: [Kubernetes] In Superset 1.4 Superset worker /bin/sh: 1: celery: not found

Posted by GitBox <gi...@apache.org>.
pedro93 commented on issue #18172:
URL: https://github.com/apache/superset/issues/18172#issuecomment-1028796138


   This got fixed on a docker version after 1.4.0, I'm pointing to latest as a fix. Assuming it will be corrected in v1.4.1


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org