Don Lee Posted June 3, 2012 Report Share Posted June 3, 2012 Running Retro 9.0.2.107 Several times now, I have seen crashes of the engine when a number of activities were active. The log(s) end up containing absolutely no indication that these activities started. The only record that I have that anything happened is the email sent by the engine, and the results of the activities - like the content of the media sets. It is distressing that any activities that were active at the time of the crash do not appear - at all - in the retrospect logs. I consider this a bug. Logs should contain a complete picture of activity. It is highly undesirable that they are "unreliable", which retro logs are, in the face of engine crashes. I would presonally much prefer a retro log that has each line tagged with the activity thread, and may be written in a non-obvious order. This would make the log hard to read, but would allow the engine to insert log entries *immediately* at all times, so the log would be useful for debugging. It is not a big deal, at least for me, to have to sort the log to see the activity by thread. The way it is, it appears that the engine buffers all the log output until the script is complete, with the result being that the activity does not appear in the log AT ALL if it crashes. 1 Quote Link to comment Share on other sites More sharing options...
twickland Posted June 4, 2012 Report Share Posted June 4, 2012 I consider this a bug. Retrospect has long had an issue of delays in sweeping information from whatever internal buffer it's using to the log. In Retrospect 6 and earlier, if a running script had a lot of sources and the backup computer experienced a crash, the log would often fail to list many backups that had actually completed before the crash, let alone the one that was in progress at the time of the crash. In this regard, Retro 8/9 has actually been improved. While what you're asking for is quite reasonable and would be helpful to many, i suspect that Retrospect (the company) would probably consider it a feature request rather than a bug. Quote Link to comment Share on other sites More sharing options...
redleader Posted August 27, 2012 Report Share Posted August 27, 2012 Same here :-( Quote Link to comment Share on other sites More sharing options...
Daniels Posted August 28, 2012 Report Share Posted August 28, 2012 I have the same problem with 8.2 Quote Link to comment Share on other sites More sharing options...
redleader Posted August 28, 2012 Report Share Posted August 28, 2012 We ALL need to submit support tickets, as I'm told this is just a Public Chat Forum and not monitored by Retrospect themselves very well :-O !! http://retrospect.com/support/contact Quote Link to comment Share on other sites More sharing options...
Don Lee Posted January 16, 2013 Author Report Share Posted January 16, 2013 UBD - never mind. Thought I had a new incident of this, but it's not what I thought. (too bad I can't delete this new entry....) Quote Link to comment Share on other sites More sharing options...
Daniels Posted January 17, 2013 Report Share Posted January 17, 2013 Same here with 8.2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.