Bug #6476

Symbiosis should deleted configurations it creates

Added by Paul Rose over 5 years ago. Updated over 4 years ago.

Status:ResolvedStart date:2014-06-18
Priority:NormalDue date:
Assignee:-% Done:


Target version:jessie


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?)



#1 Updated by Patrick Cherry about 5 years ago

  • Target version set to wheezy

#2 Updated by Patrick Cherry about 5 years ago

Also I guess if a new SSL site is created on a previously-used IP, then any existing config in sites-enabled will cause a clash. Maybe.

#3 Updated by James Carter about 5 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.

#4 Updated by Patrick Cherry over 4 years ago

  • Status changed from New to Resolved

This is fixed now for symbiosis=httpd-configure.

Also available in: Atom PDF