Networker

Re: [Networker] problems with 7.1.1 to 7.1.3 upgrade

2005-04-18 13:47:15
Subject: Re: [Networker] problems with 7.1.1 to 7.1.3 upgrade
From: Roberta Butcher Gold <gold11 AT LLNL DOT GOV>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 18 Apr 2005 10:28:28 -0700
Funny, I just ran into the same problem upgrading one of my Solaris servers. The two I did last week did not get that error. I found this in the Legato Knowlegebase. I tried the workaround and it worked.

===========================================================
Upgrading NetWorker on Solaris
===========================================================

Upgrading NetWorker on Solaris 8
After installing Sun patch 110934-2X you may receive the following error from pkgadd:
Error: '(Existing_directory_name) not writeable'

Sun Solaris patch 110934-21 enforces that request script be run a user nobody or install,
this breaks networker request script which assume that it will be run as root.
Request Script Behaviors: The request script cannot modify any files. It only interacts with administrators installing the package and creates a list of environment variable assignments based upon that interaction. To enforce this restriction, the request script is executed as the non-privileged user 'install', if that user exists; otherwise it is executed as the non-privileged
user 'nobody'. The request script does not have superuser authority.
Known issue:    Contact LEGATO Software (EMC Software Group):
work-in-progress
Work around: Set the following environment variable prior to the installation:
# NONABI_SCRIPTS=TRUE
# export NONABI_SCRIPTS
===========================================================



On Mon, Apr 18, 2005 at 11:55:47AM -0400, Teresa Biehler wrote:
 I'm upgrading my NW server from v7.1.1 (on Solaris) to v7.1.3.  Well,
 I've uninstalled without problems, but when I try to install v7.1.3, I
 get the following:

 Directory to use for client, licensing and server information [/nsr]?

 `/nsr' is not writable

 As far as I can see, /nsr is indeed writable by root.  So, I looked at
 the script in the install directory to see what tests were done to
 produce this error.  I found one place within the script that produces
 this error.  When I reproduce that function, loop and test, the results
that I receive is that our /nsr directory is writable. Has anyone seen this? Do you have any ideas?
I have seen this, and the fix in my case was to make the directory group
writable as well.  I know that it shouldn't matter, and I don't know why
it doesn't work, but adding group write permissions let the pkgadd
continue.

Dave

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Roberta Butcher Gold
Lawrence Livermore National Laboratory
ICC/HPSD - Security Technologies Group
gold11 AT llnl DOT gov
(925) 422-0167

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>