Gary,
Is the binary CSTM patch that you created required now?
-Craig
From: Gary Robillard <[log in to unmask]>
To: [log in to unmask]
Sent: Wednesday, May 27, 2015 3:36 PM
Subject: Re: Mpe: CSTM
As Mark Ranft indicated, the most common problem is the network being
stopped and restarted
without stopping and restarting the cstm processes. The network socket
handles become stale
and of course, non-functioning...
Another issue that will prevent them from running is if loopback is not
setup.
make sure you have an entry like:
127.0.0.1 localhost loopback me myself local
in hosts.net.sys and that the loopback interface has been started with
NETCONTROL START;NET=LOOP
Thanks,
Gary Robillard
On Wed, May 27, 2015 at 5:23 PM, Tim O'Neill <[log in to unmask]> wrote:
> Since SYSDIAG has become CSTM, I ran CSTM. It suggested that
> name-to-address resolution was not working, so I went and verified
> that it was working. As proof, NSLOOKUP run from Posix shell returns
> correct IP of the FQDN.
>
> I can CSTM again.
> Within CSTM, I ran STMSTART then CONNECTSYS. The same error recurred.
> I.e. it cannot connect to itself.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
