• State Suggested Answer
  • Replies replies
    4
  • Answers answer
    1
  • Subscribers subscribers
    0
  • Views views
    1189
  • Users 0 members are here
Related
Options

Postgresql database script execution is unsuccessful

Sree Vignesh

Hello,

I tried installing HP Performance Advisor 7.1 on a server. The installation fails with the message " PostgreSQl database installation is successful. postgresql database script execution is unsuccessful. HPE XP7 performance advisor management station installation is rollback". I have also been working on other set of servers, where the installation is smooth. But this has happened only in two servers until now. Has anyone else faced the same?

Below is the log extract from where the fail kicks off,

9-14-2017 05:08:26 :: INFO :: Successfully launched Postgres batch file :C:\HPE\HPSS\utils\silentInstall.bat

9-14-2017 05:08:26 :: INFO :: File (C:\HPE\HPSS\utils\silentInstall.bat) deleted Successfully

9-14-2017 05:08:26 :: INFO :: Postgres Successfully installed

9-14-2017 05:08:26 :: INFO :: Postgres Bin Path :C:\HPE\HPSS\Postgres\bin

9-14-2017 05:08:26 :: INFO :: Directory(C:\HPE\HPSS\padb\)s Created Successfully

9-14-2017 05:08:26 :: INFO :: Data Dir Path :C:\HPE\HPSS\padb\

9-14-2017 05:08:26 :: INFO :: Directory (C:\HPE\HPSS\padb\) Already exists

9-14-2017 05:08:26 :: INFO :: Postgres database command line :Y C:\HPE\HPSS\Postgres\bin C:\HPE\HPSS\padb\

9-14-2017 05:08:43 :: INFO :: Exitcode from the program C:\HPE\HPSS\scripts\installdb.bat=2

9-14-2017 05:08:43 :: ERROR :: Launch Application Failure

9-14-2017 05:08:43 :: ERROR :: Database installation fails, unable to create database :C:\HPE\HPSS\scripts\installdb.bat

9-14-2017 05:09:13 :: ERROR :: PostagreSQL database installation is successful. PostagreSQL database script execution is unsuccessful. HPE XP7 Performance Advisor Management Station installation is rollback.

9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:26.61 - START - installdb xxx xxx Y C:\HPE\HPSS\Postgres\bin

9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:26.61 - Installing as NT Service...start

9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:26.70 - Installing as NT Service...end

9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:26.71 - Initializing database...- start

9-14-2017 05:09:13 :: The files belonging to this database system will be owned by user "SYSTEM".

9-14-2017 05:09:13 :: This user must also own the server process.

9-14-2017 05:09:13 ::

9-14-2017 05:09:13 :: The database cluster will be initialized with locale "English_United States.1252".

9-14-2017 05:09:13 :: The default text search configuration will be set to "english".

9-14-2017 05:09:13 ::

9-14-2017 05:09:13 :: Data page checksums are disabled.

9-14-2017 05:09:13 ::

9-14-2017 05:09:13 :: creating directory C:/HPE/HPSS/padb/data ... ok

9-14-2017 05:09:13 :: creating subdirectories ... ok

9-14-2017 05:09:13 :: selecting default max_connections ... 100

9-14-2017 05:09:13 :: selecting default shared_buffers ... 128MB

9-14-2017 05:09:13 :: selecting dynamic shared memory implementation ... windows

9-14-2017 05:09:13 :: creating configuration files ... ok

9-14-2017 05:09:13 :: creating template1 database in C:/HPE/HPSS/padb/data/base/1 ... ok

9-14-2017 05:09:13 :: initializing pg_authid ... ok

9-14-2017 05:09:13 :: setting password ... ok

9-14-2017 05:09:13 :: initializing dependencies ... ok

9-14-2017 05:09:13 :: creating system views ... ok

9-14-2017 05:09:13 :: loading system objects' descriptions ... ok

9-14-2017 05:09:13 :: creating collations ... not supported on this platform

9-14-2017 05:09:13 :: creating conversions ... ok

9-14-2017 05:09:13 :: creating dictionaries ... ok

9-14-2017 05:09:13 :: setting privileges on built-in objects ... ok

9-14-2017 05:09:13 :: creating information schema ... ok

9-14-2017 05:09:13 :: loading PL/pgSQL server-side language ... ok

9-14-2017 05:09:13 :: vacuuming database template1 ... child process exited with exit code 1

9-14-2017 05:09:13 :: initdb: removing data directory "C:/HPE/HPSS/padb/data"

9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:32.42 - Initializing database...- end

9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:32.42 - copy postgresql.conf file to data folder. -start

9-14-2017 05:09:13 :: The system cannot find the path specified.

9-14-2017 05:09:13 ::         0 file(s) copied.

9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:32.42 - copy postgresql.conf file to data folder. -end

9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:32.42 - deleting C:\HPE\HPSS\Postgres\bin.\pgpass.txt...- start

9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:32.43 - deleting C:\HPE\HPSS\Postgres\bin.\pgpass.txt...- end

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.43 - check and create C:\HPE\HPSS\padb\\data\dbs -start

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.43 - check and create C:\HPE\HPSS\padb\\data\dbs -end

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.43 - check and create C:\HPE\HPSS\padb\\data\indexes -start

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.43 - check and create C:\HPE\HPSS\padb\\data\indexes -end

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.43 - call startdb.bat - start

9-14-2017 05:09:14 :: 'net' is not recognized as an internal or external command,

9-14-2017 05:09:14 :: operable program or batch file.

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.48 - call startdb.bat - end

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.48 - call build_datamodel.bat xxx xxx PA - start

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:43.06 - ERROR :: Create datamodel - Failed Error level 2

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.50 - START - build_datamodel xxx xxx padb C:\HPE\HPSS\Postgres\bin

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.50 - Calling getdbport - start

