Hi, It's possible that filter-media had something to do with it, but under normal circumstances it shouldn't.
What is likely here is that something has renamed or replaced the dspace.log file that Tomcat was writing to. As Tomcat retains an open handle on the log file, it will continue writing to the 'old' file, even though you can only see the new one. If you have a dspace.log.1, take a look at it - there is a distinct possibility that your 'missing' log entries may be in there. G Blanco, Jose wrote: > For some reason the dspace.log file is not being written to by dspace. > I ran filter-media around 12:30, and I lost track of when it ended, but > at 1:05 is the last entry in dspace.log from filter-media. Is there any > reason why dspace would stop writing to the dspace.log file under these > circumstances? The permissions look fine: > > -rw-r--r-- 1 dspace dspace 548742 Sep 13 13:05 dspace.log > > I know if I restart tomcat it would start writing again, but why would > it stop? Did running filter-media have something to do with it? > > Thanks! > Jose > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech > This email has been scanned by Postini. For more information please visit http://www.postini.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
