[redring] Show red LED ring when recording in standby + other options...

My redring log is fine

Code:
[RR] Sat May 31 15:09:49 2014: Persistent log starting, v2.12

I'm on CFW 3.00 but it shouldn't make a difference.

Any problems with opening the persistent log, i.e. that within /mod/tmp, will be recorded in the humaxtv.log file - you need to run the debugtv diagnostic to enable that log though.
 
This is mine with redring log zero kB
Code:
>>> Contents of /var/log/humaxtv.log 2.74 KiB
 
Micom Timestamp: 1401559945 - Sat May 31 18:12:25 2014
USER=root
REDRING_fa_blue_level=100
macaddr=
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=BST
VERBOSE=no
[RR] Sat Jan  1 00:00:07 2000: -------------------------------------
[RR] Sat Jan  1 00:00:07 2000: Initialising v2.11
[RR] Sat Jan  1 00:00:07 2000: Got Micom TX fd = 8
[RR] Sat Jan  1 00:00:07 2000: Options 0x67
[RR] Sat Jan  1 01:00:07 2000: Timezone: BST (3600)
[RR] Sat Jan  1 01:00:07 2000: Level:    ha_blue = 0x3f
[RR] Sat Jan  1 01:00:07 2000: Level:    ha_rec = 0xfc
[RR] Sat Jan  1 01:00:07 2000: -------------------------------------
-------------------------------------
Initialising IR3 v1.07
IR3 debug: 0
IR3 Mode: 2 (0x10fa)
IR3 Options: 0
Found at +00000000
getplns() = 0x14af648 (@00000000)
NEXUS_IrInput_Open(00000000, 7fb199e0, 2aab205c, 7fb199fc) = 014bcd38
-------------------------------------
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] Sat May 31 18:12:34 2014: Ring going blue, full boot.
killall: tinyftp: no process killed
[RR] Sat May 31 17:12:34 2014: Recording end 0.
[RR] Sat May 31 17:12:34 2014: Recording end 0.
DRV_DSC_Init_Begin
 
GALIO STARTING
./humaxtv --alt-config /usr/browser/config-ocontroller-si-rootfs.txt --config /var/lib/humaxtv/galio-config.txt
User opts: None
OCON | initialising controller
Restore reminders from file failed
Persist reminders to file failed
IP Address List: 192.168.0.2
mxDLNA [DLNA DMS DmsRunThread] Start (PID:225    TID:1070646480).......
[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] +++++
MEM: used heap 4692648/4702200 flex 821576/25165824
MEM: used heap 4692648/4702200 flex 821576/25165824
MEM: used heap 4692648/4702200 flex 821576/25165824
MEM: used heap 4692648/4702200 flex 821576/25165824
 
Here is one of my humaxtv.logs

Code:
>>> Contents of /var/log/humaxtv.log 5.81 KiB
 
