Job execution blocked by deleted dns zone

Discussion in 'Installation/Configuration' started by Sheridan, Jun 17, 2010.

  1. Sheridan

    Sheridan New Member

    Hi to everybody.

    I need some help with what seems to be a bug in ispconfig 3.0.2.1.

    First i created a DNS-Zone without using the wizard and adding any record. That happened by accident, so i told ispconfig to delete that zone so that i can recreate it by using the wizard and my template.

    However, that delete job show's up in the jobqueue but nothing happens. It looks like the cronjob can't remove the zone that doesn't have any records assigned.

    I'm using bind as DNS-Server.

    The system log shows the following lines after removing the lock file:

    System Log:
    Code:
    .....
    2010-06-17 22:19  	<hostname>  	Debug  	There is already a lockfile set. Waiting another 10 seconds...  	
    2010-06-17 22:19 	<hostname> 	Debug 	There is already a lockfile set. Waiting another 10 seconds... 	
    2010-06-17 22:19 	<hostname> 	Debug 	There is already a lockfile set. Waiting another 10 seconds... 	
    2010-06-17 22:19 	<hostname> 	Debug 	There is already a lockfile set. Waiting another 10 seconds...
    2010-06-17 22:18  	<hostname>  	Debug  	Call function 'soa_delete' in plugin 'bind_plugin' raised by event 'dns_soa_delete'.  	
    2010-06-17 22:18 	<hostname> 	Debug 	Found 14 changes, starting update process.
    
    The 14 changes are because i've done some other changes after that delete job before i checked the queue.

    The job queue looks like this at the moment:

    Code:
    ....
    2010-06-17 22:00  	<hostname>  	Insert  	dns_rr  	
    2010-06-17 22:00 	<hostname>	Insert 	dns_rr 	
    2010-06-17 22:00 	<hostname>	Insert 	dns_soa 	
    2010-06-17 21:51 	<hostname>	Delete 	dns_soa
    
    Hopefully theres a way to get that blocking delete executed or removed. :(

    kind regards
     
  2. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

  3. Sheridan

    Sheridan New Member

    Thanks Till.
    The update fixed that issue.
     

Share This Page