9-14-2017 05:09:14 :: C:\HPE\HPSS\scripts\\getdbport

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.53 - Calling getdbport - end

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.53 - delete datamodel.sql - start

9-14-2017 05:09:14 :: Could Not Find C:\HPE\HPSS\scripts\datamodel.sql

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.53 - delete datamodel.sql - end

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:32.53 - dropdb.exe  padb - start

9-14-2017 05:09:14 :: dropdb: could not connect to database template1: could not connect to server: Connection refused (0x0000274D/10061)

9-14-2017 05:09:14 :: Is the server running on host "localhost" (127.0.0.1) and accepting

9-14-2017 05:09:14 :: TCP/IP connections on port 2365?

9-14-2017 05:09:14 :: could not connect to server: Connection refused (0x0000274D/10061)

9-14-2017 05:09:14 :: Is the server running on host "localhost" (::1) and accepting

9-14-2017 05:09:14 :: TCP/IP connections on port 2365?

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:36.67 - dropdb.exe  padb - end

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:36.67 - createdb.exe  padb - start

9-14-2017 05:09:14 :: createdb: could not connect to database template1: could not connect to server: Connection refused (0x0000274D/10061)

9-14-2017 05:09:14 :: Is the server running on host "localhost" (127.0.0.1) and accepting

9-14-2017 05:09:14 :: TCP/IP connections on port 2365?

9-14-2017 05:09:14 :: could not connect to server: Connection refused (0x0000274D/10061)

9-14-2017 05:09:14 :: Is the server running on host "localhost" (::1) and accepting

9-14-2017 05:09:14 :: TCP/IP connections on port 2365?

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:40.79 - createdb.exe  padb - end

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:40.89 - Create datamodel for  padb - start

9-14-2017 05:09:14 :: psql: could not connect to server: Connection refused (0x0000274D/10061)

9-14-2017 05:09:14 :: Is the server running on host "localhost" (127.0.0.1) and accepting

9-14-2017 05:09:14 :: TCP/IP connections on port 2365?

9-14-2017 05:09:14 :: could not connect to server: Connection refused (0x0000274D/10061)

9-14-2017 05:09:14 :: Is the server running on host "localhost" (::1) and accepting

9-14-2017 05:09:14 :: TCP/IP connections on port 2365?

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:43.06 - ERROR :: Create datamodel for  padb - Failed, Error level is :2

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:43.06 - Create datamodel for  padb - end

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:43.06 - END - build_datamodel xxx xxx padb C:\HPE\HPSS\Postgres\bin

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:43.07 - call build_datamodel.bat xxx xxx PA - end

9-14-2017 05:09:14 :: Thu 09/14/2017   5:08:43.07 - call stopdb.bat -start

  • 0  

    Hello Sree,

    I'm sorry that you are having problems with Performance Adivsor.  Unforutnately, this is not the correct forum for HPE Performance Advisor 7.1.  This forum is for the Software product Storage Essentials, which is different.

     HPE Midrange and Enterprise Storage
    https://community.hpe.com/t5/Midrange-and-Enterprise-Storage/ct-p/midrange-enterprise

    However, in looking at the error messages that you provided for PostgreSQL, I can see the following that looks like a problem.

    ...
    9-14-2017 05:09:13 :: creating collations ... not supported on this platform
    9-14-2017 05:09:13 :: creating conversions ... ok
    9-14-2017 05:09:13 :: creating dictionaries ... ok
    9-14-2017 05:09:13 :: setting privileges on built-in objects ... ok
    9-14-2017 05:09:13 :: creating information schema ... ok
    9-14-2017 05:09:13 :: loading PL/pgSQL server-side language ... ok
    9-14-2017 05:09:13 :: vacuuming database template1 ... child process exited with exit code 1
    9-14-2017 05:09:13 :: initdb: removing data directory "C:/HPE/HPSS/padb/data"
    9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:32.42 - Initializing database...- end
    9-14-2017 05:09:13 :: Thu 09/14/2017   5:08:32.42 - copy postgresql.conf file to data folder. -start
    9-14-2017 05:09:13 :: The system cannot find the path specified.
    9-14-2017 05:09:13 ::         0 file(s) copied.
    ...

     It appears that there is a problem with the Windows Platform or something else.  I would confirm that the version of Windows that you are using is supported and maybe try again with a clean system if possible.

    I would suggest you post your question in the other forum which will have people from HPE Storage that would be able to assist you and answer your questions.

    Regards,

    Mark

  • 0 in reply to Mark_Butler

    Hello Mark,

    I am new here. Could you please help me with the Forum name which could be of very much helpful to me. Thanks in advance.

  • Suggested Answer

    0   in reply to Sree Vignesh

    Hello Sree,

    I don't know if you are aware of this, but HPE and Software are now separate companies.  The former HPE Software division is now part of a company by the name of Micro Focus.

    I mention that because I am not an authoritative source for the HPE Storage forums.

    I provided you the link to the HPE Storage area and it lists three forums which are for 3PAR, EVA and StoreVirtual.  None of those are for XP arrays, so it looks like they do not have one specific for XP arrays.  I saw a few questions within the EVA forum for XP arrays, but I do not know.

    In looking further, I did find the following URL for XP Storage.

    https://community.hpe.com/t5/XP-Storage/bd-p/xp-storage

    The challenge is that I do not see a lot of questions in the list and do not know how well it is being monitored.

    I'm sorry that I cannot provide a better answer.  Good luck.

    Regards,

    Mark

  • 0 in reply to Mark_Butler

    Thank you so much for your time and effort. Appreciate it. 

Resources

Support
Documentation
Learning Services
CyberRes Academy
Partner Programs
Contact us
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Conduct
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.