A question about setting up an Ignite server

[Yvonne Butler]

I'm trying to setup an Ignite server and have got to the part where I'm creating an ignite config file that represents the contents of the software depots. I've therefore run the following command:

make_config -a both -c /var/opt/ignite/data/Rel_B.11.11/Core_OS.cfg -s /swtmp/Ignite.depot

and have the following output:

NOTE: make_config can sometimes take a long time to complete. Please be
patient!
ERROR: Could not get the ip address for the SD server "uklunx50".

SUMMARY: 0 config files were created correctly.
1 config file could not be created due to errors.

I can't understand why its complaining about the IP address of uklunx50, I've checked the hosts file contains the correct information and that nsswitch.conf is looking at files as well as DNS. Any ideas anyone please?

Thanks and regards

[Steven E. Protter · Accepted solution]

Shalom Yvonne,

Check /etc/hosts networking, /etc/nsswitch.conf and that all servers involved in this Ignite transaction have good network connectivity.

Somewhere, perhaps the DNS database or /etc/hosts there is an inconsistency.

Perhaps fully qualified domain names would help.

What version of Ignite?

SEP

[Pratyush Paul_1]

Hi -

This is due to the dns lookup failure. Please do an nslookup of the hostname and the IP address and see if you are able to get a reply from the dns entry. Check in the following files

/etc/hosts
/etc/resolv.conf
/etc/nsswitch.conf

Please let me know if it helps.

Thanks

Pratyush

[Sivakumar TS]

Hi,

this simply means the server is unable to resolve the IP for "uklunx50" server.

check for the valid entry in /etc/hosts. If you use any DNS thenmake sure that the /etc/resolve.conf has the DNS IP.

you confirm it by,

#nslookup uklunx50

or

#ping uklunx50

If you are able to get the reply then the above process should get succeed.

With Regards,

Siva.

[Yvonne Butler]

Apologies for not getting back to you all earlier...

I believe the problem was the FQDN, it didnt match what was in resolv.conf. Now that I've changed the FQDN within /etc/hosts to match resolv.conf, the command has worked.

Thanks everyone!

[Yvonne Butler]

See last update