Operating System - HP-UX
1747984 Members
4649 Online
108756 Solutions
New Discussion юеВ

Re: make_net_recovery problems

 
SOLVED
Go to solution
Velda
Advisor

Re: make_net_recovery problems

Thank you for the idea, but I do not have the tusc on my systems.
But I have looked with ps which gzip was active during the make_net_recovery command, and it is the one in /usr/contrib/bin, and it is 1.3.5

So no other ideas.
Gzip should be OK, largefiles flag should be OK, and I do not know what else to look for.
Dennis Handly
Acclaimed Contributor

Re: make_net_recovery problems

>I do not have the tusc on my systems.

Just download it:
http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.10/
Velda
Advisor

Re: make_net_recovery problems

Maybe some other time.
For this it is not needed, since it IS pulling gzip 1.3.5

I frankly have no ideas any more.
Dennis Handly
Acclaimed Contributor

Re: make_net_recovery problems

>I frankly have no ideas any more.

Besides tracing which programs are executing, tusc can show the actual system call that is getting that error and printing "gzip: stdout: File too large"
Torsten.
Acclaimed Contributor

Re: make_net_recovery problems

I'm not sure if you already tried to re-export / re-mount. Did you?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Velda
Advisor

Re: make_net_recovery problems

Yes I did.
umount
mount
Even rebooted the server, blast it (it has a /atc/fstab entry all its own :-))).
Would the reexport be required also?
Velda
Advisor

Re: make_net_recovery problems

Dear all,
To thank you for help, and to say that the problem has been solved.
How? I am not sure, but here is what happened :
Ignite server and client had different Ignite versions (server's was higher), and that was fixed (just to mention when I tried to make a make?net?recovery from Ignite server to Ignite server I got the same error, so it should not have been this, right?).
Also Ignite server was rebooted.
That was all.
Now it works.
I am totally confused.
Ranoop Nambiar
Advisor

Re: make_net_recovery problems

Hi velda ,

You can just confirm, the veriosn of ignite on both the ends by this,

/opt/ignite/lbin/check_version -v -s ${SERVER}

/opt/ignite/lbin/check_version -p ( for the clients's fileset)

Compare the versions and make sure the same on both ends..


Cheers,
Ranoop

Velda
Advisor

Re: make_net_recovery problems

Already did.
The Ignite versions are the same on client and server. Now.
But it should not have been an issue, since I have also tried to do a meke_net_recovery from server to server (so by default Ignite is the same), and got the same mistake as in client-server version of the events.