hi, i created an image of openwrt master but it does not start luci/uhttpd.
i checked dmesg and logread, no error/warning.
i always have to ssh into the device, then service uhttpd restart and it works.
anyone an idea how i can figure out whats wrong/going on?
doesn't start when ?
when i reboot the router
there's a difference between not started, and started but not bound to all the available interfaces, which one would it be ?
when i do a "service uhttpd restart" and that works, i would chose it is not started but bound, but i am not sure.
i did not change any of the init scripts.
that solution would work for both scenarios, so it doesn't answer the question.
you need to look for the process on OS level.
or do a /etc/init.d/uhttpd status
if it is bound to any interface, i would expect that service to be started.
i will reboot the device, do an uhttpd status and paste the output here
it could be started even if it weren't, hence the question.
indeed, it is running
root@OpenWrt:~# /etc/init.d/uhttpd status
running
but somehow not serving,
root@OpenWrt:~# netstat -alpn | grep 443
tcp 0 0 :::443 :::* LISTEN 1914/uhttpd
but no web ui available when i go to https://192.168.1.1, until i do a service uhttpd restart
so it's a race condition, the uhttpd starts too early in the boot process.
you have two options.
add /etc/init.d/uhttpd restart
to /etc/rc.d/rc.local
or
in /etc/init.d
mv S50uhttpd to S99uhttpd
the 2nd option might not be enough though, and it'll be lost between upgrades.
that might be a workaround but it feels so wrong
any way to figure out what race condition this is or what its causing, so the root cause can be fixed?
since it'd not binding to all interfaces, it's the network who takes too long to come up.
why it takes time, who knows, might be hw related, or because of your config.
moving it to S99 works, but would really love to know why it fails with S50. If anyone has an idea how to debug the start/init-behaviour, please let me know
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.