Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the mogilefs-server CPAN distribution.

Report information
The Basics
Id: 75043
Status: new
Priority: 0/
Queue: mogilefs-server

Owner: Nobody in particular
Requestors: pbenard [...]

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

CC: "dormando [...]" <dormando [...]>
Subject: Host status change - bug in mogadm command
Date: Wed, 15 Feb 2012 22:55:08 +0000
To: "bug-MogileFS-server [...]" <bug-MogileFS-server [...]>
From: Pascal Benard <pbenard [...]>
Download (untitled) / with headers
text/plain 1.1k
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 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

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to