Premise PSMONITOR restarting PRKERNEL every 5 minutes

[ckindel]

My Premise instance is effed up. I obviously changed something in the past few weeks that has caused something bad.
 
Every 5 minutes or so my Builder connection would disconnect. Also there are no Events in Events.
 
I looked at the Windows Event Log on my server and PSMONITOR is restarting PRKERNEL about every 5 mintues:
 
EventID: 259
Premise Server shutdown by Premise Server Monitor.  A condition requiring a service restart was detected.   For more information, visit Premise Support Services at http://www.premisesystems.com/support.
 
At one point last week I did get a script engine queue length exceeded error. I had to restart the service manually. I'm wondering if I someone put recursion in one of my scripts? The stuff I tweaked was really simple though.
 
Sadly, I have no backups prior to that.
 
I see nothing else that would indicate why this is happening. 

 

[ckindel]

I've done the following:
 
- Restored .xdo files going back to 8/11, well before this started happening
- Disabled SMTPProxy, which I installed since then
- Disabled John in VA's Premise Web Services thingy
 
None of these fixed the problem.
 
I was about to restore the entire server back to my 8/11 backup but decided to reboot just to see. 
 
And after rebooting i haven't had a problem. 
 
Hmmm....

 

[samgreco]

Hate those kinds of problems.  You can dig forever and never really figure out what caused it.

 

[georgejm]

I'm having something very similar happening to me.  I too got the script engine exceeded queue length error once just before we left for vacation a couple of weeks ago, and haven't had one since.  PSMonitor isn't restarting the Kernel, but subscribed events in scripts and logic diagrams stop firing after a few hours.  Then mysteriously, they start working again after an hour or two.  I disabled all of my newer stuff, and restored from an older backup, but the issue is still happening.  Last night, I completely de-installed and reinstalled Premise thinking that I may have a corrupted file someplace.  I'll let you know if that fixes the problem for me. 
 
I wonder if we just got an MS patch that broke something...

 

[chucklyons]

As the guy who's probably the worst coder of all who visit here, including the google robots, I am relieved to hear that you guys have experienced the -stop restart issue.
 
I've seen it numerous times...the only thing I've ever been able to see is in the schema.xdo - error messages...I could open the schema.xdo in notebook++ (thanks, 123!), delete the 8 billion messages, then restart. It seemed to work.
 
John's work has always been tight, so I've never factored that in  ^_^

 

[georgejm]

I don't want to jinx myself, but reinstalling Premise seemed to do the trick for me.