Operating System - HP-UX
1748127 Members
3664 Online
108758 Solutions
New Discussion юеВ

Re: Ignite backup find_files command fails status 141

 
SOLVED
Go to solution
Frank Copeland
Advisor

Ignite backup find_files command fails status 141

Greetings,
We run and Ignite backup of our 3 unix servers each night. Last night we recieved these error(s) on all three servers:
WARNING: The pax command returned a non-zero exit status (exit status 1).
ERROR: The find_files command failed (exit status 141).

From what I understand a single occurance of this may indicate a bad tape or a drive problem. Three in one night makes me think otherwise. Here's the configuration:
HP-UX 11.23 all three servers.
DDS3 tape drives (one for each server)
Host machine is RX6600 with HP-UX Host.
Each is a VM guest on the RX6600 (again all three running UX 11.23)
Ignite Version C.7.4.155 (x3)

I've run tar backups to each of the drives this morning with no problem. I ran Ignite backups to all three servers with no problem every other morning this week.

No errors that I can see in syslog.log on any of the servers (including the VM host). What should I be looking at next, and after that?
11 REPLIES 11
YAQUB_1
Respected Contributor

Re: Ignite backup find_files command fails status 141

Frank Copeland
Advisor

Re: Ignite backup find_files command fails status 141

The note you sent was imformative but focused on exit status 1. Our Ignite backup didn't finish with warnings but with failure that I assume is due to the "find_files command failed (exit status 141)". Attached is a standard out/error file from one of the servers.
Dennis Handly
Acclaimed Contributor

Re: Ignite backup find_files command fails status 141

>Attached is a standard out/error file from one of the servers.

That has:
* Archiving contents of lex06 via tar image to local device /dev/rmt/0mn.
pax: write : No such file or directory
pax: A write error has occurred.
WARNING: The pax command returned a non-zero exit status (exit status 1).

It appears there is a file "write" that isn't there. Like:
pax -w -f foo.tar write

Do you have such a file named "write"? Or is ignite messing up and putting a bogus "write" on the pax command line?
Frank Copeland
Advisor

Re: Ignite backup find_files command fails status 141

There is a file called "write" on each guest and the host VM. Listing for that file follows:
[/] lex08-ROOT->ll /usr/bin/write
-r-xr-xr-x 1 bin bin 23852 Mar 26 2004 /usr/bin/write

[/roots] uxvmadm1-ROOT->file /usr/bin/write
/usr/bin/write: ELF-32 executable object file - IA64

I would suppose it belongs there and is used by Ignite and other processes. It has been part of the OS for all earlier versions of UX I've used.
Frank Copeland
Advisor

Re: Ignite backup find_files command fails status 141

I see. There's an implication that the PAX command or Ignite are trying to execute the write command but are possibly trying to execute with a corrupted PATH variable, or have the explicit /dir/path/write coded in the command, but for the wrong dir path. The script that our root cron runs to execute make_tape_recovery doesn't do anything to set or modify the PATH. I will modify that script with PATH=/usr/bin:$PATH and see if the performance improves.
Frank Copeland
Advisor

Re: Ignite backup find_files command fails status 141

Modifing Path didn't provide any change in the behavior. Still bombing at the end with:
pax: write : No such file or directory
pax: A write error has occurred.
WARNING: The pax command returned a non-zero exit status (exit status 1).
ERROR: The find_files command failed (exit status 141).

Also did a for file named ":" and came up empty. If you know of someone who may have an idea please send them here. Thanks
Hasan  Atasoy
Honored Contributor
Solution

Re: Ignite backup find_files command fails status 141

hi frank ;

are you using dds2 cartridges ?

please test with a larger capacity cartridges.
it seems that cartridges full at some point and pax exit with an exit code.

Hasan
Frank Copeland
Advisor

Re: Ignite backup find_files command fails status 141

They ARE dds2 tapes. Is theimplication that the process has reached the end of the media and just errors out? Once upon a time if we reached the end of a tape during a make_tape_recovery it prompted that we needed to insert a new tape, didn't it? I could be thinking of sysback or mksysb from AIX but should be similar regardless of OS. We'll I've replaced with DDS3 tapes now and I'll see later today if that solves the problem. That is the best notion I never thought of so far.
Dennis Handly
Acclaimed Contributor

Re: Ignite backup find_files command fails status 141

>Also did a for file named ":" and came up empty.

The name of the file is "write". If you do the pax command I showed, you get the error message as you got:
pax -w -f foo.tar write

As to how ignite gets that, I don't know. I suppose there could be unprintable chars? So use "find / -name "*write*".

>I would suppose it belongs there

Yes, that's write(1), not the one with your problem.

>PAX command or Ignite are trying to execute the write command

No, the fact that the word "write" was placed on the pax command line.
Can you look in these for "write":
/var/opt/ignite/recovery/2008-07-10,01:30/flist
/var/opt/ignite/recovery/2008-07-10,01:30/recovery.log