Uploaded image for project: 'Network Controller'
  1. Network Controller
  2. SDNC-1385

[SDNC-WEB] container in crashloop back due to empty env TOPOURL

XMLWordPrintable

      In case of empty TOPOURL https_site.conf is not correctly parsed.

      TOPOURL is not correctly replaced

       

      07:56:37.29
      07:56:37.29 Welcome to the Bitnami nginx container
      07:56:37.30 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-nginx
      07:56:37.30 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-nginx/issues
      07:56:37.30 Send us your feedback at containers@bitnami.com
      07:56:37.31

      transportPCE forwarding disabled
      topology api forwarding disabled
      tile server forwarding disabled
      starting sdnc-web
      =================
      WEBPROTOCOL : HTTPS
      WEBPORT : 8443
      SDNRPROTOCOL : https
      SDNRHOST : sdnc.onap
      SDNRPORT : 8443
      TRPCEURL :
      TOPOURL :
      TILEURL :
      SSL_CERT_DIR : /opt/app/osaaf/local/certs
      SSL_CERTIFICATE: cert.pem (missing)
      SSL_CERTIFICATE_KEY: key.pem (missing)

      07:56:37.41 INFO ==> ** Starting NGINX **
      2020/10/19 07:56:37 [warn] 29#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /opt/bitnami/nginx/conf/nginx.conf:2
      nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /opt/bitnami/nginx/conf/nginx.conf:2
      2020/10/19 07:56:37 [emerg] 29#0: invalid URL prefix in /opt/bitnami/nginx/conf/server_blocks/https_site.conf:83
      nginx: [emerg] invalid URL prefix in /opt/bitnami/nginx/conf/server_blocks/https_site.conf:83

            pendurty Ravi Pendurty
            demskeq8 Alexander Dehn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: