Direkt zum Hauptbereich

How to get rid of "ghost-servers" in your WebSEAL Server list?

Imagine some funny guys installed some weird servers or anything connecting to your policy director and you do not know why and who and they are long gone and you assume that the servers have no purpose anymore. Or you have an old Web Portal Manager (amwpm) installation, but the server where it was installed is long gone.

So, how to get rid of those servers in your list?

pdadmin sec_master> server list
si2tty-hst1116.dada.com
amwpm-hst2128
hirsch.emea.dadacorp.net-localhost

# touch /tmp/null.conf

# svrsslcfg -unconfig -f /tmp/null.conf -n amwpm -h hst2128 -P ******* -A sec_master
Unconfiguration of application "amwpm" for host "hst2128" is in progress.
This might take several minutes.
SSL unconfiguration for application "amwpm" has completed successfully.


# svrsslcfg -unconfig -f /tmp/null.conf -n si2tty -h hst1116.dada.com -P ******* -A sec_master
Unconfiguration of application "si2tam" for host "hst1116.dada.com" is in progress.
This might take several minutes.
SSL unconfiguration for application "si2tty" has completed successfully.

# svrsslcfg -unconfig -f /tmp/null.conf -n hirsch.emea.dadacorp.net -h localhost -P ******* -A sec_master
Unconfiguration of application "hirsch.emea.dadacorp.net" for host "localhost" is in progress.
This might take several minutes.
SSL unconfiguration for application "hirsch.emea.dadacorp.net" has completed successfully.

Kommentare

Beliebte Posts aus diesem Blog

How to delete WebSEAL servers which have not been configured correctly.

Problem: The WebSEAL server list in the pdadmin: pdadmin> server list shows the server, but it does not exist anymore, i.e. because the host has been disassembled without unconfiguring the WebSEAL instance. Solution: 1.) Delete the instance in the LDAP under: SecAuthority=Default - cn=securitygroup - cn=webseal-servers - cn=secmgrd-servers 2.) Configure the instance again, which will lead to an error, because it seems to be installed already. Configuring WebSEAL instance 'DO-06'...HPDMG0453E A server with the same name already exists.DPWCF0473E The WebSEAL instance 'DO-06' failed to configure. 3.) Unconfigure the instance, which will show errors, but remove the instance totally. # amwebcfg -action unconfig -inst_name DO-06 -admin_id sec_master -admin_pwd ********* Unconfiguring WebSEAL instance 'DO-06'... 2008-10-28-15:30:10.158+01:00I----- 0x389D51F2 amwebcfg ERROR wcf Error WebCfgAdminApi.cpp 84 0x002198d0 DPWCF0498E The user 'DO-06-webseald/srv1252...

Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc)

Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc) pdadmin sec_master> user create dg1234 uid=dg1234,cn=team1,cn=users,o=company lala lala ********** Could not perform the administration request Error: HPDMG0764E An internal error has occurred. (status 0x14c012fc) Description: After the upgrade from Policy Director (policy server) V5.1 to V6.0 the errors above occured when trying to write to the registry. Solution: The task of updating the ldap schema did not work well for some reason. After doing it again the errors did not occur again: # ivrgy_tool -d -h ldap_host -p port -D ldap_admin -w pwd schema