I've define a service to run a DCL script that runs some python.
It works fine when one connection is made, but crashes the system (literally, it core dumps [or whatever the VMS word is]) on multiple connections.
Here's the service definition:
TCPIP> show service himsrv/full
Service: HIMSRV
State: Enabled
Port: 11337 Protocol: TCP Address: 0.0.0.0
Inactivity: 5 User_name: HIMSRV Process: HIMSRVD
Limit: 1 Active: 0 Peak: 1
File: DKA0:[HIMSRV]HIMSRVTCP.COM
Flags: Listen Multi
Socket Opts: Rcheck Scheck
Receive: 0 Send: 0
Log Opts: None
File: not defined
Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0
sampsa <sampsa at mac.com>
mobile +961 788 10537
On Sat, Apr 27, 2013 at 5:30 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Sat, 27 Apr 2013, Sampsa Laine wrote:
After a disaster on HILANT, I had to rebuild the cluster.
What was the disaster?
Anyone got quick howto on defining / enabling a cluster alias?
sampsa
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Hello!
What was the disaster? I thought you knew, the monsters besieging your
location moved back to bombard Sampsa with issues. No seriously, what
happened? And was it Dave's fault?
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Sat, 27 Apr 2013, Sampsa Laine wrote:
After a disaster on HILANT, I had to rebuild the cluster.
What was the disaster?
Anyone got quick howto on defining / enabling a cluster alias?
sampsa
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
El 27/04/2013, a les 18:34, Sampsa Laine <sampsa at mac.com> va escriure:
For now, route through SG1.
Oki doki. I'll keep the circuit up anyway.
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
I rebuilt GORVAX, it was very weirdly unstable - it's using UCX now, not MULTINET.
For now, route through SG1.
sampsa <sampsa at mac.com>
mobile +961 788 10537
On 27 Apr 2013, at 18:49, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
Hello,
Since some days all my traffic is being routed by SG1. My "primary" circuit should go via GORVAX, thru 46.65.175.115, but that IP address does not answer my pings. Did I miss an announced change, or is it simply temporarily down?
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
Hello,
Since some days all my traffic is being routed by SG1. My "primary" circuit should go via GORVAX, thru 46.65.175.115, but that IP address does not answer my pings. Did I miss an announced change, or is it simply temporarily down?
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On Thu, 25 Apr 2013, Brian Schenkenberger, VAXman- wrote:
"Brian Schenkenberger, VAXman-" <system at TMESIS.COM> writes:
Sampsa Laine <sampsa at mac.com> writes:
I've somehow managed to screw up the boot node of HILANT, basically =
KUHAVX will boot fine by itself (VAXCLUSTER set to 0) but when I try to =
boot it as the boot node for the cluster I get this error:
%SYSINIT-E, error mounting system device, status =3D 0072832C
Any ideas?
$ EXIT %X0072832C
%MOUNT-F-DIFVOLMNT, different volume already mounted on this device
You have the system disk mounted elsewhere in the cluster.
Go to one of the other members:
$ MCR SYSMAN
SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> DO DISMOUNT/OVER=CHECK <the-volume-designation>
FYI, when in doubt, $ HELP/MESSAGE can be your friend too:
$ HELP/MESSAGE DIFVOLMNT
.... or ...
$ HELP/MESSAGE/STATUS=%x0072832C
Both will return:
DIFVOLMNT, different volume already mounted on this device
Facility: MOUNT, Mount Utility
Explanation: Previously, a different volume was mounted on this device
on another node in the cluster. The device may be in mount
verification on the other node. Either the original volume
was removed from the device and replaced with another, or its
volume identification was overwritten.
User Action: Restore the previously mounted volume to the device. If
this is not possible, dismount the device on all nodes that
currently have it mounted. Then retry the mount operation.
All those good people, now made redundant by HP, in the VMS documentation
department didn't write all this stuff simply because they couldn't get a
book published in the boof-of-the-month club. ;)
Very unfortunate. The VMS documentation is fantastic.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
