As an example of some issues , that i think you may find useful as the doc is for 6.3
Utility Server: Issues with utility server 6.3
Rate Content Rate this Page
Doc ID: ADMN112003
Version: 2.0
Status: Published
Published date: 02 May 2014
Updated: 23 Jul 2014
Author: dpandharkar
Body
It has been noticed that there are 3 critical bugs with Utility server 6.3. (SP1 and SP2)
Below is the description and solution. I hope it helps in resolving the issues quicker. Please relay across.
<!--[if !supportLists]-->1. <!--[endif]-->Administrator cannot login the Utility Server using admin account.
The login is working fine on the System Platform DOM0 and CDOM and all the other Virtual Machines.
On the Utility Server only Avaya services users (e.g. init) can login.
Apply PCN 1896S in order to permanently fix this login issue:
Installation instructions for the above PCN:
If no patch is installed currently and there was no patch removed either on the Utility Sever, go ahead and install the PCN 1896S -à patch 6.3.3.0.20 .
Manual workaround (temporary solution only):
On the Utility Server multiple duplicate entries get created in the following configuration file: /etc/ldap.conf
Go to the bottom of the file and remove the duplicate entries in order to fix the problem temporarly. This action would require Avaya sroot access on the Utility Server.
/etc/ldap.conf file looks like as follows if there are any extra entries:
# at present and does not support password policy control
#pam_sasl_mech DIGEST-MD5
nss_base_passwd ou=People,dc=vsp?one
nss_base_shadow ou=People,dc=vsp?one
nss_base_group ou=Group,dc=vsp?one
==============>keep the above entries and remove all the rest (below duplicate entries)
nss_base_passwd ou=People,dc=vsp?one
nss_base_shadow ou=People,dc=vsp?one
nss_base_group ou=Group,dc=vsp?one
nss_base_passwd ou=People,dc=vsp?one
nss_base_shadow ou=People,dc=vsp?one
nss_base_group ou=Group,dc=vsp?one
<!--[if !supportLists]-->2. <!--[endif]-->If Utility Services Service Pack 6.3.1.0.20 or 6.3.2.0.20 has been applied, Apache log file permissions are set incorrectly. This results
in the user not being able to view the log files in Utility Services under Utility Services AdministrationàApplication Log View
This problem is fixed with Utility Services Patch 3, 6.3.0.3.20.
util_patch_6.3.0.3.20.zip
This patch will need to be applied after application of either Utility Services Service Packs 6.3.1.0.20 or 6.3.2.0.20.
Note that even if it was applied after application of 6.3.1.0.20, it will need to be applied again after application of 6.3.2.0.20.
The patch should be removed (uninstalled) after ensuring that the Apache log file permissions have been corrected.
However, do not remove the patch file itself.
Please see PSN027002u before applying this patch if you have previously removed any Utility Services Service Pack.
<!--[if !supportLists]-->3. <!--[endif]-->If Utility Services Service Pack 6.3.1.0.20 or 6.3.2.0.20 has been applied, and then is removed, subsequent application of patches or
Service Packs will not apply correctly. It will say at the top of the page that the patch (Service Pack) has been successfully installed,
but if you examine the “Status” field of the Patch Detail page, it will show “Not Installed”. Unless the “Status” field shows Active,
the Service Pack or patch did not install cleanly and you will need to remediate with patch 6.3.0.4.20.
Use System Platform’s standard patching interface for an installed template.
Apply this patch AFTER removal of Utility Services Service Pack 1 (6.3.1.0.20) or AFTER removal of
Utility Services Service Pack 2 (6.3.2.0.20).
When you have verified that the patch has successfully been applied, please remove it, but do not remove
the patch file. You will need to reapply the patch if the existing Service Pack is removed.
This patch is not service affecting.
Use System Platform’s standard patching interface to confirm successful application of the patch.
Ensure that BOTH of the following are displayed on the Patch Detail page after application of the patch:
Patch 6.3.0.4.20 has been successfully installed
Status field of the Patch Detail page shows “Active”
Verify that you can now successfully apply another Service Pack or patch, for example, Service Pack 6.3.2.0.20. Again, you will
check for both the “Patch 632020 has been successfully installed” message at the top of the page, as well as the “Status” field
changing from “Not Installed” to “Active”.
APSS (SME)
ACSS (SME)
ACIS (UC)
