ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins.Read more for important details.
Absent Member.
Absent Member.
721 views

added a New Server to Tree & Removed old one - Slow Start Up

I added a new server to the Tree & removed the old one (after making this master)

When booting new Server it take a Long time for LDAP server to be ready
and similar for named

ndsrepair seems OK

Have I missed something ?

any pointers greatly appreciated
Labels (2)
0 Likes
4 Replies
Absent Member.
Absent Member.

bhrt60,

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.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://www.novell.com/support and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

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

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

Good luck!

Your Novell Forums Team
http://forums.novell.com


0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

bhrt60;2413733 wrote:
I added a new server to the Tree & removed the old one (after making this master)

When booting new Server it take a Long time for LDAP server to be ready
and similar for named

ndsrepair seems OK

Have I missed something ?

any pointers greatly appreciated


The LUM config is probably still pointing to the ip of the server you removed?

You can quickly check that by looking in /etc/nam.conf.
The better way to fix this (instead of changing the ip in that file and running "namconfig -k") is to start the OES Install & Configure module in YaST, move on to the configure screen and select to reconfigure LDAP and NAM. There you can take out any old references and put back in the new ip where needed.

Applying the changes through YaST (instead of directly in the config file) is that it will save you from "hickups" during an upgrade.

Cheers,
Willem
0 Likes
Absent Member.
Absent Member.

Hi

On a COPY / Mirror I did exactly that and it sorted it...
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

bhrt60;2416032 wrote:
...exactly that...


What exactly (the quick or cleaner way)? 🙂

Good to hear it's sorted.

Cheers,
Willem
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.