search for: ctdb_script_vardir

...: Directory >> nonexistent >> sh: echo: I/O error >> sh: echo: I/O error > > That's weird. The only file really created by that script is the lock > file that is used to make sure we don't debug locks too many times. > That should be in: > > "${CTDB_SCRIPT_VARDIR}/debug_locks.lock" Next time it happens I will check this. > The other possibility is the use of the script_log() function to try to > get the output logged. script_log() isn't my greatest moment. When > debugging you could just replace it with the logger command to get the &g...

Hi List, I set up a ctdb cluster a couple months back. Things seemed pretty solid for the first 2-3 weeks, but then I started getting reports of people not being able to access files, or some times directories. It has taken me a while to figure some stuff out, but it seems the common denominator to this happening is vacuuming timeouts for locking.tdb in the ctdb log, which might go on

...nt >>> sh: echo: I/O error >>> sh: echo: I/O error >> >> That's weird.  The only file really created by that script is the lock >> file that is used to make sure we don't debug locks too many times. >> That should be in: >> >>    "${CTDB_SCRIPT_VARDIR}/debug_locks.lock" > > Next time it happens I will check this. > >> The other possibility is the use of the script_log() function to try to >> get the output logged.  script_log() isn't my greatest moment.  When >> debugging you could just replace it with the l...

...ba/etc/ctdb/debug_locks.sh: cannot create : Directory > nonexistent > sh: echo: I/O error > sh: echo: I/O error That's weird. The only file really created by that script is the lock file that is used to make sure we don't debug locks too many times. That should be in: "${CTDB_SCRIPT_VARDIR}/debug_locks.lock" The other possibility is the use of the script_log() function to try to get the output logged. script_log() isn't my greatest moment. When debugging you could just replace it with the logger command to get the output out to syslog. > From googling, the vacuuming...

...O error >>>> sh: echo: I/O error >>> >>> That's weird.  The only file really created by that script is the lock >>> file that is used to make sure we don't debug locks too many times. >>> That should be in: >>> >>>    "${CTDB_SCRIPT_VARDIR}/debug_locks.lock" >> >> Next time it happens I will check this. >> >>> The other possibility is the use of the script_log() function to try to >>> get the output logged.  script_log() isn't my greatest moment.  When >>> debugging you could just...