redring log

mihaid said:
Can someone tell him that I'm not interested in his monologues?
Click to expand...
Can I take it that nothing I have ever written has been of any use to you? That cuts out Things Every..., guides to decryption, CF installation, HDD recovery....

Besides, it was a perfectly valid (if slightly obscure) response to the detail of your post - I take it you didn't even twig when I spelled it out. Your refusal to engage with me doesn't make my post a monologue.
 
MartinLiddle said:
I think what he is trying to establish is when the log stopped updating; was it 20th November 2013 or 20th October 2014 or some other date?
Click to expand...
I think that anyone that read this thread and looked at the logs I already posted would understand that the log stopped not on 20 Nov, mistakenly, but 20 Oct 2014. A simple, do you mean October would have sufficed.
Also why does it matter when it stopped when my main concern is that the installation of v16 does not restart the log. Main question is why? and what else can be done to restart it.
 
There is a log that stores problems for redring called humaxtv.log, to enable this log goto Web-If >> Diagnostics >> Run Diagnostic >> debugtv >> run. When this log is running, you can examine it with Web-If >> Diagnostics >> Run Diagnostic >> View Log Files >> humaxtv.log, here is part of the log :-
Code: 
>>> Contents of /var/log/humaxtv.log 11.19 KiB

DRV_DSC_Init_Begin
[RR] Sat Jan  1 00:00:11 2000: -> ???(0x8)
[RR] Sat Jan  1 00:00:11 2000: +> ???(0x8)
[RR] Sat Jan  1 00:00:11 2000: !> ???(0x8)
[RR] Sat Jan  1 00:00:11 2000: -> ???(0x17) 01 03 0c
[RR] Sat Jan  1 00:00:11 2000: +> ???(0x17) 01 03 0c
[RR] Sat Jan  1 00:00:11 2000: !> ???(0x17) 01 03 0c
[RR] Sat Jan  1 00:00:11 2000: -> LEDControl(0x10) 00 00 80 01
[RR] Sat Jan  1 00:00:11 2000:    [ USB = ON ]
[RR] Sat Jan  1 00:00:11 2000: +> LEDControl(0x10) 00 00 80 01
[RR] Sat Jan  1 00:00:11 2000:    [ USB = ON ]
[RR] Sat Jan  1 00:00:11 2000: !> LEDControl(0x10) 00 00 80 01
[RR] Sat Jan  1 00:00:11 2000:    [ USB = ON ]
route: SIOCADDRT: File exists
[RR] Sat Jan  1 00:00:14 2000: -> GetClock(0x4)
[RR] Sat Jan  1 00:00:14 2000: +> GetClock(0x4)
[RR] Sat Jan  1 00:00:14 2000: !> GetClock(0x4)
[RR] Sat Jan  1 00:00:14 2000: -> GetClock(0x4)
[RR] Sat Jan  1 00:00:14 2000: +> GetClock(0x4)
[RR] Sat Jan  1 00:00:14 2000: !> GetClock(0x4)
[RR] Mon Nov  3 17:41:42 2014: -> LEDControl(0x10) 00 00 04 01
[RR] Mon Nov  3 17:41:42 2014:    [ FULL = ON ]
[RR] Mon Nov  3 17:41:42 2014: +> LEDControl(0x10) 00 00 04 01
 
Ezra Pound said:
There is a log that stores problems for redring called humaxtv.log, to enable this log goto Web-If >> Diagnostics >> Run Diagnostic >> debugtv >> run. When this log is running, you can examine it with Web-If >> Diagnostics >> Run Diagnostic >> View Log Files >> humaxtv.log, here is part of the log :-.
Click to expand...
here is that diagnostic, I've had humaxtv already running
Code: 
Micom Timestamp: 1415027847 - Mon Nov  3 15:17:27 2014
USER=root
REDRING_fa_blue_level=100

