- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Ignite backup find_files command fails status ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-10-2008 07:57 AM
тАО07-10-2008 07:57 AM
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?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-10-2008 10:03 AM
тАО07-10-2008 10:03 AM
Re: Ignite backup find_files command fails status 141
Pls go through the below thread may be it will help 4 U.
http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1215712559643+28353475&threadId=1167906
BR/
Yaqub
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-10-2008 11:05 AM
тАО07-10-2008 11:05 AM
Re: Ignite backup find_files command fails status 141
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-10-2008 10:09 PM
тАО07-10-2008 10:09 PM
Re: Ignite backup find_files command fails status 141
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2008 06:42 AM
тАО07-11-2008 06:42 AM
Re: Ignite backup find_files command fails status 141
[/] 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2008 06:51 AM
тАО07-11-2008 06:51 AM
Re: Ignite backup find_files command fails status 141
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2008 09:24 AM
тАО07-11-2008 09:24 AM
Re: Ignite backup find_files command fails status 141
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2008 12:43 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2008 01:14 PM
тАО07-11-2008 01:14 PM
Re: Ignite backup find_files command fails status 141
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2008 04:00 PM
тАО07-11-2008 04:00 PM
Re: Ignite backup find_files command fails status 141
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
- Tags:
- unprintable chars