OpenBh 5.5.1 Now Available

Trying again!:)
@Ev0
Is there anyone else who can fix this cron problem?
Have tested both standard installation and multiboot but does not work in 5.5.1.
No changes have been made. only transferred channel list and uses Oscam
On Vu+Zero4K you have to go back to 5.2 before cron works.
A good way to check if cron works is to set the time to update
with NTP instead of transponder time.
Then a root file will automatically appear in /etc/cron/crontab/root
with this cron, if it appears then it works.
If it does not appear then cron does not work.
 
The image was switched to use NTP time by default in 5.4 so there is no need for any cron timer to be set for this.
 
Ev0 said:
The image was switched to use NTP time by default in 5.4 so there is no need for any cron timer to be set for this.
Click to expand...
Ok, that's fine but just used NTP time as an example.
Don't use this myself, stick to transponder time.
But setting a cron still doesn't work.
As I said it works in 5.2 but not after this.
 
Hacked said:
Ok, that's fine but just used NTP time as an example.
Don't use this myself, stick to transponder time.
But setting a cron still doesn't work.
As I said it works in 5.2 but not after this.
Click to expand...
Worked for me when I tested it this afternoon.
 
Ev0 said:
Worked for me when I tested it this afternoon.
Click to expand...
It's strange that my cron doesn't work in anything other than 5.2. using VU+Zero4K.
I only create the root file and put it in the folder /etc/cron/crontab/
Cron looks something like this:
30 6 * * * /usr/bin/IPTV.sh user passw >> /tmp/cron.log 2>&1
Click to expand...

Also have a Pulse4kmini, will test 5.5.1 on it.
Have been on vu+ for many years and this should be plug and play,
it shouldn't be necessary to activate anything.
 
Works fine with Pulse4kmini.
Found an error in the Vu+Zero4k log like this:
Feb 15 07:08:00 vuzero4k cron.info crond[1454]: (root) RELOAD (/var/spool/cron/crontabs/root)
Feb 15 07:08:00 vuzero4k cron.info crond[1454]: (CRON) missing newline before EOF
Click to expand...
Created a new cron in notepad++ and the problem was solved.
And works just fine on Vu+Zero4k too.
We learn as long as we live, it's important to use the right editor:cool:
 
The logs would point to a plugin or skin issue.
If no one else has suggestions, access the receiver files and delete the enigma2 folder in /etc. This can be done using terminal or putty. Then reboot the box. Do a Fresh install and do not restore anything.
 
I have tried the proposed solution but it still does not start Boot to Recovery image - slot0

Slot1 and the others are working well.
 
Remove the usb stick from the box, and it should boot slot 0.

Failing that, put an empty file named "STARTUP_RECOVERY" onto the root of the usb, just remember to remove it after you have booted slot0 otherwise you will only boot slot 0.
 
I will do a clean installation, everything from the beginning,
only slot1 installed openBH 5.5.1,
USB stick removed after installation, second one not inserted
going to boot slot0,
the system does not start.
 
The system Does Not Start???
Try creating enigma debug log. In telnet or terminal, login to the receiver and type init 4 then enigma2
init 4 followed by enigma2 will generate a log. Copy the log information from the terminal screen and post it. Maybe doing this will show exactly why the receiver stops.
 
I did

And then I copied the files libcurl.so.4 and libcurl.so.4.8.0 from /boot/linuxrootfs1/usr/lib

to usr/lib

and everything worked

Using username "root".
root@vuzero4k:~# init 4
root@vuzero4k:~# enigma2
enigma2: error while loading shared libraries: libcurl.so.4: cannot open shared object file: No such file or directory
root@vuzero4k:~#
Click to expand...
 
You must log in or register to reply here.
Back
Top