1830895 Members
1508 Online
110017 Solutions
New Discussion

Re: make_recovery errors

 
SOLVED
Go to solution
Ted Flanders_1
Advisor

make_recovery errors

I get the following errors on my HP9000 K220 running HPUX.
/etc/ is not expected : no such file or directory
make_recovery (621) : WARNING, Call to lstat failed.
session denied, no such file or directory

it says this over and over. What do I need to do to fix these errors?
Thanks.
11 REPLIES 11
Ted Flanders_1
Advisor

Re: make_recovery errors

Sorry.......HPUX 10.20
Stefan Farrelly
Honored Contributor

Re: make_recovery errors


have you checked the make_recovery log in /var/opt/ignite/logs for more detail on the error ? Sounds like something strange with /etc on your server. Is it permissioned correctly (555 bin:bin), any strange symlinks in it/to it ? is it a directory under / (not its own mountpoint/filesystem)
Im from Palmerston North, New Zealand, but somehow ended up in London...
Patrick Wessel
Honored Contributor

Re: make_recovery errors

lstat is a system call that reads in some information about a file name or symbolic link. lstat is supposed to be used to read links, while stat is supposed to be used to read file info. "Call to lstat failed" isn't really saying much except that something failed. What is unclear is if the call itself failed, so lstat didn't run, or if lstat returned some bad information.

Do you start make_recovery direct from the command line or out of a script? Which options do you use?
There is no good troubleshooting with bad data
Ted Flanders_1
Advisor

Re: make_recovery errors

I checked the logs, not much more info in them about the errors. ; Permissions are set at 555.
I run make_recovery -A -C from the command line.
Cheryl Griffin
Honored Contributor
Solution

Re: make_recovery errors

The error message points to "/etc/" which "is not expected". What is the background information for this? Did you run make_recovery in preview mode then modify the lists of files to be backed up, then resume the make_recovery? OR What's the history with the /etc/ directory? Any other problems lately? Does the system need to be fsck'd?? Are there any "strange" files in /etc... something that does not belong there?
"Downtime is a Crime."
Stefan Farrelly
Honored Contributor

Re: make_recovery errors


Ted, what version of ignite are you using ? a recent version I hope. If not, try it.
Either its an ignite bug or you have something strange with /etc on your server. Whats the output from bdf and ls -ld /etc on your server ?
Im from Palmerston North, New Zealand, but somehow ended up in London...
Ted Flanders_1
Advisor

Re: make_recovery errors

I do an ls -l on /etc and get these errors :
-rw-rw-rw root sys August 18 1998
is not expected
'newline orion : unknown host denied
ed.> line orion> ected>> 0 ;
-rw-rw-rw root sys August 18 1998 not expected
er^ cror : newl
not expected. > ed. > line orion ected >.
Stefan Farrelly
Honored Contributor

Re: make_recovery errors


My goodness. Sounds like some funny control characters in there. Do this command instead;

ls -ld /etc* | vis

This will show any control characters so we can remove them.
Im from Palmerston North, New Zealand, but somehow ended up in London...
Ted Flanders_1
Advisor

Re: make_recovery errors

That only gave me back the permissions and information about the /etc file.
It looks to me like it is trying to write the file named "error" which is a file with no bytes in it, and this is what is causing this error. How do you remove a file that isnt there?
Cheryl Griffin
Honored Contributor

Re: make_recovery errors

Ted,
there are two log files in /var/opt/ignite/logs.
makrec.log1 contains any errors encountered during the make_recovery process.
makrec.log2 contains a listing of all the files/directories that were recorded to tape.

You said you scanned them but didnt find anything relevant to the error? Can you post any details from the logs here which may help us?
"Downtime is a Crime."
Ted Flanders_1
Advisor

Re: make_recovery errors

I removed two files in the /etc directory, "ror" and a "-" file. I ran make_recovery -A -C and did not recieve any more errors. Thanks for pointing me in the right direction! This forum sure is a big help for us "newbies".