1748227 Members
4123 Online
108759 Solutions
New Discussion юеВ

Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

 
SOLVED
Go to solution
dasi66
Frequent Advisor

Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

When aplying upgrade via gui as I always done without any problems, installation stops and says "cannot connect to database". I quit and after that the system is corrupt..? Some of the services wont start.

Running Red Hat Enterprise Linux Server release 7.5 (Maipo), with MySQL-server-5.6.27-1.el7.x86_64.

Any ideas? Cannot get any more details because I restored system from snapshot.

By the way, how is the installation procedure for MySQL now on RH 7, all guides seems outdated? I cannot find any newer MySQL-server-5.x.y1.el7.x86_64 for download as in HPE guides.. Tried to do a new installation on RH 7.6 with MySQL-server-5.x.y1.el7.x86_64 but i can't get Installation check to pass mysql connection check.

15 REPLIES 15
jguse
HPE Pro

Re: Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

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.

Best regards,
Justin

Working @ HPE
Accept or Kudo
parnassus
Honored Contributor

Re: Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

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
Kudos and Accepted Solution banner
dasi66
Frequent Advisor

Re: Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

Hi again. In preparation for the upcoming release i try to set up a new platform with release 7.3 E0605P06 on i new installed RH 7.5 server. Following the MySQL 5.6 on Redhat guide. Everything seems ok, i can connect to database via  mysql тАУu root тАУp. So far so good.

But when i trying to install iMC I got database connection error and cannot continue installation. I tried with iMC 7.1, 7.2, 7.3, E403, E506, But with the same error. 

So what the hell am I doing wrong? I have worked with this for days now and cannot understand what's wrong. Also tried other versions of MySQL and RH, but same problem.

Any ideas?

jguse
HPE Pro

Re: Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

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...

Best regards,
Justin

Working @ HPE
Accept or Kudo
dasi66
Frequent Advisor

Re: Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

Thanks, I'll try that and reply with info soon. Another thing. What value shold it be in the timezone for Central European time in below description:

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) 

jguse
HPE Pro

Re: Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

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).

Best regards,
Justin

Working @ HPE
Accept or Kudo
dasi66
Frequent Advisor

Re: Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

Thanks. I notice that there are problems installing  MySQL-server-5.6.27-1.el7.x86_64.rpm on RH 7.6. Which version do you recommend for RH 7.6? 

Seems ok on earlier versions, like RH 7.4

 

It does not seem to install properly.

[root@x5377 ~]# service mysql start
Starting MySQL.. ERROR! The server quit without updating PID file (/var/lib/mysql/x5377.svk.local.pid).
[root@x5377 ~]#

jguse
HPE Pro

Re: Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

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

Best regards,
Justin

Working @ HPE
Accept or Kudo
dasi66
Frequent Advisor

Re: Problem with upgrade from 7.3E0605P06 -> 7.3E0703 on linux

[root@x5377 dasi]# service mysql status
ERROR! MySQL is not running, but lock file (/var/lock/subsys/mysql) exists

 

[root@x5377 dasi]# more /var/lib/mysql/x5377.svk.local.err

2019-06-20 12:34:38 8407 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2019-06-20 12:34:38 7f8cc046b780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed
in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2019-06-20 12:34:38 8407 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-06-20 12:34:38 8407 [Note] InnoDB: The InnoDB memory heap is disabled
2019-06-20 12:34:38 8407 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-06-20 12:34:38 8407 [Note] InnoDB: Memory barrier is not used
2019-06-20 12:34:38 8407 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-06-20 12:34:38 8407 [Note] InnoDB: Using Linux native AIO
2019-06-20 12:34:38 8407 [Note] InnoDB: Using CPU crc32 instructions
2019-06-20 12:34:38 8407 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2019-06-20 12:34:38 8407 [Note] InnoDB: Completed initialization of buffer pool
2019-06-20 12:34:38 8407 [Note] InnoDB: Highest supported file format is Barracuda.
2019-06-20 12:34:38 8407 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2019-06-20 12:34:38 8407 [Note] InnoDB: Database was not shutdown normally!
2019-06-20 12:34:38 8407 [Note] InnoDB: Starting crash recovery.
2019-06-20 12:34:38 8407 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-06-20 12:34:38 8407 [Note] InnoDB: Restoring possible half-written data pages
2019-06-20 12:34:38 8407 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2019-06-20 12:34:38 8407 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78
79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2019-06-20 12:34:39 8407 [Note] InnoDB: 128 rollback segment(s) are active.
2019-06-20 12:34:39 8407 [Note] InnoDB: Waiting for purge to start
2019-06-20 12:34:39 8407 [Note] InnoDB: 5.6.27 started; log sequence number 1600607
2019-06-20 12:34:39 8407 [Note] Server hostname (bind-address): '*'; port: 3306
2019-06-20 12:34:39 8407 [Note] IPv6 is available.
2019-06-20 12:34:39 8407 [Note] - '::' resolves to '::';
2019-06-20 12:34:39 8407 [Note] Server socket created on IP: '::'.
2019-06-20 12:34:39 8407 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
190620 12:34:39 mysqld_safe mysqld from pid file /var/lib/mysql/x5377.svk.local.pid ended