CC: | "dormando [...] cpan.org" <dormando [...] cpan.org> |
Subject: | Host status change - bug in mogadm command |
Date: | Wed, 15 Feb 2012 22:55:08 +0000 |
To: | "bug-MogileFS-server [...] rt.cpan.org" <bug-MogileFS-server [...] rt.cpan.org> |
From: | Pascal Benard <pbenard [...] sugarsync.com> |
Hello all,
We encountered an issue today where a typo in the host status change caused the entry in the DB to be blank, and then causing all the trackers to fail.
The command entered was:
mogadm --trackers=hmogile:7001 host modify hfs40 --status=alivew
==> Failure modifying host: failure Operation failed
This resulted in the "status" column of the "host" table to be nulled out for the matching host/hostid, even though the output indicated that the operation had failed.
Note that a completely wrong status will yield a different response, and will not update the DB:
mogadm --trackers=hmogile:7001 host modify hfs40 --status=klsd
==> Failure modifying host: unknown_state Invalid/unknown state
This was observed in version 2.46. It is possible that the string matching pattern function is the same in subsequent versions.
Environment:
MogileFS::Server INST_VERSION 2.46
MogileFS::Utils INST_VERSION 2.19
Linux 2.6.18-128.1.10.el5.centos.plus
Perl This is perl, v5.8.8 built for x86_64-linux-thread-multi
Thank you to all who helped resolve the issue.
Regards,
Pascal Benard