Hi all, Yesterday was the second time the weekly --net check has not run for me. No log files were created at all.
Trying to debug things, I just ran the mass-check command individually (with the options as assembled by auto-mass-check.sh), but I got no output at all, with no files being created either, and mass-check exited with a return code of 141 after maybe two seconds of waiting. I then tried to run the same mass-check command through the perl debugger (just prepending perl -d), which seemed to work, so I exited and re-started without the debugger. This time, I got "status: starting scan stage" and then things seemed to work as usual. (I aborted, assuming that the results would now be rather late.) Five further invocations of mass-check all seemed to work, i.e. none has aborted without any output, but all have shown "status: starting scan stage" before I aborted manually. In short, I cannot now reproduce the errant behaviour described in the previous paragraph, even though the file system appears unchanged in comparison to 30 minutes ago when things did not work. Is there anything else I can do to help debug the problem? Regards Marc
