Community in read only mode June 18 & 19
This community will be set in READ ONLY mode for a while on Tuesday June 18 into Wednesday June 19 while we import content and users from our Micro Focus Forums community site. MORE INFORMATION
Valued Contributor.. Ruzanna Valued Contributor..
Valued Contributor..
3122 views

UCMDB Data Flow Probe 10.30 error during installation

Jump to solution

Hello friends,

I have a problem with HP UCMDB Data Flow Probe 10.30 installation.

During installation process I recieve "Data Flow Probe PostgreSQL Database Problem" error notification.

I have attached screenshot of error window.

P.S. HP UCMDB Data Flow Probe 10.20 was successfully instaled, but I need 10.30.

 

Thanks in advance.

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Respected Contributor.. churchie73 Respected Contributor..
Respected Contributor..

Re: UCMDB Data Flow Probe 10.30 error during installation

Jump to solution

Hi Ruzanna,

 

Others have noted that this may be due to the user account chosen for the PostgreSQL having forbidden characters. I have a copy/paste below from another post addressing this issue. It is from the release notes.

"...covered in the UCMDB 10.30 Release Notes. .

Universal Discovery - General

LIMITATION: (Probe installation)

Probe cannot be started after installation if any of the following special characters are included in the PostgreSQL user account password: ? | & ) %

Workaround: During probe installation, do not use these special characters for PostgreSQL user"

Give that a try.

4 Replies
Highlighted
Respected Contributor.. churchie73 Respected Contributor..
Respected Contributor..

Re: UCMDB Data Flow Probe 10.30 error during installation

Jump to solution

Hi Ruzanna,

 

Others have noted that this may be due to the user account chosen for the PostgreSQL having forbidden characters. I have a copy/paste below from another post addressing this issue. It is from the release notes.

"...covered in the UCMDB 10.30 Release Notes. .

Universal Discovery - General

LIMITATION: (Probe installation)

Probe cannot be started after installation if any of the following special characters are included in the PostgreSQL user account password: ? | & ) %

Workaround: During probe installation, do not use these special characters for PostgreSQL user"

Give that a try.

Valued Contributor.. Ruzanna Valued Contributor..
Valued Contributor..

Re: UCMDB Data Flow Probe 10.30 error during installation

Jump to solution

Hi, thank you for your valuable response.

You are right, in my password I had have '&' sign, which I replaced with '=' sign. Installation was finished with success, but now I can't start Probe service. In the log file I recieved such errors:

