| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2202.1 | some other informations | CLINTO::DALLAVO | G.Alfredo Dall'Avo NSIS-Milan Italy | Mon Feb 03 1997 11:55 | 24 |
| <<< Note 2202.0 by ZAPATA::DALLAVO "G.Alfredo Dall'Avo NSIS-Milan Italy" >>>
-< Can't connect to server daemons - ERROR >-
Sorry for the mistake,
the version of Digital UNIX installed on the server (AXP 2100) and
on the clients (Alphastation 200 and 255) is the V4.0B.
> The failing test into the "pnv" script is:
>
> /usr/OV/bin/vfy_access ovw_binary
The error that I get after the execution of this command is:
Lost connection to the security server. Retry your function ....
Another strange thing is that a client still running PNV V4.1B can
connect the server without any problem.
Thanks in advance.
Gian Alfredo
|
| 2202.2 | | MOLAR::SIEGEL | MS: ZKO1-3/H18 DTN: 381-0035 | Mon Feb 03 1997 17:16 | 10 |
|
Gian,
Did you look at /pnv.log and see if there were any error messages?
Does the "/usr/OV/bin/pnv_server showclient check" command issued on
the server list your client's hostname?
Joanna
|
| 2202.3 | | CLINTO::DALLAVO | G.Alfredo Dall'Avo NSIS-Milan Italy | Tue Feb 04 1997 09:58 | 27 |
|
> Did you look at /pnv.log and see if there were any error messages?
The pnv.log is 0 byte long.
The /usr/OV/log directory is empty.
> Does the "/usr/OV/bin/pnv_server showclient check" command issued on
> the server list your client's hostname?
It list all the four clients: the three with PNV 4.1C and the
one with PNV 4.1B + ECO 01.
After the reinstallation on the server and on the three clients
I did "pnv_server remclient ..." + "pnv_client remserver ..."
and after "pnv_server addclient ... NFS" + "pnv_client setserver ..."
two or three times ... no changes.
The command "pnv-client checkserver" give no output on all
the four clients.
The command "pnv-client showserver" give the same output on all
the four clients.
Gian Alfredo
|
| 2202.4 | V4.0B or V4.0A? | MOLAR::SIEGEL | MS: ZKO1-3/H18 DTN: 381-0035 | Tue Feb 04 1997 10:04 | 6 |
|
Gian, are you sure you have Digital UNIX V4.0B installed or is it
V4.0A? We have not tested PNV V4.1C on DU V4.0B.
Joanna
|
| 2202.5 | OSF1 V4.0B rev. 564 | CLINTO::DALLAVO | G.Alfredo Dall'Avo NSIS-Milan Italy | Tue Feb 04 1997 10:48 | 29 |
|
> Gian, are you sure you have Digital UNIX V4.0B installed or is it
> V4.0A? We have not tested PNV V4.1C on DU V4.0B.
Absolutely yes.
/> uerf -R -r 300 | more
...
...
Digital UNIX V4.0B (Rev. 564); Sat
_Nov 23 15:18:09 MET 1996
...
...
/> uname -a
OSF1 view04.xxx.yyy.it V4.0 564 alpha
/>
The customer received OSF V4.0B one month and half ago.
The only problem we saw with OSF V4.0B + PNV V4.1B + ECO 01
was the crash of the nv_mib snmp agent extension on the server.
After every boot we did "/sbin/init.d/snmpd stop" and then
"/sbin/init.d/snmpd start"; after that all systems worked fine.
We read that the V4.1C will avoid that problem: so we installed
it.
Gian Alfredo
|
| 2202.6 | unfortunately, the release notes say.... | MOLAR::SIEGEL | MS: ZKO1-3/H18 DTN: 381-0035 | Tue Feb 04 1997 11:30 | 7 |
|
Gian,
The maximum version supported by PNV V4.1C is DU V4.0A.
Joanna
|
| 2202.7 | | CHEFS::ATTWOOL_J | | Wed Feb 05 1997 03:48 | 10 |
|
re: -.1
I too was at DU 4.0B and because of the problems I was originally
having with 4.1c (see a few notes back) I downgraded my system back to
4.0A. But that's not to say it didn't work, as I had the same problems
on 4.0A
Jka
|
| 2202.8 | PNV V41C client + Digital UNIX V4.0A doesn't work | CLINTO::DALLAVO | G.Alfredo Dall'Avo NSIS-Milan Italy | Fri Feb 07 1997 09:41 | 42 |
|
Joanna,
unfortunately I didn't read the previous reply ... I was
at the customer site.
I did the downgrade on the PNV server and on the clients of the
customer.
The problem is exactly the same as for the DU V4.0B.
Did you test the client/server interaction in DU V4.0A + PNV4.1C
configuration?
I did .... on the production systems of the customer.
They are very happy to pay our product tests as consultancy time!
The results of the tests follow:
SERVER CLIENT
====== ======
1) DU V4.0A <-- X --> DU V4.0A
PNV V4.1C ERROR PNV V4.1C
2) DU V4.0B <-- X --> DU V4.0B
PNV V4.1C ERROR PNV V4.1C
3) DU V4.0B <-------> DU V4.0*
PNV V4.1C OK PNV V4.1B
So I suppose that the problem is on the PNV V4.1C client's site.
I applied the workaround #3 to the customer production systems.
I IPMTed the problem. Now the customer is waiting for a patch.
Thanks.
Gian Alfredo
|
| 2202.9 | PNV V41C client + Digital UNIX V4.0A doesn't work | CLINTO::DALLAVO | G.Alfredo Dall'Avo NSIS-Milan Italy | Fri Feb 07 1997 09:41 | 42 |
|
Joanna,
unfortunately I didn't read the previous reply ... I was
at the customer site.
I did the downgrade on the PNV server and on the clients of the
customer.
The problem is exactly the same as for the DU V4.0B.
Did you test the client/server interaction in DU V4.0A + PNV4.1C
configuration?
I did .... on the production systems of the customer.
They are very happy to pay our product tests as consultancy time!
The results of the tests follow:
SERVER CLIENT
====== ======
1) DU V4.0A <-- X --> DU V4.0A
PNV V4.1C ERROR PNV V4.1C
2) DU V4.0B <-- X --> DU V4.0B
PNV V4.1C ERROR PNV V4.1C
3) DU V4.0B <-------> DU V4.0*
PNV V4.1C OK PNV V4.1B
So I suppose that the problem is on the PNV V4.1C client's site.
I applied the workaround #3 to the customer production systems.
I IPMTed the problem. Now the customer is waiting for a patch.
Thanks.
Gian Alfredo
|