[ViX_Misc] Unable to go into deep standby after a recording.

[ccs]

I usually set timers to go into deep standby after they've finished.
While investigating a DVB-C/T/T2 problem, I started getting the message...

"Recording(s) are in progress or coming up in a few seconds! Really shutdown now?"

There were no recordings in progress, or due soon, so I put it down to the testing process.
The odd thing is, that if I "Really do shutdown now", the box goes into deep standby and then boots up again about 2 minutes later.
A subsequent deep standby works ok.

However, it's happening all the time now. I tried it out on a backup image from Hades 18, and there were no problems.

I've rebuilt all autotimers from scratch and still it happens.

Netstat shows no outside connections, they should be blocked by the router anyway.

Could the recording that is finishing still be flagged as "in progress".

 

[abu baniaz]

The current approch you ar etaking means someone has tto repliate what you are doing and get exact same results and be able to reproduce it consistently.

You could enable the debug logs, repeat issue and upload them.

 

[ccs]

OK, I'll create a debug log later this afternoon.

 

[ccs]

I created a timer, switched on logging and went into deep standby.

The box switched on, recorded the programme (on bbc2) and asked if it was ok to go into deep standbye. Answer:Yes

"Recording(s) are in progress or coming up in a few seconds! Really shutdown now?" Answer:Yes => Enigma2-19-09-2015_14-12-40.log

Went into deep standby and box rebooted automatically 2 minutes later. => Enigma2-19-09-2015_14-22-54.log

Went straight into deep standby ok.

 

[ccs]

A recording followed by a powertimer to go into deep standby doesn't work either.

The powertimer just keeps pushing the time back and re-trying.

I'll try a clean Hades setup.

 

[ccs]

I've wasted a whole day getting nowhere fast.

Hades 18, basic setup, no settings imported, seems to work.

3.2.005, basic setup, no settings imported, + Ethernet connection + Samba, seems to work.

I say seems, because in the 1st 2 or 3 tests, coming from deep standby, the box boots up for a timer, live tv appears for a few seconds, and then it drops back into standby. The tv goes blank, the recording works ok and the box then goes into deep standby.
But in the next 2 tests, the box didn't drop back into standby before a recording, it stayed on live tv, followed by the dialogue popup to close down, which worked ok, going into deep standby.

3.2.005, flashed from an image I took earlier today, worked ok, dropping into standby as mentioned earlier, but after a few go's, when I powered on from this standby state, the "Recording(s) are in progress or coming up in a few seconds! Really shutdown now?" was back.

I guess someone is going to say re-input all your settings from scratch and see how you go.

 

[Joe_90]

I'm having issues with my MB Twin box booting from deep standby to perform recordings also. They are not exactly the same as your issues, but seem to be related. Is yours an MB Twin also?
When the box boots from deep standby to do a recording it should go into standby mode and perform the recording. After the recording it should go back into deep standby if you are using the default autotimer recording settings. This works fine for me on my Gigablue Quad Plus. On my MB Twin it boots from deep to perform a recording but it goes into normal channel zap mode (not standby). After the recording it remains tuned to the channel and does not go back into deep standby. It is as if enigma is not able to detect that the box was woken by a timer (instead of the remote or power switch). I'm chasing this issue to see if I can find anything in the logs.

 

[ccs]

Mine's an ET10K with 4 DVB-C/T/T2 tuners. It sounds like we're experiencing similar, if not the same, issues.

A clean image appears to be ok, but something eventually triggers the problem, and it doesn't go away.

The 1st debug log I posted earlier in the thread was a boot from deep standby to service a timer, and it certainly didn't drop back into standby during the recording.

 

[Joe_90]

OK - maybe something in enigma has changed which is affecting its ability to detect how it's being booted - from timer or from remote. My GB Quad Plus is fine - just the MB Twin is affected for me, but maybe the ET10K shares some hardware/firmware with the Miraclebox which is causing a common problem. I'll keep digging!

 

[ccs]

To be honest, I'd forgotten the box even dropped into standby after booting for a timer.

Maybe my original problem might be a clue why the box thinks it's been woken up.

 

[ccs]

At about 10:30 last night, I put the box into deep standby, with the usual problem of it rebooting 2 minutes later.
Anyway, I left it in deep standby - it's usually left in this state at this time.

