Allen, Not aware of any default ftplets... but if the user is willing to help out to repro the problem, you can try turning on all logging to "debug" and seeing what the chain of command is when the user logs in and uploads the file...
Also, can you print out some logging messages in your Ftplet constructor? perhaps it's not being loaded into the system the way you expect, so it never gets executed? that'd be my first attempt On Tue, Jun 7, 2011 at 6:32 PM, Allen Firstenberg <[email protected]> wrote: > We're trying to track down a problem with an ftplet (our logging ftplet, > which we're testing in production) that is totally baffling us. We have a > user that reports that they downloaded a file. As far as we can tell, > neither the beforeCommand() nor afterCommand() methods were called - > although the transfer appears to have succeeded. There are numerous errors > sent to stdout about pipes being closed on either the command or data > channel, so we can't trace them to a specific instance. > > Can anyone think of a way that the file could be transfered without our > ftplet being called? Are there default ftplets that might have told it to > skip further processing before it got to ours? > > Any thoughts about this, or how to track down the problem on a production > server, would be greatly appreciated. > > Thanks! > Allen >
