Thread: [OSR-devel] How to save the bug report within anaconda

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hello,

is there a sophisticated way to save a bug report within anaconda. The 
setup crashes right after the selection of the keyboard layout.

Thanks in advance

Thomas Kisler

On Wednesday 05 November 2008 11:21:31 Thomas Kisler wrote:
> Hello,
>
> is there a sophisticated way to save a bug report within anaconda. The
> setup crashes right after the selection of the keyboard layout.
>
> Thanks in advance
>
> Thomas Kisler
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge Build the coolest Linux based applications with Moblin SDK & win
> great prizes Grand prize is a trip for two to an Open Source event anywhere
> in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Open-sharedroot-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-devel

Depends on what you mean with crash (does the system freeze or do you fail 
back to a shell or does it reboot). You should be able to upload a "dump" 
within anaconda and be able to scp it to another host. You have to enable the 
debug mode (just start it with "linux debug" or if it is not possible you can 
at least syslog all messages to another syslog host. I think this works with 
starting with  "linux syslog=<ip>") then you should get a button from where 
you should be able to scp the data to another host.
Let me know if that works or if it at least helps?

Regards Marc.

-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

Hello,

during the Anaconda setup you also may switch to another console:

    *  Alt-F1 - installation dialog
    * Alt-F2 - shell prompt
    * Alt-F3 - install log (messages from install program)
    * Alt-F4 - system log (messages from kernel, etc.)
    * Alt-F5 - other messages

Maybe there are error messages displayed that will help debugging the issue.

Also there are anaconda kernel boot parameters that will help the debugging 
process:

    * debug - Add a debug button to the UI that allows dropping into a python 
debugger. 
    * nokill - A debugging option that prevents anaconda from terminating all 
running programs when a fatal error occurs

Usually Anaconda stores a log in /var/log/anaconda.log. From a shell you may 
access the file.

May I ask what hardware configuration do you use?

Best regards,
Reiner Rottmann

-- 
Gruss / Regards,
Dipl.-Ing. (FH) Reiner Rottmann

ATIX Informationstechnologie und Consulting AG
Einsteinstr. 10 
85716 Unterschleissheim
Deutschland/Germany

Phone: +49-89 452 3538-12     Fax: +49-89 990 1766-0
Email: rot...@at...       PGP Key-ID: 0xCA67C5A6
       www.atix.de  |  www.open-sharedroot.org

Vorstaende: Marc Grimme, Mark Hlawatschek, Thomas Merz (Vors.)
Vorsitzender des Aufsichtsrats: Dr. Martin Buss
Registergericht: Amtsgericht Muenchen
Registernummer: HRB 168930
USt.-Id.: DE209485962

On Wednesday 05 November 2008 11:21:31 am Thomas Kisler wrote:
> Hello,
>
> is there a sophisticated way to save a bug report within anaconda. The
> setup crashes right after the selection of the keyboard layout.
>
> Thanks in advance
>
> Thomas Kisler
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge Build the coolest Linux based applications with Moblin SDK & win
> great prizes Grand prize is a trip for two to an Open Source event anywhere
> in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Open-sharedroot-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-devel

Hello,

thank you for your messages. The syslog option would have been nice, but 
it seems that not recognizing the network interface is the bug. 
Therefore i was not able to copy the exception details to another host.

The missing piece was the hint with the anaconda.log. Although it does 
not reside in /var/log, knowing the name helped me finding it in /tmp. 
There is the anaconda.log and the (maybe) more interesting anacdump.txt 
which contains the exception details. I append both files and some 
information on the hardware. Tell me, if I can help you with some more 
information.

-------------------------------------------------------------------------------------------
Motherboard: K9A2CF from MSI
-------------------------------------------------------------------------------------------

lspci gives the following information:

00:00.0 Host bridge: ATI Technologies Inc RD780 Northbridge only dual 
slot PCI-e_GFX and HT1 K8 part
00:02.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge 
(external gfx0 port A)
00:06.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI 
express gpp port C)
00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA
00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0)
00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1)
00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2)
00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3)
00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4)
00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI)
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14)
00:14.1 IDE interface: ATI Technologies Inc SB600 IDE
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, 
Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, 
Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, 
Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, 
Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, 
Athlon64, Sempron] Link Control
01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7300 
GT] (rev a1)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)

-------------------------------------------------------------------------------------------
cpuinfo of one core:

processor      : 0
vendor_id      : AuthenticAMD
cpu family      : 16
model            : 2
model name   : AMD Phenom(tm) 9500 Quad-Core Processor
stepping         : 2
cpu MHz       : 2200.153
cache size      : 512 KB
physical id      : 0
siblings           : 4
core id           : 3
cpu cores       : 4
apicid            : 3
initial apicid    : 3
fpu                : yes
fpu_exception   : yes
cpuid level      : 5
wp                 : yes
flags               : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr 
pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext 
fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl pni 
monitor
 cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs
bogomips       : 4400.43
TLB size        : 1024 4K pages
clflush size      : 64
cache_alignment : 64
address sizes  : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

-------------------------------------------------------------------------------------------

Should I also create a new report at the sourceforge bug tracker?

Best regards

Thomas Kisler
------------------------
Reiner Rottmann wrote:
> Hello,
>
> during the Anaconda setup you also may switch to another console:
>
>     *  Alt-F1 - installation dialog
>     * Alt-F2 - shell prompt
>     * Alt-F3 - install log (messages from install program)
>     * Alt-F4 - system log (messages from kernel, etc.)
>     * Alt-F5 - other messages
>
> Maybe there are error messages displayed that will help debugging the issue.
>
> Also there are anaconda kernel boot parameters that will help the debugging 
> process:
>
>     * debug - Add a debug button to the UI that allows dropping into a python 
> debugger. 
>     * nokill - A debugging option that prevents anaconda from terminating all 
> running programs when a fatal error occurs
>
> Usually Anaconda stores a log in /var/log/anaconda.log. From a shell you may 
> access the file.
>
> May I ask what hardware configuration do you use?
>
> Best regards,
> Reiner Rottmann
>
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Open-sharedroot-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-devel
>   

