omcproxy icon indicating copy to clipboard operation
omcproxy copied to clipboard

omcproxy / LEDE Reboot (17.01.0, r3205-59508e3): does not start on boot

Open tvogel opened this issue 8 years ago • 13 comments

I have set up omcproxy to run on a DHCP interface named "entertain" for Telekom EntertainTV (VLAN 8). I can start omcproxy manually and it works fine. However, after reboot, the process is not running and I don't find any hints in the logs, even after enabling OPTIONS="-v".

Could it be, the procd triggers don't work?

tvogel avatar Oct 15 '17 00:10 tvogel

My workaround:

root@gw:~# cat /etc/hotplug.d/iface/99-omcproxy 
#!/bin/sh
case "$ACTION" in
ifup|ifdown)
/etc/init.d/omcproxy restart
;;
esac

tvogel avatar Oct 15 '17 00:10 tvogel

I have checked the triggers and they are ok. The problem is because the script it self checks it's own variable $PROXIES is empty and then exits 0. one simple solution is to comment out line number 117 " [ -n "$PROXIES" ] || return 0" I think that there are no adverse effects by doing it because the triggers makes it start when it should.

howl avatar Nov 26 '18 15:11 howl

This issue is solved with https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=df8f8bad082ea5280c19c9091c099b28b7e2fc67 and https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=d405edb481bb08ee5db482142c65064902899bd3

howl avatar Jan 06 '19 22:01 howl

I have checked the triggers and they are ok. The problem is because the script it self checks it's own variable $PROXIES is empty and then exits 0. one simple solution is to comment out line number 117 " [ -n "$PROXIES" ] || return 0" I think that there are no adverse effects by doing it because the triggers makes it start when it should.

Yeah that worked for me, Is that ever going to get fixed in Openwrt?

tiagogaspar8 avatar Jan 19 '19 16:01 tiagogaspar8

In the previous message you have the git commit that contains the proper fix.

howl avatar Jan 19 '19 22:01 howl

It still doesn't work for me if I don't comment out that line, what can be wrong?

tiagogaspar8 avatar Jan 19 '19 22:01 tiagogaspar8

The commit is in the development tree.

howl avatar Jan 20 '19 22:01 howl

Let me see if I got this straight, if I build a image from the latest trunk it works? 😅😅😅

tiagogaspar8 avatar Jan 20 '19 22:01 tiagogaspar8

You can simply copy over your installation the omcproxy.init file in /etc/init.d/omcproxy

howl avatar Jan 20 '19 23:01 howl

Yes, but isn't it supposed to work by default? That's why I'm telling you this ahahah

tiagogaspar8 avatar Feb 13 '19 00:02 tiagogaspar8

@tiagogaspar8, yes it works by default in snapshot and the next stable release, backport it if you want in the actual stable. Or simply copy the init file as stated before.

howl avatar Feb 13 '19 09:02 howl

You were right, sorry for the confusion, as this is solved can't this issue be closed? 😄

tiagogaspar8 avatar Feb 13 '19 23:02 tiagogaspar8

Sure, but that can only be done by the maintainer.

howl avatar Feb 14 '19 10:02 howl