Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Duo] Autobouquetsmaker issue (n/a channels)

  • Thread starter Thread starter siross
  • Start date Start date
Thanks for reporting.
It looks like the settings are not being saved on stopping E2.

Yeah I thought it was something like that.

I appreciate you need logs to look at things(I'm was in the software programming business in a previous job, different language tho). I have to goto work just now so will flash my backup later on.

Hopefully you'll get other useful replies later on.
 
Something has just occurred to me on what happened last night which may help. I don't have any debug logs yet as I cannot reproduce it this morning yet.

I was recording a program last night before going to bed and using my harmony to switch everything off. My box is set to deep standby on pressing the power button but as it was recording it comes up with the message on the vfd that a recording is in progress and do you want to shutdown yes or no. I usually hit no but didn't last night, just left it. When I got up this morning on the vfd it said 2 jobs running do you want to shutdown so hit yes and went into deep standby. Then turned everything on again and the problem was there. I also have a power timer setup to wake up for 10 minutes at 1.36am then go into deep standby so my bouquets are updated at 1.38am along with crossepg.

I will try and reproduce it with debug log but does this ring a bell with anyone having the issue?

As a side note a recording was taking place when my bouquets were being updated.
 
Last edited:
Hi,
I have just sent Debug log ref 1387811201.38 for my solo2 with the N/A issue. Will do fresh install to fix but though I'd send the log in the hope it will save others the trouble. Hope I've done it right as never used before.
Regards, Stales
 
Hi,
I have just sent Debug log ref 1387811201.38 for my solo2 with the N/A issue. Will do fresh install to fix but though I'd send the log in the hope it will save others the trouble. Hope I've done it right as never used before.
Regards, Stales

How did you reproduce this?

Tried to reproduce it by starting a recording the running auto bouquets and rebooted box but bouquets were fine.?
 
How did you reproduce this?

Tried to reproduce it by starting a recording the running auto bouquets and rebooted box but bouquets were fine.?
Hi,
My issue has nothing to do with recordings. Basically any restart, full or E2, would lose the majority of channel names. Even running ABM again would not populate, would still show as N/A. The only temporary fix for me was to run a manual or auto channel scan and all channel names come back. If it crashed or had to restart it would lose them again and so on. So, I enabled debug log, restarted box and sent debug file (hope it is useful, I have no idea). Have now reflashed and set all setting manually and although painful, mine is fixed.
Regards, Stales
 
Any updates on the issue. Did you manage to replicate the problem?

PS. having the same n/a channels issue.
 
Not been able to reproduce on mine again. Debug logs are turned on I case it happens again.
 
I still have the problem Every morning same issue but only a number of channels.

Once click on n/a channel it puts in channel name, and stays there till next day.

Going back to level 793 fixed issue
View attachment 31360
 
Hi Gary, yes, I was having exactly the same problems so I followed your advice and went back to 793 and all is well again!, thanks
 
I hope the team can fix this issue.... Not worth updating till fix found
 
I hope the team can fix this issue.... Not worth updating till fix found

No one forces you to update, nor can every one replicate your issue, although it is being looked into.
 
Crash logs are generated when a crash occurs. Debug logs record everything that is going on. A reboot is required for debug logs to kick in.
 
I have this same problem, every reboot, all channels are N/A until I either watch them or run an automatic scan of the satellite.

Running latest vix..was working fine as this is the first vix I've installed, but happened randomly after an overnight ABM update.

Any fix yet?
 
No one forces you to update, nor can every one replicate your issue, although it is being looked into.

ive replicated this error on solo , duo and solo2 so not isolated to box but to image build
earlier builds cure issue for all boxes
 

OpenViX Feeds Status

Back
Top