topic Re: Error when start a job??? in Operating System - HP-UX

Error when start a job???

Leonard Galinsky — Thu, 15 Nov 2001 17:48:30 GMT

When I start a job I receive the following error:
PID 9719 killed due to text modification or page I/O error
path.... [53]: 9753 killed

My question is, what is causing this error and what is it & how to fix it??

Re: Error when start a job???

someone_4 — Thu, 15 Nov 2001 17:51:43 GMT

Here are two docs hope they help

http://us-support.external.hp.com/cki/bin/doc.pl/sid=d1d86b070b9e3609a3/screen=ckiDisplayDocument?docId=200000048829052

http://us-support.external.hp.com/cki/bin/doc.pl/sid=d1d86b070b9e3609a3/screen=ckiDisplayDocument?docId=200000019779384

Re: Error when start a job???

harry d brown jr — Thu, 15 Nov 2001 17:52:49 GMT

(1) WHat OS level?
(2) Are your patches up to date?
(3) Do you have adequate paging space and memory?
(4) What kind of process?
(5) does this happen with every process?

live free or die
harry

Re: Error when start a job???

someone_4 — Thu, 15 Nov 2001 17:57:15 GMT

Harry you are soo right there. I am sitting here jumping for an answer .. but forgot to ask some important questions.hmmm

Lets see what he says..

Re: Error when start a job???

Leonard Galinsky — Thu, 15 Nov 2001 18:11:41 GMT

HPux 11.0
Patches are up to date as of July 01
This happens when we run a ADS job via LSF
Paging space & memory have never been an issue before

Re: Error when start a job???

Paula J Frazer-Campbell — Thu, 15 Nov 2001 18:27:42 GMT

Leonard

Does the job stop immediatly after starting or does it run for a while?

On other sessions run top and glance and watch what is happening to memory swap and cpus.

Paula

Re: Error when start a job???

Leonard Galinsky — Thu, 15 Nov 2001 18:59:13 GMT

This happens with every process (aDS & Cadence). It gives the error right after issue the command, there is no access to the program

Re: Error when start a job???

Bill Hassell — Thu, 15 Nov 2001 19:33:02 GMT

The text modification error portion means that the code was changed after the program was loaded into memory. This is unlikely *except* over NFS. Are the program(s) located on an NFS disk? If so, the network may be overloaded--check nfsstat.

Otherwise, it may be due to an actual I/O error onn the disk where the exzecutable is located, or perhaps the disk where required shared libraries are located may be having problems. Check syslog.log and make sure ESM (online diagnostics and notifidation) is installed and running.

Re: Error when start a job???

Leonard Galinsky — Thu, 15 Nov 2001 19:44:51 GMT

It is running NFS
There are no errors in syslog.log
How would I access ESM or how can I tell if it is running?

Re: Error when start a job???

T G Manikandan — Fri, 16 Nov 2001 11:15:49 GMT

Hello,

When installing a patch on the
server, the corresponding executable file on a server's disk associated with a process running on a client can be over written,
which can result in the client process dying with the error:
Pid killed due to text modification or page I/O error
*I am not sure*
rebooting the clients may solve the problem.

Re: Error when start a job???

T G Manikandan — Fri, 16 Nov 2001 11:42:05 GMT

Hello,
First try touching the file
before stating the job.
Just mofifying the time stamp!!

Thanks