Troubleshoot Your Installation
Unable to open up UI
After your installation, if you are not able to bring up Login page and you see this kind of error in your browser, then it is likely due to Selinux setting.
Because we put our software in the /opt path, and Selinux policies does not allow to run web app from anything that it is not /var/www.
Since we don't want to change system policies on the customer servers, we set it just temporarily and give user a warning to change if he want permanent setting.
When this issue occurs, you will see the following error in nginx.log file:
You can use the getenforce command to see your SELINUX mode:
How to set your system to Permissive Mode
Use the following procedure to permanently change SELinux mode to permissive. When SELinux is running in permissive mode, SELinux policy is not enforced. The system remains operational and SELinux does not deny any operations but only logs AVC messages, which can be then used for troubleshooting, debugging, and SELinux policy improvements. Each AVC is logged only once in this case.
Prerequisites
The
selinux-policy-targeted
,libselinux-utils
, andpolicycoreutils
packages are installed on your system.The
selinux=0
orenforcing=0
kernel parameters are not used.
Procedure
Open the
/etc/selinux/config
file in a text editor of your choice, for example:Configure the
SELINUX=permissive
option:Restart the system:
Verification
After the system restarts, confirm that the getenforce
command returns Permissive
:
License Module Initialization Error
If you are seeing the following error in /opt/denovov6/dnl_softswitch/log/dnl_softswitch.log, you should reset your license IP here.
Unable to open Web Portal
When you do "rpm update", the nginx config may get overwritten.
In this case, you can rerun the following command to reset the correct nginx config:
API is not responding due to Postgres is down
If API is no responding, then you may also want to check if Postgres is running:
If it is showing down, then you can start with the following command. After you restart Postgresql, you can also restart dnl_api:
Last updated