This sounds like a communication problem. You did not say what
platform your ADSM server is running on or exactly what commmethod
you are running. We have had different problems with different types.
It would be helpful if you would include that information when
you call ADSM service. Also, assuming you are running SPX,
TLI if you are running OS2 server, Novell has provided many fixes
to the communication code both client and server.
Please call ADSM service if you have not done so already.
> Hello everyone. My two heaviest used 4.10 servers are dying during
> scheduled backups. They die in different ways, one time just locking up
> completely, and
> at another time losing IPX but still pinging. There are no abend messages or
> any other message on the console. The ADSM server activity log just says
> that the session started and timed out (about the time of the crash).
> The dsmsched and dsmerror logs don't have any messages relating to the
> problem.
Subject: Re: Can I run dsmc in OS_PROTECTED?
Instead of OS_PROTECTED, try running the following NCF file.
I would suggest only a subset of the commands. Please
read the explanations carefully!
# DETECT.NCF
#
# Author: NLM Certification Team, Novell Labs
# Date: July 6, 1995 Version 2.2
#
# This file is an published work of
# Novell Labs Division of Novell, Inc.
#
# This NCF sets various parameters to values
# appropriate for working through certification
# when you generally want the server to notify
# you and continue running when most NLM
# errors occur.
#
# It is to be used for NLM certification purposes
# only, and should not be used on a production
# server. Use on production server could have
# undesirable results.
#
# On SFT III servers this NCF must be run on
# the MSEngine.
SET ALLOC MEMORY CHECK FLAG = ON
# This sets the server to perform corruption
# checking in the alloc memory nodes.
# (4.x Utilities p328)
SET ALLOW INVALID POINTERS = ON
# This does allow invalid pointers to cause
# a nonexistent page (one above the physical
# memory of the server) to be mapped in. This
# setting will cause a read page fault notification
# when an attempt to read a nonexistent page
# in memory occurs. (4.x Utilities p329)
# (Getting Started p13) (NetWare v4.0 OS
# Architecture pA-4) (NLM Development and
# Tools Overview p147) (NLM Certification p31-5)
# SET CLIB MEMORY CHECKING = ON
# This parameter is commented out because it
# causes a noticeable drop in performance.
# You should set this parameter for at least
# one iteration of your exercising procedure.
# This is the NLM Library memory allocation
# system integrity checking and allocation
# tracking parameter. In the event of unreleased
# resources, this will cause CLIB to provide the
# address of the resource, the address of the
# function that originally allocated the resource
# and the size of the resource in bytes. This
# Parameter causes high timeslices and should
# Not be used in actual certification.
SET CONSOLE DISPLAY WATCHDOG LOGOUTS = ON
# This helps debug problems with your NLMs'
# client connections. (4.x Utilities p327)
# (NLM Certification p31-4) (Client Transport
# Protocol ch3) (Programmer's Notes for C ch30)
# (Using NetWare Services ch52)
SET DEVELOPER OPTION = OFF
# The options associated with the developer
# environment are set to OFF.
# This will cause NLMs with unhandled
# exceptions to be quarantined.
# (4.x Utilities p369) (Getting Started p15)
# (NetWare v4.0 OS Architecture pA-4)
# (NLM Development and Tools Overview p148-149)
# (NLM Certification p31-8)
SET DISPLAY LOST INTERRUPT ALERTS = ON
# This alerts the system console when a driver
# or board requests an ISR then drops the
# request before the CPU can respond.
# (4.x Utilities p370) (NLM Certification p31-2)
SET DISPLAY OLD API NAMES = ON
# This will alert you to update the API
# calls in your NLM. (4.x Utilities p368)
# (NLM Certification p31-3)
SET DISPLAY RELINQUISH CONTROL ALERTS = ON
# MANDATORY setting for certification
# This parameter must be set to ON during
# all certification procedures. This is not a test
# and does not take the place of SENTRY testing.
# (4.x Utilities p367) (NLM Certification p31-3)
# (NLM Development and Tools Overview ch3)
SET GLOBAL PSEUDO PREEMPTION = OFF
# MANDATORY setting for certification
# This MUST be set to off to catch high
# timeslices should they occur.
# (4.x Utilities p369) (NLM Certification p31-8)
SET HALT SYSTEM ON INVALID PARAMETERS = OFF
# This causes the system to display an alert
# and continue running when an invalid parameter
# or condition is detected.
# (4.x Utilities p366) (NLM Certification p31-7)
SET IMMEDIATE PURGE OF DELETED FILES = ON
# This is for convenience because many exercising
# procedures create and delete large files
# and/or large numbers of files. The server usually
# retains deleted files for possible later salvage,
# taking up valuable disk space. This setting is NOT
# for production servers. (4.x Utilities p340)
# (NLM Certification p31-4)
SET READ FAULT EMULATION = ON
# This causes the server to emulate reads from
# a nonpresent page in memory. (4.x Utilities p330)
# (NLM Development and Tools Overview p147-148)
# (NetWare v4.0 Architecture pA-3)
# (NLM Certification p31-5, 31-6)
SET READ FAULT NOTIFICATION = ON
# MANDATORY setting for certification
# This notifies the console and error log when
# emulated read page faults occur in memory.
# See the NetWare 4.x manual "Supervising the
# Network" pages 402-403 for information
# on viewing and clearing the error log.
# (4.x Utilities p330) (NetWare v4.0 Architecture pA-3)
SET SOUND BELL FOR ALERTS = ON
# This will cause a bell to sound whenever
# the system console displays an alert.
# (4.x Utilities p371) (NLM Certification p31-8)
SET UPGRADE LOW PRIORITY THREADS = OFF
# MANDATORY setting for certification
# This parameter must be set to OFF during all
# certification procedures. This setting will alert
# you to "busy waiting" failures in your NLM.
# See "NLM Certification p6-15 - p6-16 "No NLM
# shall prevent low priority threads from executing."
# (4.x Utilities p367) (NLM Certification p31-7)
# (NetWare v4.0 Architecture ch3)
# (NLM Development and Tools Overview p50-51)
SET WRITE FAULT EMULATION = ON
# This causes the server to emulate writes to
# a nonpresent page in memory.
# (4.x Utilities p330) (NetWare v4.0 Architecture
# pA-3, A-4) (NLM Certification p31-6)
# (NLM Development and Tools Overview ch10)
SET WRITE FAULT NOTIFICATION = ON
# MANDATORY setting for certification
# This notifies the console and error log when
# emulated write page faults occur in memory.
# See the NetWare 4.x manual "Supervising the
# Network" pages 402-403 for information
# on viewing and clearing the error log.
# (4.x Utilities p330) (NetWare v4.0 Architecture pA-4)
> My 2.1.5 Netware clients are crashing my servers. I tried to run dsmc in
> OS_PROTECTED but some of the modules fail to initialize. I realize this is
> meant for debugging new NLMS but I'm willing to put up with some performance
> degradation. I suspect I can't do this. Thanks.
|
