Activity log inconsistencies

peterworks

peterworks

Ye Olde Bowler
Edit: I initially thought there was a problem with 'recent activity' in RS. I have now realised that it is a problem writing to the activity log in WebIf. I have changed the title to reflect this

I have two HDR Foxes both connected to RS. I have found that on Fox 1 all recordings made are displayed in the recent activity (as shown in attached). On Fox 2 it doesn't always show. For instance I recorded Elton John at Glastonbury last night at 21:00 but it does not show (as shown in attached). Not really a problem as such but I do use RS to ensure recordings have been made and, because of this inconsistency, I have to log on to Fox 2 to ensure it has recorded.
Any ideas please ?

Humax 1 recent activity.jpgHumax 2 recent activity.jpg
 
Last edited:
Does running the rs/diskpush diagnostic make it better?
I just tried a test recording, followed by the above and it appears instantly. Same for deleting it. If that works for you, then it's something odd happening on your box 2.
The contents of /mod/tmp/rs.log are of course useful as well to determine what is or isn't attempting to happen and when.
 
I ran rs/diskpush but the recording did not appear.
I have just done a recording which showed up in recent activity. I then deleted the recording, did the diskpush and the recording shows in the deleted folder.
The rs.log does not show the diskpush - it only displays what happened when it turned on at 4:10 this morning (I schedule it to come on at that time for 40 minutes to decrypt/shrink, etc).
 
Did it say something like "Sending disk information to remote server. Already up-to-date." or something else?
rs.log doesn't record results of diagnostics.
 
Here are the rs.log entries for the last three days.
24/06/2023 04:11:01 - Sending channel information to remote server.
24/06/2023 04:11:01 - Updating...
24/06/2023 04:13:16 - Sending disk information to remote server.
24/06/2023 04:13:16 - Already up-to-date.
24/06/2023 04:13:44 - Sending disk error information to remote server.
24/06/2023 04:13:44 - >>> Ok.
24/06/2023 12:18:47 - Processing command 'schedule '
24/06/2023 12:18:47 - *Schedule 8330/11170/2/26/ITV4/1687640400/World Rugby U20 Championship...
24/06/2023 12:18:48 - *Trying source service/event ID.
24/06/2023 12:18:49 - _Found event - World Rugby U20 Championship...
24/06/2023 12:18:50 - _Successfully scheduled event.
24/06/2023 12:18:55 - push
24/06/2023 12:18:55 - Sending TBL_RESERVATION schedule information to remote server.
24/06/2023 12:18:55 - Updating...
24/06/2023 12:18:55 - Sending skiplist information to remote server.
24/06/2023 12:18:55 - >>> Skipped 0.
24/06/2023 12:18:55 - Sending pending schedule information to remote server.
24/06/2023 12:18:55 - Already up-to-date.
24/06/2023 12:18:56 - ds 906.06 GiB 12.4 GiB 1 893.65 GiB
24/06/2023 12:18:56 - Already up-to-date.
25/06/2023 04:10:39 - Sending channel information to remote server.
25/06/2023 04:10:39 - Already up-to-date.
25/06/2023 04:13:39 - Sending disk information to remote server.
25/06/2023 04:13:39 - Updating...
25/06/2023 04:14:34 - Sending disk error information to remote server.
25/06/2023 04:14:34 - >>> Ok.
25/06/2023 10:42:07 - Error encountered, Error: 7 - Couldn't connect to server
26/06/2023 04:10:31 - Sending channel information to remote server.
26/06/2023 04:10:31 - Already up-to-date.
26/06/2023 04:13:04 - Sending disk information to remote server.
26/06/2023 04:13:04 - Updating...
26/06/2023 04:13:32 - Sending disk error information to remote server.
26/06/2023 04:13:32 - >>> Ok.
27/06/2023 04:10:22 - Sending channel information to remote server.
27/06/2023 04:10:22 - Already up-to-date.
27/06/2023 04:13:18 - Sending disk information to remote server.
27/06/2023 04:13:18 - Updating...
27/06/2023 04:13:58 - Sending disk error information to remote server.
27/06/2023 04:13:58 - >>> Ok.
Click to expand...
 
Here is an update to the Recent Activity screen:

Capture 27-06-2023 12_23_28.jpg
I should point out that the system boot on 25th at 20:58 was for the recording of Elton John and the system boot on 27th at 07:43 was for a recording of Super League.
 
The Alfred Hitchcock recording was done when the box was on. I have just tried another recording with the box in standby and recent activity does not show 'Recorded' although it does show when the box came out of standby.
I ran the rs/diskpush and the recording was there in RS. I deleted the recording, another diskpush and the recording showed in the dustbin. I then removed the recording from the dustbin, another diskpush and the recording was gone.
The activity log on the box reflects the 'recent activity' (is that what is copied ?).
 
Looking at the activity log Fox 2 worked fine until it had only a few recordings.

Fox 1 = 2Tb (443.89 GiB Used) - over 200 recordings
Fox 2 = 1Tb (19.28 GiB Used) - 3 recordings

