python SoftcamCheck error pops up every 5 minutes on the screen :-(

[pooface]

How can I temporarily disable this softcam check ? I only use oscam

As stated previously

you can turn off the softcam check all together but if the cam freezes for any reason the softcam manager will no be able to detect it and therefore will not be able to restart it.

to turn off the softcam check press menu while in the softcam manager and you should see a option in there.

Something changed recently as it looks like I am not the only one with this issue. Saddly I can't find any "log" therefore I can't find where is this time frequence setup etc...

Please enable debug logs... This will help us to track...

It's under settings -> log manager iirc...


Sent from my HTC Sensation using Tapatalk 2

[XabiX]

I had enable debug logs on.
I did disable it and now it works !!!!

cool

[XabiX]

false alarm, it's still appearing.

Anyway with or without enable debug logs I don't see any difference.
Where should those logs be written?

[2stein]

false alarm, it's still appearing.

Anyway with or without enable debug logs I don't see any difference.
Where should those logs be written?

/home/root/logs

[XabiX]

/home/root/logs

Where are those logs? I don't see anything in /var/log ; /home/root/logs and /media/usb/logs. Normally when they are crashes there is a file but with this pop up nothing.

As I said nothing is being writtten there. ( and I checked that the path setup in the log manager was on of these)

[2stein]

As I said nothing is being writtten there. ( and I checked that the path setup in the log manager was on of these)

i think you have to restart enigma2 to start logging.

[Larry-G]

i think you have to restart enigma2 to start logging.

yes you need to start enigma for a log to be written.

[XabiX]

yes you need to start enigma for a log to be written.

I did try that (as it was activated since my initial setup and other crashes did generate the right files like this thread that I opened with the lgos: http://www.world-of-satellite.com/sh...g-all-the-time).

This error msg doesn't generate any log in my case. Hopefully we get the new 3.x image so I can re install

[Larry-G]

I did try that (as it was activated since my initial setup and other crashes did generate the right files like this thread that I opened with the lgos: http://www.world-of-satellite.com/sh...g-all-the-time).

This error msg doesn't generate any log in my case. Hopefully we get the new 3.x image so I can re install

To be honest I'm still not sure what's going on here for you as I am unable to replicate this over any of my 6 receivers.

Sent from my GT-I9300 using Tapatalk 2

[2stein]

I did try that (as it was activated since my initial setup and other crashes did generate the right files like this thread that I opened with the lgos: http://www.world-of-satellite.com/sh...g-all-the-time).

This error msg doesn't generate any log in my case. Hopefully we get the new 3.x image so I can re install

when you turn on debug logs you get a log when starting enigma2... even without error. there is no specific log for the error. the information is contained in the regular log.

[XabiX]

Could someone say clearly which log name and path should I check?

the /var/log/messages doesn't get filled up after the boot so not sure which log you refer to

mine stops with:
Jan 9 20:58:08 gbquad user.warn kernel: WARNING: at lib/vsprintf.c:1293 vsnprintf+0x494/0x4a4()
Jan 9 20:58:08 gbquad user.warn kernel: Modules linked in: ftdi_sio usbserial ext4 jbd2 ext3 jbd ext2 dvb 8712u rt73 rt5370sta
Jan 9 20:58:08 gbquad user.warn kernel: Call Trace:
Jan 9 20:58:08 gbquad user.warn kernel: [<804a9ddc>] dump_stack+0x8/0x34
Jan 9 20:58:08 gbquad user.warn kernel: [<80038b30>] warn_slowpath_common+0x78/0xa4
Jan 9 20:58:08 gbquad user.warn kernel: [<80038b74>] warn_slowpath_null+0x18/0x24
Jan 9 20:58:08 gbquad user.warn kernel: [<8024faa8>] vsnprintf+0x494/0x4a4
Jan 9 20:58:08 gbquad user.warn kernel: [<e136e740>] BKNI_Snprintf+0x28/0x34 [dvb]
Jan 9 20:58:08 gbquad user.warn kernel: [<e12cc0d0>] msgReceived_callback+0xb4/0x240 [dvb]
Jan 9 20:58:08 gbquad user.warn kernel: [<e1347c50>] NEXUS_P_Scheduler_Step+0x30c/0x95c [dvb]
Jan 9 20:58:08 gbquad user.warn kernel: [<e13482dc>] NEXUS_P_Scheduler_Thread+0x3c/0x60 [dvb]
Jan 9 20:58:08 gbquad user.warn kernel: [<e1348bf4>] NEXUS_P_ThreadStart+0x24/0x74 [dvb]
Jan 9 20:58:08 gbquad user.warn kernel: [<8005ada8>] kthread+0x88/0x90
Jan 9 20:58:08 gbquad user.warn kernel: [<8000a14c>] kernel_thread_helper+0x10/0x18
Jan 9 20:58:08 gbquad user.warn kernel: ---[ end trace 732c900a4f63d913 ]---
Jan 9 23:24:00 gbquad authpriv.info dropbear[26902]: Child connection from 192.168.0.254:60996
Jan 9 23:24:01 gbquad authpriv.notice dropbear[26902]: Password auth succeeded for 'root' from 192.168.0.254:60996
Jan 9 23:24:01 gbquad authpriv.warn dropbear[26908]: lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or direct
ory
Jan 9 23:24:01 gbquad authpriv.warn dropbear[26908]: lastlog_openseek: /var/log/lastlog is not a file or directory!

[XabiX]

20130109_232732.jpg
reboot
wait for the pop up and then check:

root@gbquad:~# ls -lr *
-rw-r--r-- 1 root root 7942 Jan 6 19:33 ipkgupgrade.log

logs:
root@gbquad:~#

nothing

[Larry-G]

20130109_232732.jpg
reboot
wait for the pop up and then check:

root@gbquad:~# ls -lr *
-rw-r--r-- 1 root root 7942 Jan 6 19:33 ipkgupgrade.log

logs:
root@gbquad:~#

nothing

your still not doing it correctly.

activate debug logs.
wait for the error message to popup THEN restart E2 and check the Debuglog that corresponds to the reboot time.

as for logs they should be in home/root/logs by default unless you changed the path your self.

also please in future try to create a screen shot rather than a photo of the screen as frankly it's a pain trying to read the info from a photo.

to create a screenshot look here.

How to Take a screenshot from your satellite receiver
Click Here

[Rob van der Does]

your still not doing it correctly.

activate debug logs.
wait for the error message to popup THEN restart E2 and check the Debuglog that corresponds to the reboot time.

Sorry, that's the wrong sequence:
1- Activate debuglogs;
2- Restart Enigma to get the debuglogs actually started;
3- Wait for the problem to occur: then read the last lines in the latest debug log (to be found at home/root/logs or elsewhere if you set that).

No need for any other e2 restart then the first one to activate the logs.

[XabiX]

Sorry, that's the wrong sequence:
1- Activate debuglogs;
2- Restart Enigma to get the debuglogs actually started;
3- Wait for the problem to occur: then read the last lines in the latest debug log (to be found at home/root/logs or elsewhere if you set that).

No need for any other e2 restart then the first one to activate the logs.

I feel crazy Since the update to 555, I don't see the issue.
Your recommendations work and yes I do see the logs now in the initial file. I was waiting for a new one to be created.

now with 555 I see:
job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None

If someone had the issue also, could it try to upgrade to 555 to see if this solved the issue?