Hi Steve, That's strange - I've just tried this on my deployment and I didn't see this.
One thing - we don't recommend using 'monit restart'. It causes various problems (e.g. https://github.com/Metaswitch/homestead/issues/149, https://github.com/Metaswitch/sprout/issues/956, https://github.com/Metaswitch/sprout/issues/960). We're looking at fixing up our monit scripts (and the documentation), but for now we recommend using 'sudo service <process> stop', and allowing monit to restart the process. Can you try doing this and seeing if the user_settings change gets picked up? Thanks, Ellie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Steve Yeoman Sent: 04 March 2015 18:35 To: [email protected] Subject: [Clearwater] change to user settings not recognised after restart Hi, I'm using Yoshi. If I change some of my user settings in /etc/clearwater/user_settings (e.g. hss_reregistration_time) and then restart with "sudo service clearwater-infrastructure restart" and "sudo monit restart all" then the change is not invoked. I have to reboot the ec2 instance in order to invoke the new settings. This looks like a regression. I used to be able to invoke changes with the restart commands above. cheers Steve Yeoman, Opencloud _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