REDRING_ha_blue_level=25
HOME=/
IR3_MODE=2
bcmsata2=1
REDRING_fa_rec_level=100
REDRING_ha_rec_level=100
REDRING_fa_vfd_level=100
TERM=vt102
REDRING_sb_led_level=12
REDRING_options=0x0067
PATH=/sbin:/bin:/usr/sbin:/usr/bin
LD_PRELOAD=/var/lib/humaxtv_backup/mod/libdustbin.so /var/lib/humaxtv_backup/mod/libir3.so /var/lib/humaxtv_backup/mod/libredring.so
SHELL=/bin/sh
REDRING_sb_vfd_level=12
DUSTBIN_PATH=[Deleted Items]
PWD=/
IR3_OPTIONS=0
REDRING_TZ=GMT
VERBOSE=no
[RR] Sat Jan  1 00:00:08 2000: -------------------------------------
[RR] Sat Jan  1 00:00:08 2000: Initialising v2.16
[RR] Sat Jan  1 00:00:08 2000: Got Micom TX fd = 8
[RR] Sat Jan  1 00:00:08 2000: Options 0x67
[RR] Sat Jan  1 00:00:08 2000: Timezone: GMT (0)
[RR] Sat Jan  1 00:00:08 2000: Level:    ha_blue = 0x3f
[RR] Sat Jan  1 00:00:08 2000: Level:     ha_rec = 0xfc
[RR] Sat Jan  1 00:00:08 2000: -------------------------------------
-------------------------------------
Initialising IR3 v1.07
IR3 debug: 0
IR3 Mode: 2 (0x10fa)
IR3 Options: 0
Found at +00000000
getplns() = 0x100ad98 (@00000000)

-------------------------------------
Initialising Dustbin v1.0
Dustbin debug: 0
Dustbin media root: /mnt/hd2/My Video/
Dustbin path: /mnt/hd2/My Video/[Deleted Items]
-------------------------------------
udhcpc (v1.20.2) started
udhcpc deconfig  eth0  0.0.0.0
Sending discover...
Sending select for 192.168.0.2...
Lease of 192.168.0.2 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 192.168.0.1
[RR] Mon Nov  3 15:17:36 2014: Ring going blue, full boot.
killall: tinyftp: no process killed
[RR] Mon Nov  3 15:17:36 2014: Recording end 0.
-------------------------------------
Initialising Dustbin v1.0
Dustbin debug: 0
Dustbin media root: /mnt/hd2/My Video/
Dustbin path: /mnt/hd2/My Video/[Deleted Items]
-------------------------------------
[RR] Mon Nov  3 15:17:36 2014: Recording end 0.
DRV_DSC_Init_Begin
[P_MEDIA_CheckValidMediaId] Invalid Media ID.
[DI_MEDIA_MP_GetStreamInfo] Error - Invalid Media Id.
[AP_BrowserManager_Proc:608] [AP_BrowserNetTime_startNetTimeTask:171] [AP_BrowserNetTime_startNetTimeTask:208] [AP_BrowserManager_Proc:733] [scanFonts:448] [scanFonts:448] [scanFonts:448] ########################################
Domain      :.humaxtvportal.com
CertPath    :htvdev_portal_ccert_2k_20101106.p12
###### New Cert is Added
########################################
########################################
Domain      :none
CertPath    :humax_tvportal_rootcert_2k_20101106_pub.pem
###### New Cert is Added
########################################
########################################
Domain      :.bbc.co.uk
CertPath    :hdrfoxt2_20101001.p12
###### New Cert is Added
########################################
########################################
Domain      :.bbc.co.uk
CertPath    :rootcert_1k.pem
###### New Cert is Added
########################################
[syncBoxInfo:1240] [RR]: Switched to persistent log file.
IP Address List: 192.168.0.2
mxDLNA [DLNA DMS DmsRunThread] Start (PID:232    TID:1043317968).......
[mxDlnaFileScanner_create] +++++
[mxDlnaFileScanner_addDirectory] SEARCH_LIST_PATH_EXACT_MATCHED
[mxDlnaFileScanner_create] -----
[mxDlnaFileScanner_addDirectory] SEARCH_LIST_PATH_EXACT_MATCHED
[mxDlnaFileScanner_addDirectory] SEARCH_LIST_PATH_EXACT_MATCHED
[mxDlnaFileScanner_addDirectory] SEARCH_LIST_PATH_EXACT_MATCHED
[ifss_start] +++++
[AP_BrowserManager_Proc:703] [AP_BrowserManager_Proc:733] scanThread END----------------
thread detach 1045415120
[ifss_start] +++++
DB InPut Success =/mnt/hd2/My Video/[Deleted Items]/Have I Got a Bit More News for You (I:0/F:0)
[P_MEDIA_ProbeOpen] Error>> unknown stream format|
[DI_MEDIA_Probe] Error - Fail in P_MEDIA_ProbeOpen
DB InPut Success =/mnt/hd2/My Video/[Deleted Items]/Have I Got a Bit More News for You/Have I Got a Bit More News for You_20141020_2237.ts (I:0/F:1)
Error>> Cannot support video format
[DI_MEDIA_Probe] Error - Fail in P_MEDIA_ProbeOpen
DB Remove Success =/mnt/hd2/My Video/Have I Got a Bit More News for You/Have I Got a Bit More News for You_20141020_2237.ts (I:0)
scanThread END----------------
thread detach 1045415120
[ifss_start] +++++
DB InPut Success =/mnt/hd2/My Video/Holiday of My Lifetime with Len Goodman/Holiday of My Lifetime with Len Goodman_20141103_1544.ts (I:0/F:0)
 
