Question & Answer
Question
How do you test nzinit for resolv.conf issues with DNS on IBM Netezza 1000 systems?
Answer
If there are configuration issues during a heartbeat start, they are often caused by /etc/resolv.conf errors conflicting with DNS. The nzinit service owns both DNS and resolv.conf during a heartbeat start.
To troubleshoot resolv.conf configuration issues, you can bring the nzinit service online without the cluster. Doing so allows you to see the stdout error messages related to the nzinit service without looking through /var/log/messages. The procedure below sets up a test environment for troubleshooting.
1. Shutdown the cluster on both hosts:
- # service heartbeat stop ;ssh ha2 -n "service heartbeat stop"
2. Enable maintenance mode on HA1:
- # /nzlocal/scripts/nz.non-heartbeat.sh
3. As root, run the nzinit service:
- # /etc/init.d/nzinit start
This command will display any errors to stdout.
[{"Product":{"code":"SSULQD","label":"IBM PureData System"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":null,"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Historical Number
NZ651519
Was this topic helpful?
Document Information
Modified date:
17 October 2019
UID
swg21577505