Archive for 2013

Failover Cluster Report post on Scripting Guys

I’ve got another post on the Scripting Guys Blog. This post uses powershell to report on a Windows Failover Cluster. I think it’s pretty cool, let me know what you think!.

Matching windows cluster node ID to physical server

Here’s the Powershell version of matching the node number in Cluster.Log files to the actual cluster node names. Essentially log messages like this one… ERROR_CLUSTER_GROUP_MOVING(5908)’ because of ”Cluster Disk’ is owned by node 1, not 2.’ Inspired by this post using cluster.exe. ?View Code POWERSHELLGet-ClusterNode -Cluster ClusterName | SELECT Name, Id, State | Format-Table -Autosize; […]

What does disk maintenance mode actually do to a Failover Cluster?

In Failover Cluster Manager if you perform the following sequence of actions… Storage > Right Click a Disk > More Actions… > Turn on maintenance for this disk You are presented with the following message in the status bar. Turning on maintenance for a physical disk resource allows the disk to be used by applications […]

[Warning] User entry ‘username’@’hostname’ has an empty plugin value. The user will be ignored and no one can login with this user anymore.

After upgrading an instance of MySQL to 5.7 I was unable to login and had several of the following entries in the error log. [Warning] User entry ‘username’@’hostname’ has an empty plugin value. The user will be ignored and no one can login with this user anymore. This is explained the the release notes. Here’s […]

ERROR Failed to open the relay log ‘7’ (relay_log_pos 0)

I received the following error when I upgraded modified a slave from MySQL 5.6.14 to MariaDB 5.5.33 and executing “START SLAVE;”. 131106 11:12:31 [ERROR] Failed to open the relay log ‘7’ (relay_log_pos 0) I checked my relay-log.info file and it looked like below… 7 /logs/relay/hostname-relaylog.000046 661930553 hostname-masterlog.000019 661930383 0 0 0 Obviously there a difference […]