![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi All, I'm running Pervasive.SQL V8.5 on Redhat 9. My application runs for a while and then suddenly the application has stop. And are getting status 116 I've check the /var/log/messages I'm seeing this error "mkded: LsnThrd: beginthread(SelectThread) error=12". Can anyone help on this one? thanks jhun |
#3
| |||
| |||
|
|
I'm running Pervasive.SQL V8.5 on Redhat 9. My application runs for a while and then suddenly the application has stop. And are getting status 116 I've check the /var/log/messages I'm seeing this error "mkded: LsnThrd: beginthread(SelectThread) error=12". |
#4
| |||
| |||
|
|
I'm running Pervasive.SQL V8.5 on Redhat 9. My application runs for a while and then suddenly the application has stop. And are getting status 116 I've check the /var/log/messages I'm seeing this error "mkded: LsnThrd: beginthread(SelectThread) error=12". Status 116 is usually a Workgroup engine message and, though you weren't specific about which Pervasive.SQL V8.5 you are running, one would assume it is the server engine if it is running on Redhat 9, I've never seen it from a server engine. We all know why one has to be careful about assuming things without enough specfic accurage information though :-) You also didn't say what you application was running on, but I'm guessing it's on Windows so if I were you I would check for a workgroup engine running on that PC and turn off the local access so the client, and also the application, is forced to go through the server engine via the requester rather than use the workgroup engine. Please excuse me if your application is a Linux app. If the error=12 is the same as a Status 12, then it could be a pathing issue of some sort since it can't find the file. You can download and run PSA to detect if a workgroup engine is local the the PC the application runs on. Regards, JR |
#5
| |||
| |||
|
|
Hi John, I'm very sorry for lack of information actually, I'm running pervasive.sql v 8 server on redhat machine. My application is on windows and we're using Magic software. I've tried lowering the Max Microkernel Memory Usage from 90 to 50. Also their are few users now accessing that server. And now I'm not seeing the above error. One thing I've notice in version 8 is that I'm only seeing one mkded process, compared with 2000i that spawns a lot of processes. Are all the processes being share with only one mkded process? Btw, I'm taking the advice of Leonard of lower the Max Microkernel Memory Usage to 40 or 0, what's your take on this one? Thanks, Jhun Bacala jrothgeb (AT) pervasive (DOT) com (JohnR) wrote in message news:<bf1688a9.0402191011.21a1b68f (AT) posting (DOT) google.com>... I'm running Pervasive.SQL V8.5 on Redhat 9. My application runs for a while and then suddenly the application has stop. And are getting status 116 I've check the /var/log/messages I'm seeing this error "mkded: LsnThrd: beginthread(SelectThread) error=12". Status 116 is usually a Workgroup engine message and, though you weren't specific about which Pervasive.SQL V8.5 you are running, one would assume it is the server engine if it is running on Redhat 9, I've never seen it from a server engine. We all know why one has to be careful about assuming things without enough specfic accurage information though :-) You also didn't say what you application was running on, but I'm guessing it's on Windows so if I were you I would check for a workgroup engine running on that PC and turn off the local access so the client, and also the application, is forced to go through the server engine via the requester rather than use the workgroup engine. Please excuse me if your application is a Linux app. If the error=12 is the same as a Status 12, then it could be a pathing issue of some sort since it can't find the file. You can download and run PSA to detect if a workgroup engine is local the the PC the application runs on. Regards, JR |
![]() |
| Thread Tools | |
| Display Modes | |
| |