Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
tvogel opened this issue Oct 15, 2017 · 13 comments
Open

Comments

@tvogel
Copy link

tvogel commented Oct 15, 2017

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
Copy link
Author

tvogel commented Oct 15, 2017

My workaround:

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

@howl
Copy link

howl commented Nov 26, 2018

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.

@tiagogaspar8
Copy link

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?

@howl
Copy link

howl commented Jan 19, 2019

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

@tiagogaspar8
Copy link

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

@howl
Copy link

howl commented Jan 20, 2019

The commit is in the development tree.

@tiagogaspar8
Copy link

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

@howl
Copy link

howl commented Jan 20, 2019

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

@tiagogaspar8
Copy link

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

@howl
Copy link

howl commented Feb 13, 2019

@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.

@tiagogaspar8
Copy link

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

@howl
Copy link

howl commented Feb 14, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants