nv-l
[Top] [All Lists]

RE: [nv-l] Warning of a gotcha on the upgrade to 7.1.4, for the record

To: <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] Warning of a gotcha on the upgrade to 7.1.4, for the record
From: "Ray Westphal" <westphal2002@charter.net>
Date: Mon, 5 Apr 2004 19:45:28 -0500
Delivery-date: Tue, 06 Apr 2004 01:51:11 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Importance: Normal
In-reply-to: <OF9FE2C030.B6CAEE4F-ON85256E6B.006F812D-85256E6B.00713C06@us.ibm.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Thanks Leslie.
 
Ray Westphal
Enterprise Rent-A-Car
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Leslie Clark
Sent: Saturday, April 03, 2004 2:40 PM
To: nv-l@lists.us.ibm.com
Subject: [nv-l] Warning of a gotcha on the upgrade to 7.1.4, for the record


It must be that all of you did this right the first time, since I saw no mention of it in the archives (well, Ray W. may have hit it :), but for the record:

We used to have to worry about the ulimit settings in /etc/security/limits, but since /etc/netnmrc checks and sets them for us, I have not been worrying about them lately. In fact, at my current customer I don't even have read access to that file.  However, there is a common mistake in /etc/security/limits that will cause the upgrade to fail. If you have a setting in there that sets 'nofiles' to '-1' for root, it should be changed to something less than or equal to 32767. The '-1' does not actually mean 'unlimited', it means 65535 on a 32-bit system, much larger than the system limit for file descriptors, which apparently is 32767. In AIX V4 that number was 2000.

The symptom of the failure is that all of the old Netview entries in /etc/services are deleted during the upgrade but not replaced. So no daemons will start, beginning with nvlockd. The failure message in /tmp/NVS_714_NVCONF_after.error says:
 Running customize script for fileset OVMIN.
    Making links....
  Running customize script for fileset OVWIN.
ERROR:     Customize script for fileset OVWIN exited with code 2.
ERR_cfgbf_001

There is an item about this in the Knowledge Base, but you won't find it by searching on the symptoms. You have to know the cause. Go figure. We've suggested additional search words on that feedback screen they give you in the Knowledge Base. We'll see if it works. And now this will be in the listserver archives as well.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web