wrapperm | The UCMDB Probe service is not installed - The specified service does not exist as an installed service. (0x424)
wrapperm | UCMDB Probe service installed.
wrapper | --> Wrapper Started as Service
wrapper | Java Service Wrapper Professional Edition 64-bit 3.5.27
wrapper | Copyright (C) 1999-2015 Tanuki Software, Ltd. All Rights Reserved.
wrapper | http://wrapper.tanukisoftware.com
wrapper | Licensed to Hewlett-Packard Company for UCMDB Data Flow Probe
wrapper |
wrapper | Launching a JVM...
jvm 1 | -XX:+CMSClassUnloadingEnabled -XX:+CMSIncrementalMode -XX:CompileCommand=exclude,jregex/Pretokenizer,next -XX:+HeapDumpOnOutOfMemoryError -XX:InitialHeapSize=536870912 -XX:+ManagementServer -XX:MaxGCPauseMillis=250 -XX:MaxHeapSize=2147483648 -XX:MaxMetaspaceSize=1073741824 -XX:MaxTenuringThreshold=6 -XX:NewRatio=2 -XX:OldPLABSize=16 -XX:+PrintCommandLineFlags -XX:+UseAdaptiveGCBoundary -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:-UseLargePagesIndividualAllocation -XX:+UseParNewGC
jvm 1 | CompilerOracle: exclude jregex/Pretokenizer.next
jvm 1 | WrapperManager: Initializing...
jvm 1 | <2016-11-26 14:04:02,886> 0 [INFO ] [WrapperSimpleAppMain] (CollectorsParameters.java:192) - java path calculated:C:\hp\UCMDB\DataFlowProbe\bin\..\bin\jre\bin\java
jvm 1 | Starting the Probe ...
jvm 1 | Default OEM Encoding: cp437, Default ANSI Encoding: windows-1252
jvm 1 | Probe version [UCMDB.PROBE.10.30.Build_305]
jvm 1 | <2016-11-26 14:04:03,011> 125 [INFO ] [WrapperSimpleAppMain] (MainProbeAgent.java:276) - The probe will not add RMI connector in union mode.
jvm 1 | <2016-11-26 14:04:03,136> 250 [INFO ] [WrapperSimpleAppMain] (FIPSUtils.java:149) - JCE Unlimited Policy JARs are not in probe side.
jvm 1 | <2016-11-26 14:04:03,136> 250 [INFO ] [WrapperSimpleAppMain] (ProbeGwDBServicesFactory.java:35) - starting the DBServices for the ProbeGwDBServicesFactory...
jvm 1 | <2016-11-26 14:04:03,699> 813 [FATAL] [WrapperSimpleAppMain] (ProbeGwDBServicesFactory.java:59) - Failed creating DBServices for ProbeGwDBServicesFactory!!
jvm 1 | com.mercury.topaz.cmdb.shared.base.CmdbException: [ErrorCode [-2147483648] undefined error code]
jvm 1 | org.postgresql.util.PSQLException: FATAL: password authentication failed for user "mamprobe"
jvm 1 | at com.mercury.topaz.cmdb.server.manage.dal.ConnectionPoolManager.getNativeConnection(ConnectionPoolManager.java:518)
jvm 1 | at com.hp.ucmdb.discovery.library.dblayer.DBServicesImpl.init(DBServicesImpl.java:105)
jvm 1 | at com.hp.ucmdb.discovery.library.dblayer.DBServicesImpl.<init>(DBServicesImpl.java:80)
jvm 1 | at com.hp.ucmdb.discovery.probe.agents.probegw.dbservices.ProbeGwDBServicesFactory.<clinit>(ProbeGwDBServicesFactory.java:51)
jvm 1 | at com.hp.ucmdb.discovery.probe.agents.probegw.MainProbeAgent.initDbService(MainProbeAgent.java:363)
jvm 1 | at com.hp.ucmdb.discovery.probe.agents.probegw.MainProbeAgent.start(MainProbeAgent.java:125)
jvm 1 | at com.hp.ucmdb.discovery.probe.agents.probegw.MainProbeAgent.main(MainProbeAgent.java:281)
jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
jvm 1 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
jvm 1 | at java.lang.reflect.Method.invoke(Method.java:498)
jvm 1 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:325)
jvm 1 | at java.lang.Thread.run(Thread.java:745)
jvm 1 | Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "mamprobe"
jvm 1 | at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:433)
jvm 1 | at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:208)
jvm 1 | at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:67)
jvm 1 | at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:216)
jvm 1 | at org.postgresql.Driver.makeConnection(Driver.java:406)
jvm 1 | at org.postgresql.Driver.connect(Driver.java:274)
jvm 1 | at java.sql.DriverManager.getConnection(DriverManager.java:664)
jvm 1 | at java.sql.DriverManager.getConnection(DriverManager.java:208)
jvm 1 | at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:78)
jvm 1 | at com.mercury.topaz.cmdb.server.manage.dal.DataDirectConnectionFactory.createConnection(DataDirectConnectionFactory.java:30)
jvm 1 | at com.hp.ucmdb.discovery.library.dblayer.DiscoveryConnectionFactoryCreator$DbConnectionFactory.createConnection(DiscoveryConnectionFactoryCreator.java:53)
jvm 1 | at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
jvm 1 | at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
jvm 1 | at com.mercury.topaz.cmdb.server.manage.dal.ConnectionPoolManager$ConnectionPoolDecorator.borrowObject(ConnectionPoolManager.java:800)
jvm 1 | at com.mercury.topaz.cmdb.server.manage.dal.ConnectionPoolManager.getNativeConnection(ConnectionPoolManager.java:514)
jvm 1 | ... 12 more
jvm 1 | WrapperSimpleApp:
jvm 1 | WrapperSimpleApp Error: Encountered an error running main:
jvm 1 | WrapperSimpleApp Error: java.lang.ExceptionInInitializerError
jvm 1 | WrapperSimpleApp Error: at com.hp.ucmdb.discovery.probe.agents.probegw.MainProbeAgent.initDbService(MainProbeAgent.java:363)
jvm 1 | WrapperSimpleApp Error: at com.hp.ucmdb.discovery.probe.agents.probegw.MainProbeAgent.start(MainProbeAgent.java:125)
jvm 1 | WrapperSimpleApp Error: at com.hp.ucmdb.discovery.probe.agents.probegw.MainProbeAgent.main(MainProbeAgent.java:281)
jvm 1 | WrapperSimpleApp Error: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
jvm 1 | WrapperSimpleApp Error: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
jvm 1 | WrapperSimpleApp Error: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
jvm 1 | WrapperSimpleApp Error: at java.lang.reflect.Method.invoke(Method.java:498)
jvm 1 | WrapperSimpleApp Error: at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:325)
jvm 1 | WrapperSimpleApp Error: at java.lang.Thread.run(Thread.java:745)
jvm 1 | WrapperSimpleApp Error: Caused by: java.lang.NullPointerException
jvm 1 | WrapperSimpleApp Error: at com.hp.ucmdb.discovery.probe.agents.common.ProbeDBServices.<init>(ProbeDBServices.java:16)
jvm 1 | WrapperSimpleApp Error: at com.hp.ucmdb.discovery.probe.agents.probegw.dbservices.ProbeGwDBServicesFactory.<clinit>(ProbeGwDBServicesFactory.java:62)
jvm 1 | WrapperSimpleApp Error: ... 9 more
jvm 1 | <2016-11-26 14:04:05,542> 2656 [INFO ] [Thread-1] (DiscoveryClient.java:1029) - ProbeGW: sending probe status to the server: Disconnected_Stopped
jvm 1 | <2016-11-26 14:04:05,558> 2672 [ERROR] [Thread-1] (MainProbeAgent.java:77) - Failed to notify the server about being stopped
jvm 1 | <2016-11-26 14:04:05,558> 2672 [INFO ] [Thread-1] (MainProbeAgent.java:81) - Stopping the probegw ...
jvm 1 | <2016-11-26 14:04:05,574> 2688 [INFO ] [Thread-1] (MainProbeAgent.java:90) - Mam's Collectors Module stopped successfully
jvm 1 | OpenJDK 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
wrapper | on_exit trigger matched. Restarting the JVM. (Exit code: 1)
wrapper | Reloading Wrapper configuration...
wrapper | Launching a JVM...

 

Thank you for supporting!!

 

0 Likes
Valued Contributor.. Ruzanna Valued Contributor..
Valued Contributor..

Re: UCMDB Data Flow Probe 10.30 error during installation

Jump to solution

Ok, to the list of not working special characters, you can add '=' sign. All works fine after I changed it to this " _ " sign.

Thank you again!

DBarbeiro Super Contributor.
Super Contributor.

Re: UCMDB Data Flow Probe 10.30 error during installation

Jump to solution

I had a somewhat similar issue, in that the probe never stops "creating databases".

My password was (test environment) P@ssw0rd

Thing is, the installer told me I cannot use that special character, and I had to use one of the following:

,\:/._?&%=+-[]()|

 

if you look at it carefully, you will notice that these postresql forbidden characters are all there... /facepalm

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.