On Wed, Jun 8, 2011 at 2:03 AM, Niklas Gustavsson <[email protected]>wrote:
> On Wed, Jun 8, 2011 at 3:32 AM, 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. > > Is it consistent in that some commands are never logged, or just on > some sessions? > Just on some sessions, as far as we can tell. We can't figure out exactly the circumstances that it happens. At the moment we have one known documented case where a file appears to have been downloaded and no record of it happening was recorded. We also seem to have a (related?) situation where "something" is happening on the server that is forcing hte client to close the connection. The client program isn't very yielding on what or why, but its become frustrating that it happens rarely and there is nothing logged that indicates what might be going on. > > 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? > > No, there are no default Ftplets. > Thanks. That helps rule out some possibilities. Allen
