Path: utzoo!attcan!uunet!decwrl!ucbvax!tron.bwi.WEC.COM!kerr
From: kerr@tron.bwi.WEC.COM
Newsgroups: comp.sys.apollo
Subject: Re: problems with apollo's running mentor software
Message-ID: <9010101611.AA03918@uunet.uu.net>
Date: 10 Oct 90 15:50:16 GMT
References: <9010091412.AA21592@richter.mit.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 52

> Not being a Mentor user, I am simply speculating about the cause of
> your problem ...

> It occurs to me that if the time/date of the workstations running copies
> of /etc/ncs/glbd (the NCS Global Location Broker Daemon) differ by more
> than 5 minutes, the various copies of glbd will not update each other
> correctly. When this happens, the nodes which use one of the copies which
> have not been updated may be unable to see the network registry daemons.

This was the problem I was trying to correct. I ran
drm_admin and saw that our clocks were skewed. Rather than
shutting the nodes down to run ex calendar, I tried the
date. Well, the clocks were no longer skewed, but Mentor
wouldn't work :-(. Rebooting (and maybe an ex calendar)
fixed the problem.

> This will result in things like /etc/passwd being unreadable, being unable
> to change your password, being unable to login to another account, etc.
> If Mentor is trying to read /etc/passwd to get a user ID, this would explain
> the failure. If Mentor is using some NCS-based floating license server, the
> failure of the multiple copies of glbd could also result in a Mentor client
> workstation being unable to find the license server.

AT this release (7.1) Mentor doesn't use a floating license
server. It uses a static authorization file. The file
contains authorization codes that are a function of the
nodeid, the date of the software expiration, and the application
that you're authorized to run.


Thanks for the info,
Dave
--
Dave Kerr (301) 765-4453 (WIN)765-4453
tron::kerr                 Internal WEC vax mail
kerr@tron.bwi.wec.com      from an Internet site
kerr@tron.UUCP             from a smart uucp mailer

> Try using /etc/ncs/drm_admin to check how many copies of /etc/ncs/glbd
> each workstation thinks there are on the network and whether or not
> the wo> rkstations' clocks are in sync. Fire up a copy of drm_admin and
> give the command "set -o glb -h //some_node_with_glbd_running" to see
> how many copies of glbd the workstation thinks should be running and
> their respective time/date.


>  -- David Krowitz

> krowitz@richter.mit.edu   (18.83.0.109)
> krowitz%richter.mit.edu@eddie.mit.edu
> krowitz%richter.mit.edu@mitvma.bitnet
> (in order of decreasing preference)