RE: [suse-autoinstall] Tracking an error during installation
This kind of generic error usually happens if the xml file is incorrect. Ether post your file or check /var/log/YaST2/y2log* of the installation system (ALT-F2 has a shell) for errors. Mit freundlichen Grüßen / kind regards SoftService GmbH Holger Meyers Consulting Tel 0211 977 09 69 Fax 0211 977 09 27 http://www.softservice.de
-----Original Message----- From: Mitko Haralanov [mailto:mitko@pathscale.com] Sent: Friday, August 05, 2005 6:38 PM To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Tracking an error during installation
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
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
On Mon, 8 Aug 2005 11:23:03 +0200 "Meyers, Holger" <Holger.Meyers@softservice.de> wrote:
This kind of generic error usually happens if the xml file is incorrect. Ether post your file or check /var/log/YaST2/y2log* of the installation system (ALT-F2 has a shell) for errors.
I looked at the log file and I did not see anything that stood out. Just in case, I am attaching my xml file (slightly edited for privacy). I also tried attaching the y2log file but the mailing list rejected it since it was too big... -- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com ========================================== The disks are getting full; purge a file today.
On Mon, 8 Aug 2005 14:05:08 -0700 Mitko Haralanov <mitko@pathscale.com> wrote:
I looked at the log file and I did not see anything that stood out. Just in case, I am attaching my xml file (slightly edited for privacy).
I also tried attaching the y2log file but the mailing list rejected it since it was too big...
I one more thing that could be the problem: on the ALT-F3 screen/console, there are the following messages: starting setctsid "showconsole" inst_setup yast error setting kbd mode: Invalid argument install program exit code is 137 Could this be the problem that needs to be solve? And if yes, how can I change the kbd mode? Changing the values for the <keyboard> parameter does not seem to help... -- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com ========================================== 98. What the hell!? --Top 100 things you don't want the sysadmin to say
participants (2)
-
Meyers, Holger -
Mitko Haralanov