It did a timed recording (about 50 minutes) which started before midnight and ended after midnight. I didn't see what happened,
but it was in deep standby this morning, so I assume it worked ok. It's the only regular recording done at this time.
(I don't ever remember the box being switched on in the morning, but I could be wrong.)

I've now done 5 separate timed recordings, each starting from deep standby and they have all worked as expected, going into standby
during the recording and then into deep standby when it has finished.

Something clearly triggers the original problem, but currently I'm yet to find it/make it happen.
And something has switched it off as well.

 

[DaMacFunkin]

It sounds to me like some sort of WOL problem.

 

[ccs]

I've been wondering that, but there isn't an option in "Network" to switch it on or off.

I've noticed on GitHub today a reference to WOL being excluded from ET10k's, so you could be right.

If/when it goes wrong again I'll disable networking and see what happens.

Odd that it won't go wrong at the moment - can patches be downloaded without me knowing??

What do I do, in theory, to WOL the box?

This morning, I deliberately left my laptop switched off for the first 3 tests, and then switched it on, used WebIf, and then
Windows Explorer in the next 3, but nothing went wrong.

 

[abu baniaz]

Nothing is installed automatically.

 

[birdman]

I have a Power timer set to put the box into Deep Standby after 20 (or 30 - I forget) mins in Standby.
I never does this after 20 mins. It usually does it after several hours (where several is a variable number).
The box doesn't support WOL (and nothing is trying to do it anyway).

Similarly, recordings done from Deep Standby display a variable time before putting the box back to Deep Standby,

 

[ccs]

"Recording(s) are in progress or coming up in a few seconds! Really shutdown now?" eventually came back
last night and is still active this evening.
I've tried stopping Samba and networking altogether, but it's still there.
Next recording wasn't due for 25 minutes.

I've a wakeup power timer at 17:55 for 5 minutes which "does nothing". ie stays switched on.

 

[Joe_90]

Exactly the same happens with the MB Twin. If you force a shutdown after getting the warning message "Recording(s) are in progress..." the box appears to shut down (disk spins down), but the box display stays active. Nothing happens subsequently, never boots back up or performs the recording. I just switched off and manually powered it back on.

 

[twol]

As I recently found out (they fixed the ET8500) WOL is last option in network/network adaptor where you can turn it on ....
... And I have to use an IOS app called wakeup to get the receiver to wake up from deep standby .. Its not that easy.

 

[ccs]

Exactly the same happens with the MB Twin. If you force a shutdown after getting the warning message "Recording(s) are in progress..." the box appears to shut down (disk spins down), but the box display stays active. Nothing happens subsequently, never boots back up or performs the recording. I just switched off and manually powered it back on.

After forcing the deep standby, the et10k sets up a wakeup timer for 2 minutes time, shuts down to deep standby, and then reboot 2 minutes later.
It can then be but back into deep standby without any dialogue.

set wakeup time to 2015/09/19 14:21
recordTimerWakeupAuto True
[XMLTVImport] autostart (1) occured at 1442668850.14
[XMLTVImport] Stop
[AutoTimer] No changes in configuration, won't parse

 

[ccs]

Standby.py

192 		[B]next_rec_time[/B] = -1 
193             [B]if not recordings:[/B] 
194 	                [B]next_rec_time[/B] = session.nav.RecordTimer.getNextRecordingTime() 
195 		if len(jobs): 
196 			reason = (ngettext("%d job is running in the background!", "%d jobs are running in the background!", len(jobs)) % len(jobs)) + '\n' 
197 			if len(jobs) == 1: 
198 				job = jobs[0] 
199 				reason += "%s: %s (%d%%)\n" % (job.getStatustext(), job.name, int(100*job.progress/float(job.end))) 
200 			else: 
201 				reason += (_("%d jobs are running in the background!") % len(jobs)) + '\n' 
202 		if inTimeshift: 
203 			reason = _("You seem to be in timeshift!") + '\n' 
204 		[B]if recordings or (next_rec_time > 0 and (next_rec_time - time()) < 360):[/B] 
205 			default_yes = False 
206 			reason = _("Recording(s) are in progress or coming up in few seconds!") + '\n'

Pure guesswork here, I admit, but it looks like either recordings is true, or next_rec_time is less than 360 secs, neither of which is true in practice.