Remove duty to RESTART FirstSpirit SLAVE server when FirstSpirit MASTER server has been restarted

FirstSpirit allows setting up a:

  • 1 x FirstSpirit Master server (providing the FirstSpirit core including the embedded BerkeleyDB with its FirstSpirit projects)
  • n x FirstSpirit Slave servers (just for generation purposes)

Current situation:

  • a restart of the FirstSpirit master server need restarts of all available FirstSpirit slave servers
  • an individual handling is not possible up to now
  • this behavior leeds to out of sync scenarios (generation aborts in consequence) when having forgotten the slave FirstSpirit server in the manual restart process


  • automatic syncing between master/slave servers
Tags (2)
1 Comment
Community Manager
Community Manager

Hello Holger

thank you for your idea to improve FirstSpirit. It is important for us to learn from the experiences of our customers and partners. For this reason we appreciate feedback and any suggestion.

We have evaluated the issue once again, but have no plans for a realisation in the near future. Therefore, we cannot consider your feature request at this time.

Best regards