wsrep_node_name blank for servers with 3rd level domain name

Bug #1551369 reported by Mike EKlund on 2016-02-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Fix Released
Undecided
Unassigned

Bug Description

I am not sure if it is strictly 3rd level or there are other issues.

ii percona-xtradb-cluster-5.6-dbg 5.6.28-25.14-1.trusty amd64 Debugging package for Percona XtraDB Cluster
ii percona-xtradb-cluster-client-5.6 5.6.28-25.14-1.trusty amd64 Percona XtraDB Cluster database client binaries
ii percona-xtradb-cluster-common-5.6 5.6.28-25.14-1.trusty amd64 Percona XtraDB Cluster database common files (e.g. /etc/mysql/my.cnf)
ii percona-xtradb-cluster-full-56 5.6.28-25.14-1.trusty amd64 Percona XtraDB Cluster with Galera
ii percona-xtradb-cluster-galera-3 3.14-1.trusty amd64 Metapackage for latest version of galera3.
ii percona-xtradb-cluster-galera-3.x 3.14-1.trusty amd64 Galera components of Percona XtraDB Cluster
ii percona-xtradb-cluster-galera-3.x-dbg 3.14-1.trusty amd64 Debugging package for Percona XtraDB Cluster Galera 3.
ii percona-xtradb-cluster-galera3-dbg 3.14-1.trusty amd64 Metapackage for latest version of debug packages.
ii percona-xtradb-cluster-garbd-3 3.14-1.trusty amd64 Metapackage for latest version of garbd3.
ii percona-xtradb-cluster-garbd-3.x 3.14-1.trusty amd64 Garbd components of Percona XtraDB Cluster
ii percona-xtradb-cluster-garbd-3.x-dbg 3.14-1.trusty amd64 Debugging package for Percona XtraDB Cluster Garbd 3.
ii percona-xtradb-cluster-server-5.6 5.6.28-25.14-1.trusty amd64 Percona XtraDB Cluster database server binaries
ii percona-xtradb-cluster-server-debug-5.6 5.6.28-25.14-1.trusty amd64 Percona XtraDB Cluster database server UNIV_DEBUG binaries
ii percona-xtradb-cluster-test-5.6 5.6.28-25.14-1.trusty amd64 Percona XtraDB Cluster database test suite

<email address hidden>:~# hostname -f
sql07.atl.domain.net

mysql> SHOW VARIABLES LIKE 'wsrep_node_name';
+-----------------+-------+
| Variable_name | Value |
+-----------------+-------+
| wsrep_node_name | |
+-----------------+-------+
1 row in set (0.11 sec)

CVE References

Mike EKlund (meklund-launchpad) wrote :

it appears to be related to the glibc updates for https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7547

root@atl-userdb3:~# hostname -f
atl-userdb3.domain.com

mysql> SHOW VARIABLES LIKE 'wsrep_node_name';
+-----------------+-------+
| Variable_name | Value |
+-----------------+-------+
| wsrep_node_name | |
+-----------------+-------+
1 row in set (0.00 sec)

Kenn Takara (kenn-takara) wrote :

Hmm. Looking through the code, I don't think the hostname is ever used as a default (it looks like we look it up, but then overwrite it during initialization).

Mike EKlund (meklund-launchpad) wrote :

well, before CVE-2015-7547 glibc updates it had a value then after it did not.

Changed in percona-xtradb-cluster:
status: New → Fix Committed
Changed in percona-xtradb-cluster:
milestone: none → 5.6.29-25.15
Changed in percona-xtradb-cluster:
status: Fix Committed → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-534

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-509

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers