I need assistance with a problem we are experiencing.  We currently operate
two seperate stores via the original HTTP Server.  We recently upgraded to
5.1 from 4.5 and since have encountered a sigkill by qwtpitpp on a daily
basis.

The pages are created using net.data on both 'stores' but only encounter
sigkill on one store.  This is by far the most used and I'm wondering if
there is some attribute I need to adjust to keep the store from crashing.
Once I stop and restart the server instance everything is normal for
another day.

Here is the job log entry that appears each time the store goes down.  Does
anyone know how to eliminate this problem.

Thanks in advance,
Mark A McCarty
Navy Exchange Service Command

CPC1224    Completion              50    11/04/02   10:09:01   QWTPITPP
QSYS        0695     *EXT                      *N
                                     Message . . . . :   Job ended
abnormally.
                                     Cause . . . . . :   A SIGKILL signal
was received for the job. The action for
                                       the signal was to terminate the job.



***************************defiant************************************
This email and any files transmitted with it are intended solely for
the use of the individual or agency to whom they are addressed. If
you have received this email in error please notify the Navy Exchange
Service Command e-mail administrator.

This footnote also confirms that this email message has been scanned
for the presence of computer viruses.

messaging_support_team@nexnet.navy.mil
**********************************************************************



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.