I am a recent convert to redring. I installed it on four units, two weeks ago. One unit logged for two days until stopping on October 22nd, the other three don't record log entries. If you enable debugging in the settings page and reboot then logging starts, but it stops again if you disable this setting. I have tried removing and reinstalling the package, running the fix-flash-packages diagnostic, force reinstalling etc. without success. One of the units had other problems, so before installing redring I removed the custom firmware, packages and settings (RMA), reset the unit to factory defaults and reinstalled the CFW from scratch: no redring log.
The redring preferences are in the file 'redring.conf' in '/mod/boot'. If debugging is enabled the last line of the file reads 'options 0x8027', if disabled it reads 'options 0x0027'. Could someone who has redring with standard logging working correctly confirm that the last line of the file reads 'options 0x0027'.
 
Here is the contents of my 'working' redring.conf :-
Code: 
humax# cat redring.conf
sb_led_level 20
ha_rec_level 50
sb_vfd_level 20
fa_vfd_level 50
fa_blue_level 70
fa_rec_level 70
ha_blue_level 25
# blue, red, debug, purple
options 0x8007
I think there can be many combinations in the last line 'options', I think they specify all the things you can change, e.g.blue, red, debug, purple etc.
 
Last edited:
mihaid said:
here is that diagnostic, I've had humaxtv already running
Click to expand...
I don't pretend to understand all the stuff in humaxtv.log but you don't seem to have any [RR] entries after the 'DRV_DSC_Init_Begin' line, where as I have the lines in #23
 
It looks like a bug in redring 2.16. If you turn on debugging the logging works (last line in redring.conf = options 0x8027) turn it off and it doesn't (last line = options 0x0027). The last line in redring.conf should be 'option 0x8007' - thanks Ezra: if you edit the file manually and change to this value then reboot, logging to redring.log recommences.

Edit: it might not be as simple as this, my conf file settings don't match the settings page now.
 
Last edited:
I was being a bit hasty, the digit '8' after 'x' in e.g. 'options 0x8007' appears to correspond to debug mode (it also says debug in the line above). A zero in the place of the eight means no debugging. So I have not solved the problem :( Ezra's log is working, but he has debugging switched on. Logging works if you have debugging enabled but stops if you switch this off. What extra entries are logged in debug mode that are not in standard mode (when it is working correctly, of course)?
 
Last edited:
You're right in that the 8 for the first digit means debug mode. The options is a set of flags and the line directly above starting with a # shows you which options are enabled in your configuration - usually more readable than the hexadecimal flags.

From looking at the code, you should be getting messages even without debugging enabled including those about recordings starting and stopping. Does look like a bug somewhere. Knowing that it only occurs when debug mode is off should let me track it down though, thanks!
 
af123 said:
You're right in that the 8 for the first digit means debug mode. The options is a set of flags and the line directly above starting with a # shows you which options are enabled in your configuration - usually more readable than the hexadecimal flags.

From looking at the code, you should be getting messages even without debugging enabled including those about recordings starting and stopping. Does look like a bug somewhere. Knowing that it only occurs when debug mode is off should let me track it down though, thanks!
Click to expand...
So it's a matter of wait to see what af does next?
 
Well, if you don't want to wait you could just upgrade your redring package to version 2.17...
 
Done & fixed ( at least for me, the non-logging issue I had with V2.16)
humax# cat redring.log
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Tue Nov 4 11:28:00 2014: Persistent log starting, v2.17
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Tue Nov 4 11:28:00 2014: Recording start 39:'/mnt/hd2/My Video/BBC World News_20141104_1128.nts'
[RR] Tue Nov 4 11:28:00 2014: Recording 1
[RR] Tue Nov 4 11:28:00 2014: REC icon on.
 
My log started as well last night. There seem to be missing a few entries in v16. Then v17 kicked in. I'll monitor this.
 
You must log in or register to reply here.
Back
Top