Re: upd distribution/install

Gerald Guglielmo (gug@fnal.gov)
Thu, 02 Sep 1999 09:52:43 -0500

Hi,
Marc Mengel was able to help me resolve the problem. I was trying to
install products into a new database which was empty to start with
(seems reasonable for a new database). Anyway the problem surfaced
because the database was empty. It turns out that if the database is
empty, not all of the environment variables UPD needs to install
products properly get defined. At least UPD_USERCODE_DIR does not get
defined, which turns out to be how UPD knows where to look for updusr.pm
and thus the error message. The solution was to create a directory in
the new database so that the database would not be empty. Marc suggested
xxx, I used something a little more descriptive:
cd /usr/global/products/ups_database
mkdir emptyDatabaseBugFix

Once this directory was created, UPD was able to successfully install
products into the database. Now why didn't I think of that?

Gerald Guglielmo wrote:
>
> Hi,
> I cannot get the default Fermi RedHat Linux upd to work. The error I
> am getting is:
> Notice: no updusr.pm module found
> Undefined subroutine &updstb::updusr_get_db called at
> /local/ups/prd/upd/v4_4/src/updstb.pm line 99.
>
> >From the web doc
> http://www.fnal.gov/docs/products/ups/InstallDocs/ups-install.html
>
> 5.Create the files updconfig and updusr.pm in the UPD_USERCODE_DIR.
>
> As a template, you can use the updconfig.template and
> updusr.pm.template files from the ups
> subdirectory of the upd product. You should not need to
> modify the example updusr.pm file for most configurations;you will need
> to edit the updconfig file. The most important keyword is UPS_PROD_DIR,
> which determines the product root naming convention on your system.
>
> $ cp /path-to-upd-v4/ups/updusr.pm.template \
> /path-to-upsdb/.updfiles/updusr.pm
>
> Looking at these two files I see:
>
> droidh}(g023) less /local/ups/prd/upd/v4_4/ups/updusr.pm.template
> require 'default_updusr.pm';
>
> droidh}(g023) diff /local/ups/prd/upd/v4_4/ups/updusr.pm.template
> /local/ups/db/.updfiles/updusr.pm
> droidh}(g023)
>
> So it looks like the bootstrap install is doing the above advice and
> updusr.pm is in the right place and is identical to the template version
> in upd/v4_4/ups area. I'm guessing the problem is with
> default_upduser.pm, which I haven't been able to find. Any ideas on how
> to fix this?
>
> --
> -Jerry->
> gug@fnal.gov
> Pepe's Theory of everything: "Under the right circumstances, things
> happen."

-- 
-Jerry->
gug@fnal.gov
Pepe's Theory of everything: "Under the right circumstances, things
happen."