Thomas,
ok looks like two things I'd say.
The first is a bug: 
11:25:32 CRITICAL: Traceback (most recent call first):
  File "/usr/lib/anaconda/iw/osr_gui.py", line 51, in getScreen
    node.addNetdev(OSRClusterNodeNetdev(node, net.available().keys()[0]))
We expect anaconda to find a valid nic. Looks like anaconda did not detect 
your realtec nics.
Would be nice if you could file a bug.
We'll include it into the next release.

The second is that anaconda does not find the nics in your server.

The means even if we fix that bug you wont have a valid cluster without nics.

A valid solution would be to change the nic:
Do you have another nic (intel, broadcom, ..) that you can plug into this 
server?

Regards Marc.

On Thursday 06 November 2008 12:00:27 Thomas Kisler wrote:
> Hello,
>
> thank you for your messages. The syslog option would have been nice, but
> it seems that not recognizing the network interface is the bug.
> Therefore i was not able to copy the exception details to another host.
>
> The missing piece was the hint with the anaconda.log. Although it does
> not reside in /var/log, knowing the name helped me finding it in /tmp.
> There is the anaconda.log and the (maybe) more interesting anacdump.txt
> which contains the exception details. I append both files and some
> information on the hardware. Tell me, if I can help you with some more
> information.
>
> ---------------------------------------------------------------------------
>---------------- Motherboard: K9A2CF from MSI
> ---------------------------------------------------------------------------
>----------------
>
> lspci gives the following information:
>
> 00:00.0 Host bridge: ATI Technologies Inc RD780 Northbridge only dual
> slot PCI-e_GFX and HT1 K8 part
> 00:02.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge
> (external gfx0 port A)
> 00:06.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI
> express gpp port C)
> 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA
> 00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0)
> 00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1)
> 00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2)
> 00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3)
> 00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4)
> 00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI)
> 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14)
> 00:14.1 IDE interface: ATI Technologies Inc SB600 IDE
> 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
> 00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
> 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
> 00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
> Athlon64, Sempron] HyperTransport Configuration
> 00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
> Athlon64, Sempron] Address Map
> 00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
> Athlon64, Sempron] DRAM Controller
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
> Athlon64, Sempron] Miscellaneous Control
> 00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
> Athlon64, Sempron] Link Control
> 01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7300
> GT] (rev a1)
> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
>
> ---------------------------------------------------------------------------
>---------------- cpuinfo of one core:
>
> processor      : 0
> vendor_id      : AuthenticAMD
> cpu family      : 16
> model            : 2
> model name   : AMD Phenom(tm) 9500 Quad-Core Processor
> stepping         : 2
> cpu MHz       : 2200.153
> cache size      : 512 KB
> physical id      : 0
> siblings           : 4
> core id           : 3
> cpu cores       : 4
> apicid            : 3
> initial apicid    : 3
> fpu                : yes
> fpu_exception   : yes
> cpuid level      : 5
> wp                 : yes
> flags               : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
> pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
> fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl pni
> monitor
>  cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a
> misalignsse 3dnowprefetch osvw ibs
> bogomips       : 4400.43
> TLB size        : 1024 4K pages
> clflush size      : 64
> cache_alignment : 64
> address sizes  : 48 bits physical, 48 bits virtual
> power management: ts ttp tm stc 100mhzsteps hwpstate
>
> ---------------------------------------------------------------------------
>----------------
>
> Should I also create a new report at the sourceforge bug tracker?
>
> Best regards
>
> Thomas Kisler
> ------------------------
>
> Reiner Rottmann wrote:
> > Hello,
> >
> > during the Anaconda setup you also may switch to another console:
> >
> >     *  Alt-F1 - installation dialog
> >     * Alt-F2 - shell prompt
> >     * Alt-F3 - install log (messages from install program)
> >     * Alt-F4 - system log (messages from kernel, etc.)
> >     * Alt-F5 - other messages
> >
> > Maybe there are error messages displayed that will help debugging the
> > issue.
> >
> > Also there are anaconda kernel boot parameters that will help the
> > debugging process:
> >
> >     * debug - Add a debug button to the UI that allows dropping into a
> > python debugger.
> >     * nokill - A debugging option that prevents anaconda from terminating
> > all running programs when a fatal error occurs
> >
> > Usually Anaconda stores a log in /var/log/anaconda.log. From a shell you
> > may access the file.
> >
> > May I ask what hardware configuration do you use?
> >
> > Best regards,
> > Reiner Rottmann
> >
> >
> > ------------------------------------------------------------------------
> >
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> > challenge Build the coolest Linux based applications with Moblin SDK &
> > win great prizes Grand prize is a trip for two to an Open Source event
> > anywhere in the world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Open-sharedroot-devel mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/open-sharedroot-devel

-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

Thomas,
I moved the bug you've opened to the right place: 
https://bugzilla.open-sharedroot.org/show_bug.cgi?id=298
Please add yourself as CC to it.

But anyway I think if you really like to get any further you should follow the 
alternative way which is described here:
* 
http://www.open-sharedroot.org/documentation/rhel5-gfs-shared-root-mini-howto
* http://www.open-sharedroot.org/documentation/the-opensharedroot-mini-howto

Thanks and Regards
Marc.
-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/