General
cancel
Showing results for 
Search instead for 
Did you mean: 

Not able to configure SFM in Hpux11iv3

 
Joshy PJ
Occasional Advisor

Not able to configure SFM in Hpux11iv3

We are not able to configure ProviderSvcsCore @Hpux11iv3, root cause is not able to start postgress DB because of TCP/IP socket issue. Error logs files are pasted below. Any help is much appreciated.

 

[root@test SD2./root]# swlist -l fileset -a state | grep -vE "\#|configured"

 

  ProviderSvcsCore.PSB_CER                                     installed

  RAIDSA-PROVIDER.RAIDSA-PROV-RUN               installed

  SAS-PROVIDER.SAS-PROVIDER-RUN                 installed

  SFM-CORE.EVWEB_COREIA                         installed

  SFM-CORE.SFM_PRO_IA                           installed

  WBEMP-FCP.FCP-**bleep**-RUN                         installed

  WBEMP-Storage.STORAGE-PROV-RUN                installed

 

 

cat /var/opt/psb/log/install.log

 

[2014-10-21 20:50:58 EDT] ProviderServicesBase configure begins...

*********************************************************************************************

Moving to trust mode in Re-installation/Upgrade case.

Postmaster is not running ...

Postmaster successfully started

Postmaster connection is available. Checking connection health.

[Postgres connection error] psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.10864"?

Starting to configure CER DB

Stopping cimserver

PGS10019: CIM server is stopped.

Creating CER database

createdb: could not connect to database postgres: could not connect to server: No such file or directory

        Is the server running locally and accepting

        connections on Unix domain socket "/tmp/.s.PGSQL.10864"?

Command: createdb failed for CER DB

Starting cimserver

Failed to change the password for EMT user for CER database.

Failed to create the CER database.

CER configure failed. Revert Back to MD-5 mode.

Moving to md5 mode.

Postmaster is not running ...

Postmaster successfully started

 

We tried DB creation manually & not able to start the same because of TCP/IP socket issue

 

[root@test SD2./db]#  /sbin/init.d/psbdb start

Initializing database. . .

The files belonging to this database system will be owned by user "sfmdb".

This user must also own the server process.

 

The database cluster will be initialized with locale C.

The default database encoding has accordingly been set to SQL_ASCII.

The default text search configuration will be set to "english".

 

fixing permissions on existing directory /var/opt/psb/db/pgsql ... ok

creating subdirectories ... ok

selecting default max_connections ... 100

selecting default shared_buffers ... 32MB

creating configuration files ... ok

creating template1 database in /var/opt/psb/db/pgsql/base/1 ... ok

initializing pg_authid ... ok

initializing dependencies ... ok

creating system views ... ok

loading system objects' descriptions ... ok

creating conversions ... ok

creating dictionaries ... ok

setting privileges on built-in objects ... ok

creating information schema ... ok

vacuuming database template1 ... ok

copying template1 to template0 ... ok

copying template1 to postgres ... ok

 

WARNING: enabling "trust" authentication for local connections

You can change this by editing pg_hba.conf or using the -A option the

next time you run initdb.

 

  1. You can now start the database server using:

 

    /opt/psb/db/pgsql/bin/postgres -D /var/opt/psb/db/pgsql

or

    /opt/psb/db/pgsql/bin/pg_ctl -D /var/opt/psb/db/pgsql -l logfile start

 

 

[sfmdb@test SD2./tmp]$ id

uid=104(sfmdb) gid=20(users)

[sfmdb@test SD2./tmp]$     /opt/psb/db/pgsql/bin/postgres -D /var/opt/psb/db/pgsql

<%2014-10-21 21:38:06 EDT>FATAL:  could not create any TCP/IP sockets

[sfmdb@test SD2./tmp]$

 

1 REPLY 1
GregSB
Occasional Advisor

Re: Not able to configure SFM in Hpux11iv3

Hello,

 

I would start by going through the complete /var/adm/sw/swagent.log swinstall session information from when SFM-Core and the other "installed" products were installed to insure that no filesets were excluded because of missing dependencies or corequisites.  

 

HPSC support document mmr_kc-0109038  (http://h20565.www2.hp.com/hpsc/doc/public/display?calledBy=Search_Result&docId=mmr_kc-0109038&docLocale=en_US) contains a procedure, which can be used to remove System Fault Mananagement (SFM), ProviderSvcsCore (PSB), and the other WBEM providers contained in the WBEMMgmtBundle.   Once the products have been removed manually removing any remain SFM or PSB directories will insure that the old data or corruption is removed prior to reinstalling. 

 

If needed, the latest WBEMMgmtBundle, which contains SFM, PSB, and WBEM provider is available at:

https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=WBEMMgmtBundle

 

Hope this helps.

I work for HP
A quick resolution to technical issues for your HP Enterprise products is just a click away HP Support Center Knowledge-base
See Self Help Post for more details