Error message when slaves not working
sanados
sanados at failure.at
Tue Mar 11 14:30:10 UTC 2008
sanados wrote:
> currently i get those error messages:
>
> root at srv079:/etc/mogilefs# /etc/mogilefs/trunk/utils/mogtool --domain
> files --tracker 127.0.0.1:7001 extract new_motd test.motd
> Error: Something went wrong
> MogileFS backend error message: failure Operation failed
>
> root at srv079:/etc/mogilefs# /etc/mogilefs/trunk/utils/mogtool --domain
> files --tracker 127.0.0.1:7001 lo new_motd
> Error: Something went wrong
> MogileFS backend error message: failure Operation failed
>
>
> after some debugging i found out that this occured by reading the
> pathes from the database.
> Furthermore this is the error message when trying to read the paths
> from the slave but the user has no rights to access the tables;
>
> Perhabs you could adjust the error message to something that would
> give a hint about the problem!
>
> thx
> Jürgen
is it possible that the slave mechanism are not quite production ready?
(after setting users on the slaves)
root at srv079:/etc/mogilefs# mysql -h 10.0.0.162 -u mogilefs -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 26887010
Server version: 5.0.45 MySQL Community Server (GPL)
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> use mogilefs;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> quit
Bye
root at srv079:/etc/mogilefs# mogadm slave list
fsc_db_slave --dsn=10.0.0.162 --username=mogilefs --password=nope
root at srv079:/etc/mogilefs# /etc/mogilefs/trunk/utils/mogtool --domain
szene1 --tracker 127.0.0.1:7001 lo new_motd
Error: Something went wrong
MogileFS backend error message: failure Operation failed
now i ran out of ideas what could be wrong :(
More information about the mogilefs
mailing list