Symbiosis should deleted configurations it creates
Symbiosis currently doesn't delete any configuration files it creates (namely Apache2 and DNS configurations) which can cause issue when removing domains from the system.
An example can be found in two customer issues:
A domain that has a separate IP address set up, creates it's own configuration in '/etc/apache2/sites-available/'. Customer removed the domain over FTP but did not remove the apache2 configuration (They were using FTP so it can be argued they shouldn't have known to). This means that apache2 would still accept requests for the deleted domain and spawn a 'symbiosis-apache-logger' process. The process would then recreated the deleted domain in order to write to a log file. This is done so that the logger doesn't kill apache2 when it fails.
The solution was to removed the domains from /srv/ and deleted the apache2 configurations however. Symbiosis should be do this however when a domain has been deleted ( incron job?)
#3 Updated by James Carter over 4 years ago
- Target version changed from wheezy to jessie
The specific issue of domains being automatically created by apache_logger after previously being removed has been fixed. The more general issue of configuration snippets outliving their domain is to be punted to jessie.