| Title: | VAX MAILGATE for MEMO |
| Moderator: | STKHLM::OLSSON |
| Created: | Sat Feb 25 1989 |
| Last Modified: | Tue May 14 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 216 |
| Total number of notes: | 933 |
Hi Folks,
i get today an outage call from a customer with following situation:
by starting the memo-server (start 1) comes following message:
%.... status .....
%.... identification ....
%MRMEMO-W-NOSERVER, TARGET SERVER IS NOT ACCESSABLE
%SYSTEM-F-LINKEXIT, NETWORK PARTNER EXITED
the object at ncp (mrmemo1) has the id from the generated process, but the
connections to MRLISTEN are not available.
(MRMEMO$DIR:NETSERVER.LOG AND MRMEMO1.LOG are ok, no error messages)
after some time, i found out that the customer has defined a default
decnet entry at the characteristics from the executer node
....
Nonprivileged user id = DECNET
Nonprivileged password = DECNET
....
and there was an entry in the UAF with
DEFAULT: SYS$SPECIFIC:[DECNET]
LGICMD: LOGIN.COM
FLAGS: ... Restricted ....
b u t, no directory and of course no login available for this account.
i generate a directory, also a login.com, starts the server and
i t w o r k s
why needs MRMEMO the default decnet account for starting the server?
is it possible to change this (workaround: include username and password
by the object definition from
MRMEMO1 at the ncp?)
or what else can we do?
btw, the customer uses
MAILbus V3.1B
MR/MEMO V2.1
VMS V5.3-1
greetings from munich
Michael
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 66.1 | START needs new design | STKHLM::OLSSON | Anders Olsson, SIP Sweden | Fri Jan 18 1991 17:35 | 31 |
Hello Michael,
.0> why needs MRMEMO the default decnet account for starting the server?
.0> is it possible to change this (workaround: include username and password
.0> by the object definition from
.0> MRMEMO1 at the ncp?)
.0> or what else can we do?
When the START command is given, MRMMAN sends a connect request with
username and password to the MRMEMO account. The login command file in
the MRMEMO account starts the (detached) MRMEMO server process, returns
the process start status to MRMMAN and exits.
The server process now initializes and declares itself as a known network
object (number 0, name MRMEMO1). Meanwhile, MRMMAN tries to connect to
the server object WHITHOUT any username/password info in the connect
request. If the server has not yet declared itself as a network object,
the connect request will result in a login attempt.
It should work to include username and password in a MRMEMO1 object
definition as a workaround. But don't use the MRMEMO account, since the
login command file there expects to be accessed only by the MRMMAN
START command to start a new server.
We are aware of that the implementation of the START command have some
design flaws. A change in this area is quite high up on the wishlist
(even higher now because of this problem report).
Please let us know if the workaround works and is acceptable.
Anders
| |||||
| 66.2 | it's ok now | PEARS::SONNTAG | Michael Sonntag, TSSC-OIS, @MUH | Thu Feb 07 1991 11:49 | 9 |
Hello Anders,
sorry about my late reply, but i get in illness over 14 days.
the customer accept the workaround (he generate a new account with the
same groupuic as mrmemo) and it works fine.
thanks
Michael
| |||||