KenthJ Absent Member.
Absent Member.
1186 views

DNS entered failed state

Hi

After an upgrade to OES2018 I started to get problems with the DNS.
Every two weeks DNS enters failed state.


[7915]: rbtdb.c:1032: INSIST(version->references > 0) failed

[7915]: exiting (due to assertion failure)

systemd[1]: novell-named.service: Main process exited, code=killed, status=6/ABRT

stop-novell-named[7137]: novell-named: no process found

systemd[1]: novell-named.service: Unit entered failed state.

systemd[1]: novell-named.service: Failed with result 'signal'.


Any suggestions what to do?

Regards,
Kenth
Labels (1)
0 Likes
10 Replies
AutomaticReply Absent Member.
Absent Member.

Re: DNS entered failed state

KenthJ,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit https://www.microfocus.com/support-and-services and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.microfocus.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.microfocus.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.microfocus.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Micro Focus Forums Team
http://forums.microfocus.com



0 Likes
Knowledge Partner
Knowledge Partner

Re: DNS entered failed state

In article <KenthJ.8o71lz@no-mx.forums.microfocus.com>, KenthJ wrote:
> After an upgrade to OES2018 I started to get problems with the DNS.
> Every two weeks DNS enters failed state.

....
> Systemd[1]: novell-named.service: Failed with result 'signal'.
>
> Any suggestions what to do?


Sorry for the delay, those of us who normally hang out have been busy
with our day jobs (the fall conference season here in Toronto)

the usual places to check for clues
/var/log/messages (possibly other files if you've re-directed them
elsewhere)
/var/opt/novell/log/named

are the failures at the same time of day?
Is the DNS server at all accessible from the outside?

Does restarting just the service keep it going for those two weeks or
is a full server restart needed (or have you even done a full (patch&)
reboot since this started)


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
https://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
KenthJ Absent Member.
Absent Member.

Re: DNS entered failed state

Hi,

Checked the log files.
named.run:

26-Sep-2018 08:33:58.334 general: task: info: creating thread for dynamic reconfiguration.
26-Sep-2018 08:33:58.335 general: dynamicrecon: info: Starting the dynamic reconfiguration
26-Sep-2018 08:33:58.336 general: dynamicrecon: info: Reconfiguring all the zones.
26-Sep-2018 08:33:58.360 general: dns/db: info: Read the configuration for the zone: xxxxxxx_xx.Dns.xxxxxx.xxxxx of type: 1 with return code: 0
26-Sep-2018 08:33:58.370 general: dns/db: info: Read the configuration for the zone: xx_xxx_xx_IN-ADDR_ARPA.Dns.xxxxxx.xxxxx of type: 1 with return code: 0
26-Sep-2018 08:33:58.381 general: dns/db: info: Read the configuration for the zone: RootServerInfo.Dns.xxxxxxx.xxxxx of type: 1 with return code: 0
26-Sep-2018 08:33:58.399 general: dynamicrecon: info: Dynamic reconfiguration completed.
26-Sep-2018 08:33:58.399 general: task: info: dynamic reconfiguration thread exiting gracefully
26-Sep-2018 08:33:58.407 general: dns/zone: error: zone RootServerInfo/IN: has no NS records
26-Sep-2018 08:33:58.407 general: dns/zone: warning: zone RootServerInfo/IN: Failed to Reload the zone
26-Sep-2018 08:35:43.266 update-security: update: error: client xx.xxx.xxx.xxx#64071: update 'xxxxx.xx/IN' denied
26-Sep-2018 08:35:47.124 general: main: critical: rbtdb.c:1032: INSIST(version->references > 0) failed
26-Sep-2018 08:35:47.127 general: main: critical: exiting (due to assertion failure)


The failures comes whenever, no specific time or day.
No access to the DNS from the outside.

Restarting the service keeps it going for a couple of weeks before failure again.
I have patched the server several times and done several of reboots.
0 Likes
Knowledge Partner
Knowledge Partner

Re: DNS entered failed state

Just out of the blue: we had over the years issues with the named daemon on OES11 and OES2015 when multiple cores where involved (which nowadays should be the common offset). So might want to start the daemon manually with the
-n 1
parameter or limit it to CPU0 at runtime with something like
taskset -pc 0 pid-of-named
If it still dies you haven't lost anything, if the behaviour stops we know that an issue has been reintroduced which had been fixed multiple times before.
0 Likes
KenthJ Absent Member.
Absent Member.

Re: DNS entered failed state

Hi

DNS now failed both Friday and Monday.
Started the DNS today with systemctl start novell-named.service -n 1
So lets see how long DNS works this time

Thanks
0 Likes
Knowledge Partner
Knowledge Partner

Re: DNS entered failed state

Did you verify (with taskset) that the daemon is REALLY bound to CPU0?
taskset -p <pid> should return affinity MASK 1
taskset -pc <pid> should return affinity LIST 0
0 Likes
KenthJ Absent Member.
Absent Member.

Re: DNS entered failed state

No it was not really bound to CPU0
Did "taskset -pc 0 pid-of-named" instead, so now it's bound to CPU0

Thanks
0 Likes
Knowledge Partner
Knowledge Partner

Re: DNS entered failed state

Yes, on checking with OES2018 yesterday it seemed that the daemon didn't honor the "n" switch.
0 Likes
KenthJ Absent Member.
Absent Member.

Re: DNS entered failed state

Hi

Today the DNS failed again, so no help with bound to CPU0
0 Likes
Knowledge Partner
Knowledge Partner

Re: DNS entered failed state

Then it's SR time.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.