Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SCO Unix Memory Issue?

Status
Not open for further replies.

ItsChrisJ

MIS
Joined
Jul 22, 2003
Messages
2
Location
US
OK, first off, I am not a UNIX admin, I'm a software support tech for a UNIX based software called Medical Manager. I know the software in and out, and am usually able to install, set up, and troubleshoot the application through an ANSI terminal emulation. Unfortunately, I am stuck with an issue that seems to be OS based, and I don't know enough about SCO to isolate it. I don't have all the info on me tonight, but if you need version info and such to help, let me know, and I'll pull it off the site first thing in the morning. Here's the issue:

When I reach the point in the application where I would transmit files to a remote server, via a modem connection, I am getting the following string of errors:

"System Write Error 0 (this repeats 11 times)

Memory Fault

A system call returned error code 139. "

My handy dandy UNIX troubleshooting tips indicated this is a possible memory issue...corruption, or swap file size problem. I ran df -v against the box and both mounted shares are fine... DEV/ROOT at 12%, and DEV/BOOT at 40%. I am stuck, and the UNIX admins around the shop are harder to get a hold of than a beer and a playboy in baghdad. Any tips, tricks, or secrets would be greatly appreciated. Let me know what additional info to provide...I'll have it posted by 7:15 AM EST.

 
This is the (short) explanation of errno 139 for OSR 5.0.x:
[EISNAM] (139) Is a name file
A name file (semaphore, shared data, and so on) was specified when not expected.

Hope This Help
PH.
 
Hi Chris,
Have you solve your problem? E-mail me the result. I will try to help you. Which Medical Manager co. are you
with? There were a couple of posts in the past related to
this software.
thanks hershey1975@excite.com
 
Hi all. Well, it turns out the error was related to one of those tiny, tiny bugs in the TERM scripts. The first dataset was transmitting fine; only the second was affected. So I went through every configuration screen in the first dataset and took screen shots, then compared them line by line to the second. The only difference? One referenced port ttyA01, the other ttya01. Gawd...

At any rate, problem solved, everything is working OK now. I work at the Southeast Regional Headquarters of Medical Manager in Tampa, FL.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top