Re: [Hardhats-members] Linux GT.M Error message

2005-04-05 Thread Lloyd Milligan
- Original Message - From: Mark Street [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Monday, April 04, 2005 3:53 PM Subject: [Hardhats-members] Linux GT.M Error message Well, I finally tweaked it enough to get some sort of error message. Things are going downhill fast... I have

[Hardhats-members] Linux GT.M Error message

2005-04-04 Thread Mark Street
Well, I finally tweaked it enough to get some sort of error message. Things are going downhill fast... I have 20+- mumps processes running and error messages every second or so. ... I think I broke something... You never learn if you don't break something... Error message below.

Re: [Hardhats-members] Linux GT.M Error message

2005-04-04 Thread Kevin Toppenberg
Mark, Comment below: --- Mark Street [EMAIL PROTECTED] wrote: Well, I finally tweaked it enough to get some sort of error message. Things are going downhill fast... I have 20+- mumps processes running and error messages every second or so. ... I think I broke something... You never

Re: [Hardhats-members] Linux GT.M Error message

2005-04-04 Thread Bhaskar, KS
Is GT.M writing messages in your system log? This looks like GT.M may be doing a periodic ZSHOW dump (refer to Programmers Guide on documentation of ZSHOW, which is a GT.M command). What is causing GT.M to do a ZSHOW? It could be a mupip interrupt (USR1 signal) that has a signal handler that

Re: [Hardhats-members] Linux GT.M Error message

2005-04-04 Thread Mark Street
Bhaskar, KS said: Is GT.M writing messages in your system log? This looks like GT.M may be doing a periodic ZSHOW dump (refer to Programmers Guide on documentation of ZSHOW, which is a GT.M command). What is causing GT.M to do a ZSHOW? It could be a mupip interrupt (USR1 signal) that has a

Re: [Hardhats-members] Linux GT.M Error message

2005-04-04 Thread Michael Zacharias
If it is an assert failure as indicated in $ZSTATUS, the problem could be with the database. The offending line of code is at ERR2+10^%ZTMS which is trying to get a lock on ^%ZTSCH(ER) gtm ZP ERR2+10^%ZTMS L +^%ZTSCH(ER) H 1 S ZTERROH=$H I would try stopping all of your mumps process to

Re: [Hardhats-members] Linux GT.M Error message

2005-04-04 Thread Bhaskar, KS
Mark -- I have no idea what all the VistA configuration information does, but one person I showed the dump to wondered if you were perhaps running out of lock space. The LKE utility will tell you about lock usage. Lock space is allocated in shared memory when a database is first opened. To

Re: [Hardhats-members] Linux GT.M Error message

2005-04-04 Thread Mark Street
Well, I guess I can rule out the database. does this output look OK for a virtually empty system? Hmmm. Back to square 1 and back down the yellow brick road. [EMAIL PROTECTED] vista]$ mupip integ File or Region: g/mumps.dat No errors detected by integ. Type Blocks

RE: [Hardhats-members] Linux GT.M Error message

2005-04-04 Thread Bhaskar, KS
Yes, that's a clean integ report. -- Bhaskar -Original Message- From: [EMAIL PROTECTED] on behalf of Mark Street Sent: Mon 4/4/2005 8:20 PM To: hardhats-members@lists.sourceforge.net Cc: Subject:Re: [Hardhats-members] Linux GT.M Error message Well, I guess I can rule