Article ID: 121824, created on May 30, 2014, last review on May 27, 2016

  • Applies to:
  • Operations Automation

Symptoms

Tasks to update named fail:

Task name        Update named ns1.pa.domain.tld(1)
Last execution output   
Multiple errors during NS update: domain.name.(6941): Destination host 'ns1.pa.domain.tld' (#7), IP '<NS_SERVER_IP>' : lstat /var/named/run-root/var/domain.name.: No such file or directory (errno 2).

Cause

The mentioned file, /var/named/run-root/var/domain.name, is absent on the NS server. The issue is likely to occur when 2 DNS record add/remove operations for the same domain are running simultaneously.

Resolution

Install OA 6.0.6 with all hotfixes or 6.0.7 to minimize the frequency of the issue occurrence.

To resolve the task failure, check which DNS records are present in the domain's zone under Services > Domains > domain.name > DNS > DNS Records.

Manually create the zone file mentioned in the error and fill it with necessary content. The syntax can be checked in the nearby configuration files (in /var/named/run-root/var/ folder).

This should resolve the issue and the tasks can be rerun.

Search Words

Task ID 21017080

Multiple errors during NS update:

-

failed task

Update named ns2.crystone.net(3)

Multiple errors during NS update: No such file or directory

recursion requested but not available

Task 'Update named .... No such file or directory (errno 2).

subscription not creted in PPA, but showing active in OBAS

Service Creation Failed: Parallels Operation Automation service was not created

No such file or directory (errno 2)

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF