Circuit SVA-0, Load, Successful, Node = 9.15 (MADDY)
File = EWS$LIBRARY:EWS$GAB_075.SYS, Operating system
Ethernet address = 08-00-2B-09-12-F1
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 10-JUN-2014 20:07:25.38 %%%%%%%%%%%
Message from user AUDIT$SERVER on MOIRA
Security alarm (SECURITY) and security audit (SECURITY) on MOIRA, system id: 9217
Auditable event: Detached process login failure
Event time: 10-JUN-2014 20:07:25.27
PID: 20200123
Process name: _WSA1:
Username: SYSTEM
Process owner: [SYSTEM]
Image name: MOIRA$DKA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE
Status: %DECW-F-NOMSG, Message number 02DB8204
DECWindows is started...VAXELN loaded...but it still can't open graphics device? WINDOW_SYSTEM is set to 1 in MODPARAMS.DAT
200122 SERVER_00CE LEF 6 186 0 00:00:01.39 1709 312 N
[EWS$SERVER] 156Kb
I can't imagine I need to put the graphics card back in the boot node? That just wouldn't make sense!
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Mode and or duplex incompatibilities.
This can't be the problem in this case. I'm running both nodes inside
the same VM (VirtualBox), so they share the same NIC.
I have replaced the file copy by a screen copy:
NFT TI:=SNAKE::LB:[1,2]EXECUTIVE.HLP
(EXECUTIVE.HLP is 259. blocks)
and I can see random freezes.
A successful, uninterrupted transfer takes 7 seconds.
It hangs almost every time I write to disk:
NFT FOO=SNAKE::LB:[1,2]EXECUTIVE.HLP
I suppose virtualization needs some extra caution. I have to browse
simh at trailing-edge archive for what have been said about VirtualBox.
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Mode and or duplex incompatibilities.
This can't be the problem in this case. I'm running both nodes inside
the same VM (VirtualBox), so they share the same NIC.
I have replaced the file copy by a screen copy:
NFT TI:=SNAKE::LB:[1,2]EXECUTIVE.HLP
(EXECUTIVE.HLP is 259. blocks)
and I can see random freezes.
A successful, uninterrupted transfer takes 7 seconds.
It hangs almost every time I write to disk:
NFT FOO=SNAKE::LB:[1,2]EXECUTIVE.HLP
I suppose virtualization needs some extra caution. I have to browse
simh at trailing-edge archive for what have been said about VirtualBox.
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Everything else seems ok.
Could be many different reasons. All from general network load affecting things to thing like duplex, which Brian suggested.
Really hard to give a good explanation on why without having good access to all parts of the setup to be able to test and examine things.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Mode and or duplex incompatibilities.
This can't be the problem in this case. I'm running both nodes inside
the same VM (VirtualBox), so they share the same NIC.
I have replaced the file copy by a screen copy:
NFT TI:=SNAKE::LB:[1,2]EXECUTIVE.HLP
(EXECUTIVE.HLP is 259. blocks)
and I can see random freezes.
A successful, uninterrupted transfer takes 7 seconds.
It hangs almost every time I write to disk:
NFT FOO=SNAKE::LB:[1,2]EXECUTIVE.HLP
I suppose virtualization needs some extra caution. I have to browse
simh at trailing-edge archive for what have been said about VirtualBox.
--
Jean-Yves Bernier
Mode and or duplex incompatibilities.
This can't be the problem in this case. I'm running both nodes inside the same VM (VirtualBox), so they share the same NIC.
I have replaced the file copy by a screen copy:
NFT TI:=SNAKE::LB:[1,2]EXECUTIVE.HLP
(EXECUTIVE.HLP is 259. blocks)
and I can see random freezes.
A successful, uninterrupted transfer takes 7 seconds.
It hangs almost every time I write to disk:
NFT FOO=SNAKE::LB:[1,2]EXECUTIVE.HLP
I suppose virtualization needs some extra caution. I have to browse simh at trailing-edge archive for what have been said about VirtualBox.
--
Jean-Yves Bernier
Everything else seems ok.
Mode and or duplex incompatibilities.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
Circuit QNA-1, Dropped by adjacent node, Adjacent node = 1.13 (MIM)
"Dropped by adjacent node"? Does that mean that MIM decided to drop the
connection to me? How anti-social of it :-) It'd be nice if it said
why....
Actually it isn't just MIM - this seems to be happening with several nodes
on the bridge. The adjacency will come back up in a minute, and then get
dropped again.
Hmm. Could be serveral reasons. Do you have a max routers set too low on your machine maybe? We have quite a few routers on the bridge segment.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
