redring log

mihaid

Well-Known Member
is there a way to get what is inside the dotted line time period?
[RR] Mon Oct 13 22:01:37 2014: Recording end 31.
[RR] Mon Oct 13 22:01:37 2014: Changing to red.
[RR] Mon Oct 13 22:02:30 2014+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Fri Oct 17 15:37:39 2014: Persistent log starting, v2.15
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Fri Oct 17 15:37:39 2014: Play icon on.
[RR] Fri Oct 17 15:57:49 2014: Play icon off.
 
Before the hard disk has spun up and come online, log entries go to /tmp/humaxtv.log but they are lost on reboot.
 
I'm not sure what you want to achieve, what is the problem?
BTW
af123 wrote redring, so he is the No. 1 authority on it. it is possible to filter the redring log into another file, I archive only certain lines into a my-redring.log like this :-
Code:
[RR] Mon Oct 13 17:59:15 2014: Persistent log starting, v2.15
[RR] Mon Oct 13 19:02:05 2014: Recording start 42:'/mnt/hd2/My Video/The Gadget Show/New_ The Gadget Show_20141013_1902.nts'
[RR] Mon Oct 13 19:02:05 2014:    Recording 1
[RR] Mon Oct 13 19:55:48 2014: Recording end 42.
[RR] Mon Oct 13 20:28:00 2014: Recording start 43:'/mnt/hd2/My Video/Gadget Man/Gadget Man_20141013_2028.nts'
[RR] Mon Oct 13 20:28:00 2014:    Recording 1
[RR] Mon Oct 13 21:09:59 2014: Recording end 43.
[RR] Mon Oct 13 21:58:00 2014: Recording start 43:'/mnt/hd2/My Video/8 Out of 10 Cats/8 Out of 10 Cats_20141013_2158.nts'
[RR] Mon Oct 13 21:58:00 2014:    Recording 1
[RR] Mon Oct 13 22:01:43 2014: Recording start 34:'/mnt/hd2/My Video/Never Mind the Buzzcocks/Never Mind the Buzzcocks_20141013_2201.nts'
[RR] Mon Oct 13 22:01:43 2014:    Recording 2
[RR] Mon Oct 13 22:01:43 2014:    Changing to purple.
[RR] Mon Oct 13 22:31:53 2014: Recording end 34.
[RR] Mon Oct 13 22:31:53 2014:    Changing to red.
[RR] Mon Oct 13 22:54:59 2014: Recording end 43.
[RR] Tue Oct 14 01:34:55 2014: Standby ring dim detected.
[RR] Tue Oct 14 01:34:55 2014: Standby ring dim detected.
[RR] Tue Oct 14 01:34:55 2014: Ring trying to go amber.
[RR] Tue Oct 14 01:34:55 2014:   Changing to dim blue.
[RR] Tue Oct 14 01:34:57 2014: Standby ring dim detected.
 
mihaid seems to have gone into terse mode lately. I'll take a guess he means the rows of + symbols in post 1 - what do they mean, what's causing them, and is there a bug causing meaningful text to come out garbled.
 
No, I took it that the log stops on Monday then pluses instead of real red ring entries and it only resumes logging on Friday. My question is why the entries from Monday to Friday don't get logged. There sure were some.
 
There is something missing in your Redring log but it is not 'inside the dotted line time period', the +++ persistent log +++ can be rearguard as a single entry that is sent at the same time, in your case at Fri Oct 17 15:37:39 2014. the missing data is between 'Mon Oct 13 22:02:30 2014' and the first '+' when Redring stopped logging for some reason, the first line of '+++' extends beyond the other lines because at the end of the missing text there would have been a 'new-line' character, placing the '+++' on a new line
 
Code:
[RR] Sat Oct 18 03:35:33 2014: Standby ring dim detected.
[RR] Sat Oct 18 03:35:33 2014: Ring trying to go amber.
[RR] Sat Oct 18 03:35:33 2014:   Changing to dim blue.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Mon Oct 20 16:38:48 2014: Persistent log starting, v2.15
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Mon Oct 20 16:38:48 2014: Play icon on.
[RR] Mon Oct 20 17:15:59 2014: Play icon off.
There is something missing in your Redring log but .......... when Redring stopped logging for some reason,
I seem to get these missing bits regularly. Can something be done to correct that behaviour?
 
I'm wondering if there could be a problem because your Redring log is too big, what size is displayed against it?, If you don't mind losing the old data you could try 'Clearing' the redring.log to see if that fixes the problem

upload_2014-10-27_12-43-24.png

Note:- You won't have a redring-old.log on your humax, this is something I have created
 
redring-old.log(679.9 KiB) Clear
redring.log(108.26 KiB) Clear

is that too big?
Also would clearing actually work or it will be for nothing.
 
No 108 KiB is very small, I have had logs up 10 MiB with no trouble, I wasn't aware that the standard Redring produced redring-old.log files, mine was generated by a script I wrote, I guess this is a new feature af123 has built in. Clearing the log is worth a try, but the file isn't too big. You could reinstall the package with Web-If >> Diagnostics >> Package redring Force re-install
 
Last edited:
so just to make sure I understood you. Your redring log does not have periods when events are not logged or the +++++++++++++++ line.

what redring version and what CF version you're on?
 
No, under normal circumstances all events are logged, with the exception of the very last entries before the unit goes into standby as there is no time to store them before shut down, this is usually only a message saying that the front LED is going to amber

the +++ lines are logged every time the Humax turns on from standby, they do not indicate missing text, e.g. :-

Code:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Tue Oct 28 17:53:23 2014: Persistent log starting, v2.16
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
As you can see above I am on the latest Redring version, 2.16
 
I have force reinstalled redring 2.16 and the log stopped on 20 Nov. is there a way to restart it?
 
Can someone tell him that I'm not interested in his monologues?

the installation of redring 16 seems to have no influence on the log starting. I can't quite remember how I ended up with redring old log. would clear restart the log?
 
Back
Top