fosquitto: raise respawn_timeout
Description
Raise respawn_timeout from 0.2 to 2s in order to not to try respawn
process too fast.
This proposed change helps for Mox AEEE/D with default simple network setup (no VLANs). But it definitely needs testing on different Mox combinations.
Tested variants:
| variant | no VLANs | VLANs |
|---|---|---|
| AC | ||
| AE | ||
| AEC | ? | |
| AEEC | ||
| AGBEEC | ||
| AEED | ||
| AGBEED | ||
| AEEED | ||
| AGBEEED |
How to test
Example VLAN setup
Modify /etc/config/network to use VLANs.
For example on Mox AC:
config interface 'lan'
[...]
option device 'br-lan.1'
config interface 'guest_turris'
[...]
option device 'br-lan.100'
config interface 'IoT_turris'
option enabled '1'
option proto 'static'
option ipaddr '192.168.220.40'
option netmask '255.255.255.0'
option bridge_empty '1'
option device 'br-lan.101'
config device
option name 'br-lan'
option bridge_empty '1'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
option type 'bridge'
option macaddr 'aa:bb:cc:dd:ee:ff'
config bridge-vlan
option device 'br-lan'
option vlan '1'
list ports 'lan1'
config bridge-vlan
option device 'br-lan'
option vlan '100'
list ports 'lan2:t'
list ports 'lan3:t'
config bridge-vlan
option device 'br-lan'
option vlan '101'
list ports 'lan3:t'Adjust port to VLANs based on number of ethernet ports available.
Before fix
On longer Mox variations (8 and more ethernet ports), mosquitto and foris-controller is not running right after boot sequence is complete (aka "Router Turris successfully started.").
Sometimes it works fine on regular (setup from guide) network setup, but breaks on network setup with VLANs.
After fix
mosquitto and foris-controller should be up and running right after boot sequence is complete.
Might help resolve: #832 (closed)