Hello, we have a system that we are testing in production and I noticed a problem since yesterday. Upon browsing the logs I started tail:ing the main one. The last log entry before was from 09:56 yesterday.
I then generate some more traffic, tail informs me that the file was truncated (ie log4net/rollingfileappender shuffled the logdata around). When I revisit the previous log file (the one before the current one) I find that it only has log entries up until 09:14!! Log data from 09:14 to 09:56 has vanished. I feverishly tried searching but to no avail. In order to avoid this, I wonder: Are there any notes / info that seem applicable? Hopefully, this is a "duh" question! I will go research on my own, just thought I'd start here. Any hints appreciated! Thankyou in advance! /mawi PS (a) Here is end of "latest-1" log file (EOLs truncated for brevity): 2007-05-20 09:14:20,542 [MessageProcessorThread] DEBUG FileProcessor [84]: Will parse file at 2007-05-20 09:14:20,557 [MessageProcessorThread] DEBUG FileProcessor [84]: Will parse file at 2007-05-20 09:14:20,557 [MessageProcessorThread] DEBUG FileProcessor [84]: Will parse file at 2007-05-20 09:14:21,026 [MessageProcessorThread] DEBUG FileProcessor [77]: Parsing complete. (b) Here is output from tail, showing log data before truncating and truncating transition (stuff omitted for brevity): T:\log>tail visionlinklib.log -f at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCa llMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) [...] MonitorService.cs:line 151 2007-05-20 09:56:15,544 [MessageProcessorThread] WARN Dispatcher [104]: Unknown message: No handler wants a message of this type: [...] .Network.Protocol.MessageParsing.NewRollIDRequestMessage. Thanks for trying!|| [...] .Network.Dispatcher.Dispatch( [...] \Dispatcher.cs:104) ==> visionlinklib.log: file truncated <== 2007-05-21 14:42:46,747 [2024] DEBUG MonitorService [106]: Monitor connected.|| [...] .Monitoring.MonitorService.Connect( [...] \MonitorService.cs:106) tail: visionlinklib.log: Invalid argument tail: no files remaining T:\log>tail visionlinklib.log -f [...]