Micom Timestamp: 1401555976 - Sat May 31 17:06:16 2014
USER=root
REDRING_fa_blue_level=100
macaddr=xx:xx:xx:xx:xx:xx
REDRING_ha_blue_level=25
HOME=/
bcmsata2=1
REDRING_fa_rec_level=100
REDRING_ha_rec_level=75
REDRING_fa_vfd_level=25
TERM=vt102
REDRING_sb_led_level=12
REDRING_options=0x0127
PATH=/sbin:/bin:/usr/sbin:/usr/bin
LD_PRELOAD=/var/lib/humaxtv_backup/mod/libdustbin.so /var/lib/humaxtv_backup/mod/libfan.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=BST
VERBOSE=no
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
Waiting for humaxtv to start...
/var/lib/humaxtv/mod/bootstrap.d/setdlnaname: Matched: entry 0 "1.03.12" for process 237.
/var/lib/humaxtv/mod/bootstrap.d/setdlnaname: Next DLNA Server Name is now "Green      ".
[RR] Sat Jan  1 00:00:10 2000: -------------------------------------
[RR] Sat Jan  1 00:00:10 2000: Initialising v2.12
[RR] Sat Jan  1 00:00:10 2000: Got Micom TX fd = 8
[RR] Sat Jan  1 00:00:10 2000: Options 0x127
[RR] Sat Jan  1 01:00:10 2000: Timezone: BST (3600)
[RR] Sat Jan  1 01:00:10 2000: Level:    ha_blue = 0x3f
[RR] Sat Jan  1 01:00:10 2000: Level:    ha_rec = 0xbd
[RR] Sat Jan  1 01:00:10 2000: Level:    fa_vfd = 0x3f
[RR] Sat Jan  1 01:00:10 2000: -------------------------------------
-------------------------------------
Initialising IR3 v1.07
IR3 debug: 0
IR3 Mode:  (0x1000)
IR3 Options: 0
Found at +00000000
getplns() = 0x100ab70 (@00000000)
NEXUS_IrInput_Open(00000000, 7ff419d0, 2aab238c, 7ff419ec) = 01018260
Sat Jan  1 00:00:11 2000 Applying minimum fan speed = 147 (93)
-------------------------------------
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.104...
Lease of 192.168.0.104 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 192.168.0.1
[RR] Sat May 31 17:06:26 2014: Ring going blue, full boot.
[scanFonts:448] [scanFonts:448] [scanFonts:448] 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] ########################################
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] IP Address List: 192.168.0.104
[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
mxDLNA [DLNA DMS DmsRunThread] Start (PID:237    TID:1042617552).......
[ifss_start] +++++
Sat May 31 16:08:21 2014 Applying minimum fan speed = 127 (7f)
Sat May 31 16:10:21 2014 Applying minimum fan speed = 135 (87)
[DtcpFileInfo] using_dtcp=0
PCFile2Open mxfile_openfile ((nil))++++
PCFile2Open mxfile_openfile return(0)and(0x1a43330)----
[RequestRange]Range(bytes=0-) 
[DtcpFileInfo] using_dtcp=0
PCFile2Open mxfile_openfile ((nil))++++
PCFile2Open mxfile_openfile return(0)and(0x17cc830)----
[RequestRange]Range(bytes=0-) 
[DtcpFileInfo] using_dtcp=0
PCFile2Open mxfile_openfile ((nil))++++
PCFile2Open mxfile_openfile return(0)and(0x17baac0)----
[RequestRange]Range(bytes=0-)
 
Redring Ver 2.12 depends on muiltenv ver 1.6 or above being installed, my Humax is running multienv ver 1.7-1, it might be worth checking that you have this package running

Also

I notice both Mihaid and Wallace have [RR] entries in their humaxtv.log files, however, they don't have any [RR] entries after the "DRV_DSC_Init_Begin" line, whereas I have a lot of [RR] entries immediately after this line
 
FWIW. I have multienv ver 1.7-1 installed on both boxes. Both units are set up identically, both in the packages installed and the way the packages are configured.
 
Just to add, apart from the odd 'blue ring in the morning' (no jokes please), redring is working fine, on both boxes. It is just that the log is not being written to.
 
Ooh. Just had a look to see the size of my log (#86KiB) and noticed my log restarted itself yesterday evening.
Looking back it seems to have done this many times. First ever entry is 31 Jan 2013 and there are gaps of anything from a couple of days to several weeks scattered from 1 Feb 2013 across the period to date. Versions 2.10, 2.11 and 2.12 are all involved.
And no, they don't correspond to the box not being used while on holidays, or suchlike.
 
Any problems with opening the persistent log, i.e. that within /mod/tmp, will be recorded in the humaxtv.log file - you need to run the debugtv diagnostic to enable that log though.
Can you see any of these problems in my humaxtv log in post 362?
 
As stated in #364, the difference I see in my humaxtv.log are the 70 odd [RR] entries that follow DRV_DSC_Init_Begin e.g. :-

Code:
DRV_DSC_Init_Begin
[RR] Sat Jan  1 01:00:11 2000: -> LEDControl(0x10) 00 00 80 01
[RR] Sat Jan  1 01:00:11 2000:    [ USB = ON ]
[RR] Sat Jan  1 01:00:11 2000: +> LEDControl(0x10) 00 00 80 01
[RR] Sat Jan  1 01:00:11 2000:    [ USB = ON ]
[RR] Sat Jan  1 01:00:11 2000: !> LEDControl(0x10) 00 00 80 01
 
NOTE 60 [RR] entries removed from here
 
[RR] Mon Jun  2 17:57:50 2014:    [ Timer Clock = ON ]
[RR] Mon Jun  2 17:57:50 2014: !> LEDControl(0x10) 00 08 00 01
[RR] Mon Jun  2 17:57:50 2014:    [ Timer Clock = ON ]
[scanFonts:448] [scanFonts:448] [scanFonts:448] [AP_BrowserManager_Proc:608] [AP_BrowserNetTime_startNetTimeTask:171] [AP_BrowserNetTime_startNetTimeTask:208]
[RR]: Switched to persistent log file.

Note the last entry " [RR]: Switched to persistent log file."
 
The majority of the 70 odd lines are normal RR entries and are not significant, however there must be a switch over from entering [RR] into the humaxtv.log and the (persistent) redring.log, because I only get stuff in the redring.log after the [RR]: Switched to persistent log file line at Mon Jun 2 17:57:50 2014, e.g. :-

Code:
[part of redring.log]
 
[RR] Mon Jun  2 04:44:22 2014: +> RingBrightness(0x1a) 1d
[RR] Mon Jun  2 04:44:22 2014: !> RingBrightness(0x1a) 1d
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Mon Jun  2 17:57:53 2014: Persistent log starting, v2.12
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
[RR] Mon Jun  2 17:57:54 2014: -> LEDControl(0x10) 00 80 00 01
[RR] Mon Jun  2 17:57:54 2014:    [ Disk space 1 = ON ]
[RR] Mon Jun  2 17:57:54 2014: +> LEDControl(0x10) 00 80 00 01
[RR] Mon Jun  2 17:57:54 2014:    [ Disk space 1 = ON ]
 
Sorry Ezra, still no idea. All I know is that redring is working but it ain't writing a log. I have no idea why. It's the same on both my boxes. It's obviously not important, but it would be nice to find out why.
 
And that means?
It is important to me because it could have pointed me to why failed recording occurred, when the rs log stopped logging recordings made.
 
Maybe af123 will throw some light onto it
Not from any of the output posted so far unfortunately but redring can only start logging to the persistent log (the one on the hard disk rather than in memory) once the disk has come online. Redring starts with the standard Humax software which is before the disk is even powered on but whenever it writes out a log line it checks to see if it can switch to logging to disk.
If all log entries continue to go to humaxtv.log then it could be due to one or more of the following:
  • Cannot open the log file on disk for append;
  • Redring options failed to load properly;
  • The non-persistent-log debug flag is set in the configuration.
None of these possible causes seem likely from the log file extracts posted though!
 
So where does that leave us? Since redring log not logging and rs log not logging recordings made, can I conclude that my CF is screwed somehow?

Also I was wondering, the other guys with bad redring logs, could you check the rs recent events log on rs webpage to see if your logs include recordings made?
 
HDR [Green] has not been used to record anything in a while so I cannot use that as a guide. However, HDR [Orange] has been used. It recorded two programmes last night. Both have been correctly manipulated. I.E. shrunk and decrypted on the HDR as expected.

There are also corresponding entries in the rs.hpkg.tv (Remote Scheduling) site. So that seems to be working for me.
 
Would you believe it, redring log started by itself on Monday. And also the log on rs started logging recordings again on Saturday.
 
Back
Top