iMC PLAT 7.3 E0705 - MySQL 8.0.23 : MysqL syntax error during installation /deployment failed

[nonozi]

Hello

I'm doing a fresh install of iMC on a new 7.9 redhat with a MySQL 8.0.23 base. iMC does not install and i have a MySQL syntax error. Here is what gives me the dbresult.log file which is displayed during this error:

Begin to install imcwlandm database and data...

Current Database is Mysql

Begin to create wlan_db database...

mysql: [Warning] Using a password on command line interface can be insecure.

mysql: [Warning] Using a password on command line interface can be insecure.

mysql: [Warning] Using a password on command line interface can be insecure.

ERROR 1064 (42000) at line 2: You have a error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'identified by 'iMC5_00559G6Iwhs'' at line 1

The install of imcwlandm finished uncussefully, please contact your local IMC support centre.

Plugin policy password was disable.

Have you got some ideas about this error and hox to resolve it ?

Thanks you very much for any help you could give me.

Arnaud

[jguse]

Hello,

I've seen this before with MySQL 8.0 - here's a summary of the issue:

IMC attempts to CREATE USER with auth plugin (mysql_native_password) but without any password, which may fail password validation unless disabled.

It will follow that up with a second ALTER USER command, which attempts to set the user’s password in the ‘IDENTIFIED BY …’ part of the statement.

That is basically command syntax which worked in older MySQL but was deprecated in newer MySQL and eventually dropped entirely from 8.0 onwards.

8.0: https://dev.mysql.com/doc/refman/8.0/en/alter-user.html

There is no IDENTIFIED BY option in the permitted syntax.

5.7: https://dev.mysql.com/doc/refman/5.7/en/alter-user.html

ALTER USER 'jeffrey'@'localhost' IDENTIFIED BY 'new_password',

I see the issue in your case is with the WSM component included in IMC Enterprise, so I would suggest deploying all other components except WSM for now, which should work. Then you can un-deploy the two WSM components (via DMA's Deploy tab, right-click them), remove them entirely, and then install and deploy WSM with the latest base version from the website - https://h10145.www1.hpe.com/downloads/SoftwareReleases.aspx?ProductNumber=JF414AAE

Root cause is that WSM 7.3 E0603 included in your IMC Enterpris did not support MySQL 8.0, this is fixed in E0604.

[nonozi]

Justin,

Thank you very much for these precious very clear explanations.

I will follow your advice and then I will come back in a while to close my post by bringing the conclusions following these explanations.

Regards 

Arnaud

[nonozi]

Hello,

If i desactivate NW componant, installation is a success.

At the end of installation i check the box to start service now in window prompt. I can connect but Firefoxor Chrome browser was extremelly slow to load the page. Next step, i restart my RedHat and the TCP/port (8080 and 8443) for administration are not up and running.

I try to restart imcdmsd process but still the same think : not listenning on 8080 and 8443 ports.

If a do a ps -auxx |grep java, i only see one process :

root      1484 13.7  0.9 4903132 233836 ?      Sl   15:52   0:05 /soft/iMC/deploy/jdk/bin/java -server -Xrs -Xms256m -Xmx2048m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/soft/iMC/deploy/log -cp /soft/iMC/deploy/deploy.jar:/jdbc/lib/ojdbc6.jar:/jdbc/lib/ojdbc8.jar -Djavax.net.ssl.trustStore=/soft/iMC/deploy/newks -Djavax.net.ssl.trustStorePassword=iMCV500R001 -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=/soft/iMC/tmp -Dfile.encoding=GB18030 -Dorg.apache.activemq.SERIALIZABLE_PACKAGES=* com.h3c.imc.deploy.DeployMonitorServerLauncher start

I try to restart the process imcdmsd but same thing...

On my old IMC server in production,  there are 4 process java.

# ps auxww |grep java
root      4132  0.0  3.8 2580904 316592 ?      Sl    2020  40:52 /softdata/soft/IMC/deploy/jdk/jre/bin/java -server -Xrs -cp /softdata/soft/IMC/deploy/deploy.jar -Djavax.net.ssl.trustStore=/softdata/soft/IMC/deploy/truststore -Djavax.net.ssl.trustStorePassword=iMCV300R002 -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=/softdata/soft/IMC/tmp -Dfile.encoding=GB18030 com.h3c.imc.deploy.DeployMonitorServerLauncher start
root      4212  0.0  5.7 1024076 468828 ?      Sl    2020  18:55 /softdata/soft/IMC/common/jre/bin/java -Xms32m -Xmx512m -Dimc.home=/softdata/soft/IMC/unbam -Duser.language=en -Duser.country=US -Djavax.net.ssl.keyStore=/softdata/soft/IMC/unbam/security/keystore -Djavax.net.ssl.keyStorePassword=<xxxxxx> -Dfile.encoding=GB18030 -jar /softdata/soft/IMC/unbam/bin/bootstrap.jar -port 8051 start
root      4216  0.0  1.3 2487340 108500 ?      Sl    2020   3:11 /softdata/soft/IMC/common/jre/bin/java -server -Xrs -Dimc.home=/softdata/soft/IMC/seplat -Dfile.encoding=GB18030 -Djava.io.tmpdir=/softdata/soft/IMC/tmp -jar /softdata/soft/IMC/seplat/bin/bootstrap.jar -serverClassName com.h3c.imc.core.CommonServer -port 8039 start
root      4226  0.3 15.3 4092420 1253020 ?     Sl    2020 251:10 /softdata/soft/IMC/common/jre/bin/java -server -Xmx2048m -Xrs -XX:PermSize=64m -XX:MaxPermSize=1024m -Dimc.home=/softdata/soft/IMC/client -Duser.language=en -Duser.country=US -Dfile.encoding=GB18030 -Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=9091 -Dcom.sun.management.jmxremote.authenticate=false -Djavax.net.ssl.keyStore=/softdata/soft/IMC/client/security/keystore -Djavax.net.ssl.keyStorePassword=<xxxxx> -Djava.io.tmpdir=/softdata/soft/IMC/tmp -Dorg.apache.el.parser.COERCE_TO_ZERO=false -jar /softdata/soft/IMC/client/bin/bootstrap.jar start
root      4229  0.0  2.1 2506700 173508 ?      Sl    2020   2:33 /softdata/soft/IMC/common/jre/bin/java -server -Xrs -Dimc.home=/softdata/soft/IMC/euplat -Dfile.encoding=GB18030 -Djava.io.tmpdir=/softdata/soft/IMC/tmp -jar /softdata/soft/IMC/euplat/bin/bootstrap.jar -serverClassName com.h3c.imc.core.CommonServer -port 8035 start

Any idea why imc does not up the TCP port in listenning mode and why it was extremelly slow at the first connection (before reboot) ?

Thanks

Arnaud

[jguse · Accepted solution]

Hello,

Considering the other post about migration - did you migrate using the DBMAN tool, or did you restore a Mysqldump? iMC will not work on the new system if you didn't use the DBMAN to restore the filesystem as well.

[nonozi]

Hello Justin and other people interrested in this post,

To close this post, for installing NW components, i have to install 7.3 E0503P02 (patch 02) : it's a prerequired for NW component (IMC_WSM_7.3_E0604).

Now, i'm going to try to use dbman to report data into my new fresh installation https://community.hpe.com/t5/IMC/uograde-IMC-7-3-on-new-server-RedHAT-MySQL-8-0/td-p/7121630 

Regards,

Arnaud