Pierre-Nicolas Posted October 17, 2022 Share Posted October 17, 2022 We have identified an issue happening for setups with multiple boosters ; this issue is linked to NATs, the internal notification system, and how it is configured on boosters. Boosters are currently incorrectly configured to have the same server_name while NATs expects each booster to have a unique server_name. FileWave 14.9.0 fixes the configuration, but in the meantime you can fix it by changing the following booster setting: In /usr/local/etc/filewave/nats or C:\ProgramData\FileWave\FWBooster\nats remove in booster.conf files any line with server_name: "FileWave NATS Booster" and restart boosters. Sorry for the inconvenience. Link to comment Share on other sites More sharing options...
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now