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

FS#1554 - procd/netifd: on shutdown direct start stopping netifd leaving open connections on connected clients #6510

Open
openwrt-bot opened this issue May 20, 2018 · 0 comments
Labels

Comments

@openwrt-bot
Copy link

chris5560:

procd does not stop services managed by procd or not on shutdown before start stopping netifd
If there is no tun-ovpn and br-guest then br-lan is the first network that is stopped.
Consequence: ie radicale (not managed by procd) and dropbear (managed by procd) get no chance to correctly close their client connections.
So client-site running into timeout with possibly incomplete data transfer.

Log:

....
12:00:51 daemon.info procd: - shutdown -
12:00:53 daemon.notice netifd: Network device 'tun-ovpn' link is down
12:00:53 daemon.notice netifd: Interface 'ovpn' has link connectivity loss
12:00:53 daemon.notice netifd: Interface 'ovpn' is now down
12:00:53 daemon.notice netifd: Interface 'ovpn' is disabled
12:00:56 user.warn radicale[----]: Service shutdown FORCED
12:00:56 user.notice radicale[6141]: Service stoped successfully
12:00:56 authpriv.info dropbear[5674]: Early exit: Terminated by signal
12:00:56 authpriv.info dropbear[5675]: Early exit: Terminated by signal
12:00:56 daemon.notice netifd: Interface 'guest' is now down
12:00:56 kern.info kernel: [ 245.292858] br-guest: port 2(wlanif5g) entered disabled state
12:00:56 kern.info kernel: [ 245.298826] br-guest: port 1(wlanif2g) entered disabled state
....

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

No branches or pull requests

1 participant