Error: Http 404 Page not found

This is the most common problem that you may encounter.

To resolve this issue:

1. Verify the Domain Name System (DNS) configuration.

   Note:

   These steps apply for local DNS resolution via the hosts file. For any other DNS resolution, such as corporate DNS, follow the corresponding steps.
   The hosts configuration file is located at:

   • On Windows: C:\Windows\System32\drivers\etc\hosts
   • On Linux: /etc/hosts
   Verify if the following entry exists in the hosts configuration file of the client machine from where you are trying to connect to ASAP:

   • Local installation of Kubernetes without Oracle Cloud Infrastructure load balancer:

     Kubernetes_Cluster_Master_IP <hostname provided in the values.yaml file>

   • If Oracle Cloud Infrastructure load balancer is used:

     Load_balancer_IP  instance.project.asap. <hostname given in the values.yaml file>

   Resolve the DNS configuration.

2. Verify the browser settings and ensure that *.asap.org is added to the No proxy list, if your proxy cannot route to it.
3. Verify if the Traefik pod is running and installing or updating the Traefik Helm chart:

   kubectl -n traefik get pod
   NAME                                READY   STATUS    RESTARTS   AGE
   traefik-operator-657b5b6d59-njxwg   1/1     Running   0          128m
   

4. Verify if the Traefik service is running:

   kubectl -n traefik get svc
   NAME                         TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)                      AGE
   oci-lb-service-traefik       LoadBalancer   10.96.136.31    100.77.18.141   80:31115/TCP                 20d    <---- Is expected in OCI environment only --
   traefik-operator             NodePort       10.98.176.16    <none>          443:30443/TCP,80:30305/TCP   141m
   traefik-operator-dashboard   ClusterIP      10.103.29.101   <none>          80/TCP                       141m
   

   Note:

   If the Traefik service is not running, install or update the Traefik Helm chart.
5. Verify if the Traefik back-end systems are registered, by using one of the following options:
   • Run the following commands to check if your project name space is being monitored by Traefik. The absence of your project name space means that your managed server back-end systems are not registered with Traefik.

     $ cd $ASAP_CNTK
     $ source scripts/common-utils.sh
     $ find_namespace_list 'namespaces' traefik traefik-operator
     "traefik","project_1", "project_2"
     

   • Verify the Traefik Dashboard and add the following DNS entry in your hosts configuration file:

     Kubernetes_Access_IP traefik.asap.org

     Add the same entry regardless of whether you are using Oracle Cloud Infrastructure load balancer or not. Navigate to: http://traefik.asap.org:30305/dashboard/ and check the back-end systems that are registered. If you cannot find your project name space, install or upgrade the Traefik Helm chart. See "Installing the Traefik Container Image" for more information.

Reloading Instance Backend Systems

If your instance's ingress is present, yet Traefik does not recognize the URLs of your instance, try to unregister and register your project name space again. You can do this by using the unregister-namespace.sh and register-namespace.sh scripts in the toolkit.

Debugging Traefik Access Logs

To increase the log level and debug Traefik access logs:

1. Run the following command:

   $ helm upgrade traefik-operator traefik/traefik   --version 9.11.0  --namespace traefik   --reuse-values   --set logs.access.enabled=true

   A new instance of the Traefik pod is created automatically.
2. Look for the pod that is created most recently:

   $ kubectl get po -n traefik
   NAME                                  READY     STATUS     RESTARTS   AGE
   traefik-operator-pod_name   1/1       Running   0          0          5s
    
   $ kubectl -n traefik logs -f traefik-operator-pod_name

3. Enabling access logs generates large amounts of information in the logs. After debugging is complete, disable access logging by running the following command:

   $ helm upgrade traefik-operator traefik/traefik   --version 9.11.0  --namespace traefik   --reuse-values   --set logs.access.enabled=false

Cleaning Up Traefik

helm uninstall traefik-operator -n traefik

Cleaning up of Traefik does not impact actively running ASAP instances. However, they cannot be accessed during that time. Once the Traefik chart is re-installed with all the monitored name spaces and registered as Traefik back-end systems successfully, ASAP instances can be accessed again.

Setting up Logs

As described earlier in this guide, ASAP and WebLogic logs can be stored in the individual pods or in a location provided via a Kubernetes Persistent Volume. The PV approach is strongly recommended, both to allow for proper preservation of logs (as pods are ephemeral) and to avoid straining the in-pod storage in Kubernetes.

Within the pod, logs are available at: /u01/oracle/user_projects/domains/domain/servers/AdminServer/logs.

ASAP logs: /scratch/oracle/asap/DATA/logs/

When a PV is configured, logs are available at the following path starting from the root of the PV storage:

project-instance/logs.

The ASAP Email plugin is currently not supported. Users who require this capability can create their own plugin for this purpose.