The portal is where you configure your OP5 Appliance System. This includes configuring its IP address, NTP server, email relay, and other values.
Sometimes the login can fail, for a multitude of reasons. In this section we will show you some of the problems we have encountered during the lifetime of the application.
The Configure System feature in the Portal requires the user to login using the root password. This login might stop working, although the password seems right. Please follow the steps below to troubleshoot this problem:
Is the config daemon running?
Is your system set up with a locale other than C, or not even an English locale? Running the following from the shell:
Should lead to one of the following outputs:
Simply running the
'locale'command will also show a value. However that value may differ from the environment of the op5config process if the values had changed after bootup. The running process would have inherited the environment set in '/etc/sysconfig/i18n'.
LANG values other than English, such as 'de_DE.utf8' or 'sv_SE.utf8', need to be changed. One solution is to make sure LANG is set to C in '/etc/sysconfig/i18n' and reboot the server. Red Hat provides full details on setting the value successfully.
Is the Unix socket configured with the correct permissions?
Is the Apache user able to talk to the Unix socket?
Does the op5config authentication module accept the root password?
These commands can help in cases where the wrong password is entered or the password fails for some other reason:
The op5config authentication module, which runs as root, drops to the Apache user and tries to su to root using the supplied password. Is this procedure working?
Some users have previously changed the system's PAM configuration, which prohibits this user change from Apache to root. To check the PAM configuration, you can verify the files located in 'etc/pam.d/':
This output will only include PAM authentication files with anomalies. In case a file in the directory does not belong to any installed RPM package, a line similar to the last line above will be displayed. The verification codes, found in man 8 rpm, show that the valid auth files above each have a symlink that fails to resolve. This is actually normal:
S file Size differs M
Mode differs (includes permissions and file type)
5 digest (formerly MD5 sum) differs D Device major/minor number mismatch L readLink(2) path mismatch U User ownership differs G Group ownership differs T mTime differs P caPabilities differ