[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | PATHWORKS for OpenVMS (NetWare) Conf. |
| Notice: | Shipping on OpenVMS/Alpha and OSF/1 - ECOs=314.* - Kits=21.* |
| Moderator: | DELNI::GORCZYCA |
|
| Created: | Wed Nov 04 1992 |
| Last Modified: | Tue Jun 03 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 805 |
| Total number of notes: | 2930 |
Hi,
NVT has crashed twice since February. Here is the log file. Any ideas?
Thanks!
cindy
28-MAR-1997 11:27:19.32 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:19.39 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:19.47 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:19.54 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:19.61 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:19.67 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:19.74 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:19.81 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:19.87 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:19.96 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.02 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.09 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.16 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.22 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.29 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.37 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.44 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.51 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.58 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.69 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.79 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:20.91 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:21.14 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
28-MAR-1997 11:27:21.24 PTD$WRITE failed Device[1],
VMSstatus[0x000022E4]
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=00000028, PC=00114003, PSL=03C00004
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC
abs PC
00114003
00114003
00112A0E
00112A0E
001960D7
001960D7
0012562F
0012562F
NVT_CREATEPROC xon_ast 9635 00000052
00027E9E
8BFDE15F
8BFDE15F
000A7CCF
000A7CCF
MTS$MAIN main 2972 0000001B
00029CC3
28-MAR-1997 11:27:32.41 NVT Daemon Shutdown initiated...executing
ExitHandler
Server Statistics
Connections Recved Rejected Accpted Norm_Term Aborted
Shutdown
244 0 244 217 22 5
Network I/O #Reads ByteCount #Writes ByteCount
100567 198801 470748 12986937
Terminal I/O #Reads ByteCount #Writes ByteCount #Echoes
ByteCount
470301 12986582 100126 196560 0 0
28-MAR-1997 11:27:32.53 NVT Daemon ExitHandler done.
SYSTEM job terminated at 28-MAR-1997 11:27:33.16
0
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 797.1 | Hardware? | CPEEDY::FLEURY | | Thu Apr 03 1997 09:17 | 8 |
| The status reported (VMSstatus[0x000022E4]) resolves to:
%SYSTEM-F-DATALOST, data lost
I'd suspect that the device itself is having problems. Have you
checked the errorlog for entries?
Dan
|
| 797.2 | Ungraceful connection termination? | VMSNET::C_MANDERSON | | Thu Apr 03 1997 11:40 | 15 |
| Hi,
There does not appear to be any messages in any other log files. Could
it be an issue with the PC. For example, the user on a windows 95 pc
and is using KEAterm over NVT just shuts himself off without
disconnecting gracefully. Doesn't even run SHUTDOWN! The consultants
working with this individual to perform a more graceful shutdown. This
user causes problems about three times a week. If this user is killing
his 95 pc and the connection is still established, could this cause the
problem?
thanks!
cindy
|
| 797.3 | Please enter supporting info | CPEEDY::COOK | Just say NO to that AccViO! - Java!!! | Thu Apr 03 1997 12:38 | 10 |
| >>If this user is killing
>>his 95 pc and the connection is still established, could this cause
>>the problem?
It's certainly possible. However, we don't have any other reports
of a similar problem.
When you get a chance, please post the usual info that you'd
enter for a CLD, such as: ALPHA or VAX, and the version number of
PATHWORKS and version number of OpenVMS.
|
| 797.4 | Windows 3.1 | VMSNET::C_MANDERSON | | Fri Apr 04 1997 13:00 | 17 |
| Hi,
Sorry..
VAX
VMS 6.1
PATHWORKS for OpenVMS (NetWare)1.0-430d
The system isn't Windows 95 after all. It's a Windows 3.1 system. This
system is banged off by their fists and not powered off gracefully. My
customer apologizes for this incorrect info regarding the client
operating system. The application running on NVt via Keaterm is a timer
update program that transfers bond prices from VMS to the PC. The
customer suspects the user is impatient when the prices are being
downloaded to the pc and shut the pc off.
cindy
|