Re: [Maria-discuss] Latest round of Oracle CVE status on MariaDB

2015-08-13 Thread Sergei Golubchik
Hi, Brian! Thanks. I've updated the security page now. I think that CVE-2015-4757 is fixed in 5.5.43 (and 10.0.18), and CVE-2015-4752 CVE-2015-2648 CVE-2015-2643 CVE-2015-2582 are fixed in 5.5.44 (and 10.0.20). While I cannot be sure what CVE-2015-4737 and CVE-2015-2620 are about, I susp

[Maria-discuss] Latest round of Oracle CVE status on MariaDB

2015-08-13 Thread Brian Evans
The quarterly CVE list from oracle was published[1]. The following CVEs are listed there affecting 5.5, but not listed on the MariaDB security page[2]. CVE-2015-4757 CVE-2015-4752 CVE-2015-4737 CVE-2015-2648 CVE-2015-2643 CVE-2015-2620 CVE-2015-2582 Are they fixed with 5.5.45 and 10.0.21, or an

Re: [Maria-discuss] Mariadb 10.1.6, total cluster recovery - gvwstate.dat

2015-08-13 Thread Nirbhay Choubey
Hi Max, On Thu, Aug 13, 2015 at 7:17 AM, Max Zulio wrote: > Hi, > > I am using a Mariadb 10.1.6 three node cluster with wsrep. There is a > gvwstate.dat file created in /var/lib/mysql, but in the log file when > restarting the nodes I see: [Warning] WSREP: access file(gvwstate.dat) > failed(No s

Re: [Maria-discuss] Mariadb 10.1.6, total cluster recovery - gvwstate.dat

2015-08-13 Thread Jamie Gibbard
Hi, Are you sure there are no other errors? I'm not sure that the file being missing is the problem there: When a node stores the Primary Component state to disk, it saves it as the gvwstate.dat file. The node creates and updates this file when the cluster forms or changes the Primary Componen

[Maria-discuss] Mariadb 10.1.6, total cluster recovery - gvwstate.dat

2015-08-13 Thread Max Zulio
Hi, I am using a Mariadb 10.1.6 three node cluster with wsrep. There is a gvwstate.dat file created in /var/lib/mysql, but in the log file when restarting the nodes I see: [Warning] WSREP: access file(gvwstate.dat) failed(No such file or directory). This seems to be the only thing stopping automa