![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We just implemented a Linux RedHat ES4 server with PSQL ver 9.2 and Samba shares. We have a vb application that can run from the server OR the desktop accessing the db through the PSQL ODBC client. In either scenario, if more than one user is modifying data, the mkde crashes. The only way I can recover the server from the crash to is to run mkded -force, then mkded -start in a terminal session. I am stumped where to start resolving this issue. Does anyone have any similar experiences they have resolved?? Thanks!! Liz |
#3
| |||
| |||
|
|
Hi Liz, What does PVSW.LOG say? Have you installed a client on your desktops (I assume they're Windows clients)? If so then you can use Pervasive utilities to simulate the same situation and possibly get some better responses prior to the mkde crashing. Liz ha scritto: We just implemented a Linux RedHat ES4 server with PSQL ver 9.2 and Samba shares. We have a vb application that can run from the server OR the desktop accessing the db through the PSQL ODBC client. In either scenario, if more than one user is modifying data, the mkde crashes. The only way I can recover the server from the crash to is to run mkded -force, then mkded -start in a terminal session. I am stumped where to start resolving this issue. Does anyone have any similar experiences they have resolved?? |
#4
| |||
| |||
|
|
Hi Liz, What does PVSW.LOG say? Have you installed a client on your desktops (I assume they're Windows clients)? If so then you can use Pervasive utilities to simulate the same situation and possibly get some better responses prior to the mkde crashing. Liz ha scritto: We just implemented a Linux RedHat ES4 server with PSQL ver 9.2 and Samba shares. We have a vb application that can run from the server OR the desktop accessing the db through the PSQL ODBC client. In either scenario, if more than one user is modifying data, the mkde crashes. The only way I can recover the server from the crash to is to run mkded -force, then mkded -start in a terminal session. I am stumped where to start resolving this issue. Does anyone have any similar experiences they have resolved?? |
#5
| |||
| |||
|
|
Hi Wayne...thanks for the reply. I can check the log....users have an application installed locally on their Wintel machines, but the executable can be run from the server on a mapped drive as well. That is how we had it running on Novell in an Oracle environment. I know there is a pvsw.log on the local machine, what about any logs on the psql share on Linux?? Thanks...I have been pulling out hair for a couple of days now...not a pretty sight ;o) Liz Wayne wrote: Hi Liz, What does PVSW.LOG say? Have you installed a client on your desktops (I assume they're Windows clients)? If so then you can use Pervasive utilities to simulate the same situation and possibly get some better responses prior to the mkde crashing. Liz ha scritto: We just implemented a Linux RedHat ES4 server with PSQL ver 9.2 and Samba shares. We have a vb application that can run from the server OR the desktop accessing the db through the PSQL ODBC client. In either scenario, if more than one user is modifying data, the mkde crashes. The only way I can recover the server from the crash to is to run mkded -force, then mkded -start in a terminal session. I am stumped where to start resolving this issue. Does anyone have any similar experiences they have resolved?? |
#6
| |||
| |||
|
|
Hi Wayne...thanks for the reply. I can check the log....users have an application installed locally on their Wintel machines, but the executable can be run from the server on a mapped drive as well. That is how we had it running on Novell in an Oracle environment. I know there is a pvsw.log on the local machine, what about any logs on the psql share on Linux?? Thanks...I have been pulling out hair for a couple of days now...not a pretty sight ;o) Liz Wayne wrote: Hi Liz, What does PVSW.LOG say? Have you installed a client on your desktops (I assume they're Windows clients)? If so then you can use Pervasive utilities to simulate the same situation and possibly get some better responses prior to the mkde crashing. Liz ha scritto: We just implemented a Linux RedHat ES4 server with PSQL ver 9.2 and Samba shares. We have a vb application that can run from the server OR the desktop accessing the db through the PSQL ODBC client. In either scenario, if more than one user is modifying data, the mkde crashes. The only way I can recover the server from the crash to is to run mkded -force, then mkded -start in a terminal session. I am stumped where to start resolving this issue. Does anyone have any similar experiences they have resolved?? |
![]() |
| Thread Tools | |
| Display Modes | |
| |