HP-UX 10.01 Backup Problem

[Sanjiv Sharma_1]

Dear Friends,
I am facing a problem with HP9000/827/H20 machine which is running on HPUX
10.01.
We are having a customized script which is used to take the
backup. Backup normally takes more than 30 min.. But for last few
days, after 10 or 15 min., the backup script is exiting with an error code
"memory fault ( core dump)". We tested the memory, all the memory is
detecting with out any problem. Swap also not getting utilized much. So to
isolate the problem, we made a script which will execute find command for
more than 15 min.. We got the same error here also after 10 to 15 min..
So we added 16 MB memory more to the system. Tried again. Same problem
exists still.
System is having 96MB memory now.
Please help me to solve the problem.

[melvyn burnard]

The memory fault message you are seeing has nothing to do with physical memory. It is more a case of the program that is running having a fault, which causes it to sore dump.
If you run the file command against hte core file it produces, you may get an indication of which area the failure is in.
I would also suggest you check for any recent changes, patch installs etc.
It may also help if you include the error message, along with the program itself.

[Sanjiv Sharma_1]

Dear Melvyn,

Enclosed please find the core dump file.

Pls. help me to understand the problem from it.

Thanks and Regards,
Sanjiv Sharma

[James Odak]

i think what the above person wanted was the program that you are running

instead of attaching the core file on your system change to the dir where the file is and type
file core
and
what core

these both may give you clues on what the problem is

or better, copy the response to here

another sugestion is to run the script line by line (not exactly line for line, just execute what the script does piece by piece) at the command promt and see just what is happening
core dumps are a pain
good luck

[Rick Garland]

The customized script has something in it that is not valid.

Does this script run with other machines - that may have a higher/lower OS rev or a different flavor of UNIX? There may be a command that the higher rev OS can handle but the lower rev OS chokes on - thus the memory fault.

(Could go the other way as well - lower OS has command that higher OS does not)

The script may be flavor or OS rev dependent.