Autoyast 'xmlns' and 'xmlns:config' values
![](https://seccdn.libravatar.org/avatar/db238fed93e61eccada7e1a2330d80ef.jpg?s=120&d=mm&r=g)
Hi, I have been having problem with autoyast very early in the installation process without any error messages showing up and I was trying to check the XML file. While the XML file looks correct, the values for the 'xmlns' and 'xmlns:config' attributes of the <profile> tag don't seem right. If I try to go to http://www.suse.com/1.0/ or http://www.suse.com/1.0/yast2ns with my browser I get 'Error 404: Object Not Found' errors. Has the URL for those files changed? What should be the values for the two attributes? -- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com ========================================== Let the machine do the dirty work. -- "Elements of Programming Style", Kernighan and Ritchie
![](https://seccdn.libravatar.org/avatar/926abfa8eb8dab66c00070f582fc2b84.jpg?s=120&d=mm&r=g)
On Wed, Oct 05, 2005 at 03:50:37PM -0700, Mitko Haralanov wrote:
Hi, I have been having problem with autoyast very early in the installation process without any error messages showing up and I was trying to check the XML file.
While the XML file looks correct, the values for the 'xmlns' and 'xmlns:config' attributes of the <profile> tag don't seem right. If I try to go to http://www.suse.com/1.0/ or http://www.suse.com/1.0/yast2ns with my browser I get 'Error 404: Object Not Found' errors.
Has the URL for those files changed? What should be the values for the two attributes?
Nothing is wrong. The URIs of XML namespaces are arbitrary and need not reference a real document. (Though there have been attempts to standardize some useful content) -- Martin Vidner, YaST developer SuSE CR, s.r.o. e-mail: mvidner@suse.cz Drahobejlova 27 tel:+420-296542390 190 00 Praha 9, Czech Republic http://www.suse.cz
![](https://seccdn.libravatar.org/avatar/db238fed93e61eccada7e1a2330d80ef.jpg?s=120&d=mm&r=g)
On Thu, 6 Oct 2005 11:07:30 +0200 Martin Vidner <mvidner@suse.cz> wrote:
Nothing is wrong. The URIs of XML namespaces are arbitrary and need not reference a real document. (Though there have been attempts to standardize some useful content)
Thank you for your reply! However, now I am even more at a loss of why I would be having problems with my kickstart. The only thing I get is the error message "An error occurred during the installation" as soon as the ncurses interface comes up. The only thing I can think of is that the XML file is not valid but I have validated it and it is OK. The logs (y2log and y2start.log) do not show anything useful besides a message stating that the installer exited with code 137 but there is nothing else. Does anyone know what exit code 137 means? What else could cause this problem? Any help will be appreciated! -- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com ========================================== 85. It didn't do that a minute ago... --Top 100 things you don't want the sysadmin to say
![](https://seccdn.libravatar.org/avatar/926abfa8eb8dab66c00070f582fc2b84.jpg?s=120&d=mm&r=g)
On Thu, Oct 06, 2005 at 10:32:08AM -0700, Mitko Haralanov wrote:
The only thing I get is the error message "An error occurred during the installation" as soon as the ncurses interface comes up.
That means that yast has exited with an error.
The only thing I can think of is that the XML file is not valid but I have validated it and it is OK.
The logs (y2log and y2start.log) do not show anything useful besides a message stating that the installer exited with code 137 but there is nothing else. Does anyone know what exit code 137 means?
It is signal number + 128. So it got SIGKILL.
What else could cause this problem? Any help will be appreciated!
Try the kernel parameter Y2DEBUG=1 to get more verbose yast logs. -- Martin Vidner, YaST developer SuSE CR, s.r.o. e-mail: mvidner@suse.cz Drahobejlova 27 tel:+420-296542390 190 00 Praha 9, Czech Republic http://www.suse.cz
![](https://seccdn.libravatar.org/avatar/db238fed93e61eccada7e1a2330d80ef.jpg?s=120&d=mm&r=g)
On Fri, 7 Oct 2005 10:38:18 +0200 Martin Vidner <mvidner@suse.cz> wrote:
Try the kernel parameter Y2DEBUG=1 to get more verbose yast logs
OK, I did that but I really can't tell whether the logs have gotten more verbose. y2log show a lot of [ui-layout] problems but I doubt that is the problem. y2start.log does show that Y2DEBUG was set and that the debug file "YAST_DEBUG=/debug/yast.debug". However, I can't seem to find that file. It is not on the local filesystem and I even tried the boot server :) Where is that file supposed to be? Is that where the debugging info is recoreded? Thanx -- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com ========================================== 23. What happens to a Hard Disk when you drop it? --Top 100 things you don't want the sysadmin to say
![](https://seccdn.libravatar.org/avatar/926abfa8eb8dab66c00070f582fc2b84.jpg?s=120&d=mm&r=g)
On Fri, Oct 07, 2005 at 05:10:12PM -0700, Mitko Haralanov wrote:
On Fri, 7 Oct 2005 10:38:18 +0200 Martin Vidner <mvidner@suse.cz> wrote:
Try the kernel parameter Y2DEBUG=1 to get more verbose yast logs
OK, I did that but I really can't tell whether the logs have gotten more verbose. y2log show a lot of [ui-layout] problems but I doubt that is the problem.
y2start.log does show that Y2DEBUG was set and that the debug file "YAST_DEBUG=/debug/yast.debug". However, I can't seem to find that file. It is not on the local filesystem and I even tried the boot server :)
Where is that file supposed to be? Is that where the debugging info is recoreded?
/var/log/YaST2/y2log* should have debug level (<0>) messages. I don'f know about the other file, sorry. -- Martin Vidner, YaST developer SuSE CR, s.r.o. e-mail: mvidner@suse.cz Drahobejlova 27 tel:+420-296542390 190 00 Praha 9, Czech Republic http://www.suse.cz
participants (2)
-
Martin Vidner
-
Mitko Haralanov