SOLVED
Hello,
Could be that you are running into the Timezone issue on Linux with MySQL.
Next time you attempt an upgrade, check the iMC\deploy\log\dmalog.txt and if you see any error like:
Caused by: com.mysql.cj.exceptions.InvalidConnectionAttributeException: The server time zone value 'CEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support.
Here is a workaround for now:
1) Login to MySQL command line (as root)
2) SET GLOBAL time_zone = '+3:00';
(where '+3:00' should be changed to this server's timezone offset)
See also https://stackoverflow.com/questions/26515700/mysql-jdbc-driver-5-1-33-time-zone-issue
There is another issue that is triggered by NTA, if you have that module installed. It requires upgrading NTA to E0506P02 (to be released shortly).
That said, as I wrote in another post:
It would probably be better not to upgrade to E0703 if you haven't started already, unless you need the features/fixes. There are two known issues with RHEL and MySQL, and I posted the workarounds/fixes here (and in the other thread), and for one of them you would need the new NTA patch (to be posted).
There may be a new base version coming out relatively soon to address the known issues - but don't quote me on that as I'm not involved in it, and you would need to contact your HPE Sales/Account Management for any details about future versions.
Justin
Working @ HPE
Yeah, and @jguse really saved my day (reported issues -> doubt -> question -> issue avoided + waiting for updates)...read here...I'm on a scenario very similar to your one BUT, after reading all the issues that are popped up during last few days, I happily followed given advice.
I'm not an HPE Employee
Hello,
There's one key bit of information I noticed is missing in the manual (sorry, I'd update it if I could). The hostname and actual IP address of the IMC server must be defined in /etc/hosts for IMC installation to work.
Edit /etc/hosts and add a line with "imc.my.domain ip.address", save and try the IMC installer again.
Here is a video on the whole installation process that should help: https://www.youtube.com/watch?v=Ymz-I9F4Hko
Hope that helps you get it running...
Justin
Working @ HPE
Hello,
Here are some MySQL-related answers about timezone that should provide clarity:
https://stackoverflow.com/questions/5488694/mysql-difference-between-cet-and-cest
https://stackoverflow.com/questions/930900/how-do-i-set-the-time-zone-of-mysql
If you are on CET, that is UTC+1:00 and the timezone offset should be based on UTC offsets (not GMT).
Justin
Working @ HPE
Are there any details about the error? For example with service mysql status output, or looking in /var/lib/mysql/ for any .err files that were generated.
I wonder if there is a restriction in RHEL 7.6 regarding MySQL versions supported? However MySQL indicates it should be supported: https://www.mysql.com/support/supportedplatforms/database.html
Justin
Working @ HPE
Ah, glad to hear you could get it working!
Technically you should use MySQL Enterprise (according to Release Notes), but I'll admit I've used the community edition myself for some lab installs and it works fine. Since you mention my.cnf, here is a config I made for reference that is working for me on 5.6, using 1000 max connections to ensure IMC has enough if you install optional modules:
# This file has all unnecessary comments and options removed.
# For all options, please look at the original my-huge.cnf file.
[client]
port = 3306
socket = /var/lib/mysql/mysql.sock
[mysqld]
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-external-locking
key_buffer_size = 384M
max_allowed_packet = 200M
table_open_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
max_connections = 1000
character-set-server = latin1
default-storage-engine = INNODB
lower_case_table_names = 1
innodb_buffer_pool_size = 512M
innodb_additional_mem_pool_size = 16M
thread_concurrency = 8
server-id = 1
[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
no-auto-rehash
[myisamchk]
key_buffer_size = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
I recall having issues with 5.7 because IMC requires innodb_additional_mem_pool_size which is deprecated there. Perhaps they've removed that requirement in E0703 though, I'll make a note to test it one of these days.
Justin
Working @ HPE