Could it be a timing issue ?
Fox 1 closes down in > 10 seconds when put into standby
Fox 2 closes down in < 5 seconds when put into standby
Possibly the housekeeping does not have time to complete ? (or am I going down a dead-end !)
 
peterworks said:
Looking at the activity log Fox 2 worked fine until it had only a few recordings.

Fox 1 = 2Tb (443.89 GiB Used) - over 200 recordings
Fox 2 = 1Tb (19.28 GiB Used) - 3 recordings

Could it be a timing issue ?
Fox 1 closes down in > 10 seconds when put into standby
Fox 2 closes down in < 5 seconds when put into standby
Possibly the housekeeping does not have time to complete ? (or am I going down a dead-end !)
Click to expand...
For me, I find that the time it takes for a normal tidy close down is related to the used space on 'My Video'.
So, in your example, if your Fox 2 were to be populated to the same degree as the other one, it'll take similar time to shut down.
 
Last edited:
prpr said:
so what EXACTLY is not working?
Click to expand...
The activity log on Fox 2 is not being updated when a recording is successful but is done in standby. Doing a recording on Fox 2 when the box is on shows in the activity log. I did a power off/on yesterday on both boxes. Fox 1 showed 'System booted (Power cycle)' in the activity log but Fox 2 did not. 'Recent activity' in RS correctly reflects the activity log.
Perhaps I should change the title ?
 
peterworks said:
The activity log on Fox 2 is not being updated when a recording is successful but is done in standby. Doing a recording on Fox 2 when the box is on shows in the activity log. I did a power off/on yesterday on both boxes. Fox 1 showed 'System booted (Power cycle)' in the activity log but Fox 2 did not. 'Recent activity' in RS correctly reflects the activity log.
Perhaps I should change the title ?
Click to expand...
The network is not active when in standby so it is not surprising that RS is not being updated for such recordings, hopefully it should be updated shortly after the box wakes up
 
peterworks said:
Fox 1 showed 'System booted (Power cycle)' in the activity log but Fox 2 did not
Click to expand...
Then the network is not coming up for whatever reason. You can read the code in /mod/etc/init.d/S55rs - it sits in an endless loop.
MymsMan said:
it is not surprising that RS is not being updated for such recordings
Click to expand...
Indeed.
hopefully it should be updated shortly after the box wakes up
Click to expand...
With the then current activity. Any previous intervening activity in standby or for other non-functional network reasons since last active doesn't get retrospectively logged.
 
I have done some testing and found the following:
I made 12 recordings (22.07 GiB) yesterday afternoon/evening. I then did a recording this morning with the box in standby and the activity log updated correctly. The box now takes longer to shutdown after the recording completes. I will do another recording this morning (whilst in standby) and, if the same happens, then, perhaps, it is a timing issue whereby the box shuts down before the activity log can be updated.

Edit: I am not sure how to state the difference between standby when the box is off and standby when the box is awake waiting to start the recording. The recordings I refer to are in the latter standby situation.
 
Are these boxes wired or wireless?
peterworks said:
perhaps, it is a timing issue whereby the box shuts down before the activity log can be updated.
Click to expand...
Does the entry in /mod/tmp/activity.log show up? This is identical to the log entry transmitted to the RS server, and presumably/possibly/maybe the WebIf one happens just after the RS one (depends how recmon works).
Perhaps because you have so few recordings on this box it is indeed shutting down early. As bottletop said, more recordings means longer shutdown time.
 
No the entry does not show up in /mod/tmp/activity.log:
29/06/2023 04:07:28 - System booted (Scheduled event).
29/06/2023 04:12:29 - Automatically upgraded package tmenu from 1.22 to 1.24
29/06/2023 04:12:30 - Automatically upgraded package auto-update from 2.0.5 to 2.0.6 (Also update additional data)
29/06/2023 06:42:30 - System booted (Scheduled event).
29/06/2023 09:53:15 - System booted (Remote control handset).
29/06/2023 09:53:58 - Scheduled Countryfile Summer Diaries @ 1688031000
29/06/2023 10:12:28 - System booted (Scheduled event).

but it does in 'recent activity'.
Capture 29-06-2023 11_14_51.jpg
 
Looking at the activity log on box I have noticed another inconsistency. I unscheduled 2 entries and the activity log shows 'Scheduled' instead of unscheduled:

29/06/2023 12:17:36 - System booted (Scheduled event).
29/06/2023 12:19:06 - Scheduled Spy in the Ocean @ 1687716000
29/06/2023 12:19:11 - Scheduled New: A Country Life for Half... @ 1687723200

whereas 'recent activity' shows:
Capture 29-06-2023 12_28_20.jpg
 
prpr said:
Are these boxes wired or wireless?
Click to expand...
Sorry I missed this question. They are both wired (through a switch to a TP-Link powerline adapter).
Also I have often wondered what recmon does. The log has not been updated since April this year and shows only 5 entries, all saying 'Terminated'
 
You must log in or register to reply here.
Back
Top