Re: [suse-autoinstall] Tracking an error during installation
On 4 Aug, Mitko Haralanov wrote:
lockd: failed to open /var/lib/nfs/state: err=-2
Anyone have an idea why this would be showing up and whether it is the problem?
Assuming you're doing an nfs mount yourself in a script? If so, add the options -o ro,nolock after mount and it'll fix it. If it's autoyast.. not sure what to say as it should know better. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com "There are no significant bugs in our released software that any significant number of users want fixed." - Bill Gates in an interview with Focus magazine, Oct 23, 1995.
On Thu, 4 Aug 2005 15:46:59 -0700 (PDT) Michael Marion <mmarion@qualcomm.com> wrote:
Assuming you're doing an nfs mount yourself in a script? If so, add the options -o ro,nolock after mount and it'll fix it.
Unfortunately, this is not exactly the case! The autoyast/kickstart process is done over nfs but I am not doing a manual nfs mount. The error message comes up as soon as the autoyast/kickstart process switches to the (pseudo-) graphical mode (presumably, when it tried to get the kickstart xml file from the server) -- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com ========================================== TRANSACTION CANCELLED - FARECARD RETURNED
Still no ideas? Because of this problem, I am pretty much stalled and I really need to get it going. Any help will be appreciated!! Thanx On Thu, 4 Aug 2005 16:02:32 -0700 Mitko Haralanov <mitko@pathscale.com> wrote:
On Thu, 4 Aug 2005 15:46:59 -0700 (PDT) Michael Marion <mmarion@qualcomm.com> wrote:
Assuming you're doing an nfs mount yourself in a script? If so, add the options -o ro,nolock after mount and it'll fix it.
Unfortunately, this is not exactly the case! The autoyast/kickstart process is done over nfs but I am not doing a manual nfs mount. The error message comes up as soon as the autoyast/kickstart process switches to the (pseudo-) graphical mode (presumably, when it tried to get the kickstart xml file from the server)
-- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com
========================================== TRANSACTION CANCELLED - FARECARD RETURNED
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com ========================================== UNIX was half a billion (500000000) seconds old on Tue Nov 5 00:53:20 1985 GMT (measuring since the time(2) epoch). -- Andy Tannenbaum
On Friday 05 August 2005 18:37, Mitko Haralanov wrote:
Still no ideas? Because of this problem, I am pretty much stalled and I really need to get it going. Any help will be appreciated!!
Which version of SUSE Linux do you use? at the moment I have no idea. Is there anything in the /var/log/YaST2/y2log ? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
On Mon, 8 Aug 2005 09:57:27 +0200 Uwe Gansert <ug@suse.de> wrote:
Which version of SUSE Linux do you use? at the moment I have no idea. Is there anything in the /var/log/YaST2/y2log ?
I am installing SuSE 9.3 and as far as I can tell there is nothing out of the ordinary in /var/log/YaST2/y2log. -- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com ========================================== "I'll bet you $5 USD (and these days, that's about a gadzillion Euros) that this explains it." - Linus
participants (3)
-
Michael Marion -
Mitko Haralanov -
Uwe Gansert