28 replies to this topic

[marcus83]

hi guys!

 

why sometimes oscam does not start when starting the decoder? you need to restart softcam

 

and sometimes it stops working…

 

 

Oscam status:

 

Error: [Errno 111] Connection refused

[littlesat]

Did you get your oscam from our feeds?

[s3n0]

Hi.

 

It happens to me too, but I haven't found out why. Sometimes Oscam just stops working after booting. In my case, however, it is Enigma2 distribution OpenATV 7.3 + Formuler F4-Turbo set-top box.

 

In old versions of Enigma2 it was OK.

 

Since I don't often need to reboot the set-top box, it doesn't matter to me. I restart Oscam after booting Enigma2 manually and then Oscam works OK.

 

From my point of view, the problem can be, for example, in the loading of some libraries, drivers or the computer network itself. Apparently, Oscam has some problem with the mentioned system resources until they are fully started / fully implemented - fully available for the Linux system. But that's just my humble guess!

[mimisiku]

Never had a problem with a non-starting OScam… Not with OpenPli, or any other DreamOS based image..

[neo]

Never seen this as well...

[WanWizard]

Box connected using wifi, and Oscam using external CS connections that can't be made until the network is up?

 

Having said that, all my boxes are connected wirelessly too, and I've never experienced this issue.

[mrvica]

8.3 is just loading too fast, before any dvb drivers (firmware), maybe we should put some sleep here

instead of

exec start-stop-daemon -S -x /usr/bin/oscam -b

some sleep

sleep 15 && exec start-stop-daemon -S -x /usr/bin/oscam -b

[WanWizard]

On which box(es) do you experience this? I'd like to see it before adding all sorts of hacks...

[mrvica]

I experienced this on H7 on 8.3 release not on previos develop version, it is booting faster means the script with oscma is booting faster as well, oscam needs some stuff to start which is not loaded yet, jus my opinion

[s3n0]

I experienced this on H7 on 8.3 release not on previos develop version, it is booting faster means the script with oscma is booting faster as well, oscam needs some stuff to start which is not loaded yet, jus my opinion

Yes, but then the question is, what is wrong with Oscam if it starts too early. Oscam is a system process that runs independently of the Enigma2 GUI. Rather, it depends on the DVB drivers in the Linux system. The start delay can be added very easily to the "init.d" or "systemd" script itself.

 

According to me, after the first start, Oscam does not find the DVB hardware (decoding card) and does not try to search for it again the second time. As long as the connection to the external proxy works OK.

 

Thus, a delayed start of the Oscam process would help if it is an Enigma2 boot. I solved how to detect the Enigma2 boot state in my shell scripts, for example by testing OpenWebif with the help of the WGET command. If OpenWebif is still not started, it means that Enigma2 is still not booted either. So it is enough to add the OpenWebif test to the startup algorithm in the shell-script for Oscam, and in case of an error, you have to start Oscam with a time loop of 15 seconds .

 

There are many ways to delay the start of Oscam, especially when booting Linux. Meanwhile, when calling the softcam script under normal circumstances, i.e. when Linux is running, it will run normally.

[littlesat]

Where did you get the binary from? There are 3rd party binaries that do not cover the clock properly!

[s3n0]

Hi again.

 

I also thought that it would be appropriate to check whether the "init.d" script for starting the softcam has the last priority / order. The symbolic link for starting can be found in run-level-3, so in the directory: /etc/rc3.d/ and the ideal value is 99 for this softcam, so look for a link like: S99softcam . Also check if there are more symbolic links for the same softcam (when installing and uninstalling incorrectly, which also happens a lot). Delete them if so and install your softcam again. As far as I know, some installers specify the order value 50 and that is also not suitable.

 

However, this startup priority only applies to the shell scripts themselves, respectively the "init.d" module itself. This does not apply, for example, to booting Linux drivers itself. So renaming the sym-link to the name "S99.........." may not help.

 

If anyone would like, I made my own shell-script for Softcams:

https://github.com/s... still booting)

...which tests the boot-state with the help of the available OpenWebif. It is only a marginal solution for now. It would be better to test the current run-level with the runlevel command in the startup shell-script. However, in a typical small Linux system, this may not work completely regularly either.

Edited by s3n0, 7 June 2023 - 11:16.

[piplan1966]

Hi
I have a Vu Zero receiver,
Figure 8.3 is
I have checked OSCAM 11718 today, working fine,

[s3n0]

Hi
I have a Vu Zero receiver,
Figure 8.3 is
I have checked OSCAM 11718 today, working fine,

Hi. Yes... but it doesn't happen every time the set-top box is restarted. It happens only occasionally - for example only every 3-10 times when the set-top box is rebooted (or even during normal power-on, i.e. cold start).

[WanWizard]

Still no answer on whether this happens with the oscam we provide, of if this is happening with some custom installed oscam (and oscam scripts).

 

I can only repeat I've never seen it, and I flash / update my boxes virtually daily, including a restart.

[marcus83]

the problem happens with the latest version of oscam 11718...so do you think i should install the version directly from the feed?

[WanWizard]

If you wait until after the build this weekend, then 11719 wil be in the feed.

[marcus83]

If you wait until after the build this weekend, then 11719 wil be in the feed.

yes I know that the latest version of oscam has been released, ok I wait..

 

can you tell me all the commands and paths to remove oscam manually? because I can not find it in the list of installed plugins. thx!

[40H3X]

If you installed it from our feeds, it should be in the installed plugins and if you did not install it from our feeds, it maybe the cause of your problems.

 

To answer you question, if it is not in the installed plugins, than I advise you to install it "from our feeds", with this action (installing) it should overwrite the present oscam file, which should be in

/usr/bin/oscam

If you can work with the CLI you could find were it is located, using

find / -xdev -name oscam

The stop it with

kill oscam

and remove it

rm oscam

and then install it from with the plugins.

 

 

Btw if you want to check if it is installed, use

 opkg list-installed | grep *oscam*

[marcus83]

 

If you installed it from our feeds, it should be in the installed plugins and if you did not install it from our feeds it maybe the cause of our problems.

 

To answer you question if it is not in the installed plugins, than I advise you to install it "from our feeds, this action it should overwrite the present oscam file, which should be in

/usr/bin/oscam

If you can work with the CLI you could find it, using

find / -xdev -name oscam

no I did not install it from your feed because the latest version was not there