I think your problem might be caused by shell semantics; command >& file works in most cases but is not preferred. Try using &> instead, which according to the bash manpage is semantically equivalent to >word 2>&1

Update:
I shouldn't go off and do work in the middle of writing a reply, or two other people will beat me to it ;)