I was reconfiguring autofs and when I tried to rmdir one of the directories, I got "Device or resource busy"... ok, so let's just run 'fuser -v /dir'. To my surprise, it returned nothing. Alright, back to good old, lsof and..... nothing.
Strange. Looks like a bug.
So, I had to un-reconfigure autofs and put everything back the way it was. Once I did that, I restarted autofs and fuser -v correctly identified the rogue dir as being held open by autofs.
Now, all I did was, shutdown autofs, removed the rogue dir and reconfigure autofs once again.
Friday, April 26, 2013
Sunday, April 21, 2013
taboot except Exception as e
taboot
Traceback (most recent call last):
File "/usr/bin/taboot", line 19, in ?
import taboot.cli
File "/usr/lib/python2.4/site-packages/taboot/cli.py", line 24, in ?
import taboot.runner
File "/usr/lib/python2.4/site-packages/taboot/runner.py", line 19, in ?
from taboot.util import instantiator
File "/usr/lib/python2.4/site-packages/taboot/util.py", line 25, in ?
from taboot.log import *
File "/usr/lib/python2.4/site-packages/taboot/log.py", line 114
except Exception as e:
^
SyntaxError: invalid syntax
I'm on RHEL 5 and I finally have taboot executing after a lot of effort troubleshooting. It's a terrible show stopper bug. I yum installed it from the EPEL repo and you would think that since you yum installed the command, it would just work right? Well, not with taboot.
The problem was, the syntax in taboot was coded for python v >2.4 but it wants v2.4. So, I had to go replace all of the "as e" errors with ",e".
Apparently, this "as e" vs. ",e" has to do with the version of python.
Subscribe to:
Posts (Atom)