PXE boot stuck just prior to download kernel

Help with booting MiniMyth

Moderator: Pablo

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Sat Dec 13, 2008 6:02 am

So why do my frontends fail to boot with "minimyth.conf not found" unless I include MM_INIT_TYPE=sh and how do I fix that?

(sorry, I know this has gone off original topic...)

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Sun Dec 14, 2008 7:24 am

mx-5 wrote:So why do my frontends fail to boot with "minimyth.conf not found" unless I include MM_INIT_TYPE=sh and how do I fix that?
I do not know why they fail to boot other than there must be a bug in the perl init scripts. Unfortunately, as I am not able to reproduce the problem, I cannot debug. On the chance that you have the time to help with the debugging, I am providing some debugging steps that might help isolate the problem.

If you boot the system with MM_INIT_TYPE=sh, then you can run perl init scripts manually in order to see whether or not they are failing to execute properly. A perl init script is run manually by telneting in to the MiniMyth frontend and running the command

Code: Select all

mm_service <init> start
The error message that you are seeing is generated by the 'conf' init script. The following is an ordered list of init scripts up to and including the 'conf' init script

Code: Select all

ld
loopback
dhcp
modules_automatic
conf
I would start by running

Code: Select all

mm_service conf start
However, before running it, you should run the command

Code: Select all

rm /etc/conf.d/minimyth
which will delete the processed minimyth.conf file which the 'conf' init script should create from the fetched minimyth.conf file.

If that does not produce any useful error messages, then I would try

Code: Select all

mm_service dhcp start
(sorry, I know this has gone off original topic...)
No problem.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Mon Feb 16, 2009 3:42 am

Pablo wrote:
mx-5 wrote:So why do my frontends fail to boot with "minimyth.conf not found" unless I include MM_INIT_TYPE=sh and how do I fix that?
I do not know why they fail to boot other than there must be a bug in the perl init scripts. Unfortunately, as I am not able to reproduce the problem, I cannot debug. On the chance that you have the time to help with the debugging, I am providing some debugging steps that might help isolate the problem.

If you boot the system with MM_INIT_TYPE=sh, then you can run perl init scripts manually in order to see whether or not they are failing to execute properly. A perl init script is run manually by telneting in to the MiniMyth frontend and running the command

Code: Select all

mm_service <init> start
The error message that you are seeing is generated by the 'conf' init script. The following is an ordered list of init scripts up to and including the 'conf' init script

Code: Select all

ld
loopback
dhcp
modules_automatic
conf
I would start by running

Code: Select all

mm_service conf start
However, before running it, you should run the command

Code: Select all

rm /etc/conf.d/minimyth
which will delete the processed minimyth.conf file which the 'conf' init script should create from the fetched minimyth.conf file.

If that does not produce any useful error messages, then I would try

Code: Select all

mm_service dhcp start
(sorry, I know this has gone off original topic...)
No problem.
Sorry for the lack of testing...

mm_service conf start gives me this:

tftp: server error: (1) File not found
tftp: server error: (1) File not found

mm_service dhcp start gives me this:

MiniMyth::var_save: MiniMyth configuration variables have not been loaded. at /usr/lib/perl5/site_perl/5.10.0/MiniMyth.pm line 252.

So this brought back memories of my initial attempts to get minimyth to work where I was also getting minimyth.conf not found messages due to dnsmasq / tftp. (http://www.minimyth.org/forum/viewtopic.php?t=1669)

So I checked my log for tftp and saw the following:

without MM_INIT_TYPE=sh:

Feb 15 18:26:17 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.0 to 192.168.188.116:2070
Feb 15 18:26:17 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.0 to 192.168.188.116:2071
Feb 15 18:26:17 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.cfg/ffffffff-ffff-ffff-ffff-ffffffffffff to 192.168.188.116:57089
Feb 15 18:26:17 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.cfg/01-00-02-a5-41-1d-a3 to 192.168.188.116:57090
Feb 15 18:26:17 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/minimyth-0.21.0-61/kernel to 192.168.188.116:57091
Feb 15 18:26:17 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/minimyth-0.21.0-61/rootfs to 192.168.188.116:57092
Feb 15 18:26:52 ubuntu1 atftpd[4648]: Serving usr/tftpboot/PXEClient/conf/cfi/minimyth.conf to 192.168.188.116:49816
Feb 15 18:26:52 ubuntu1 atftpd[4648]: Serving usr/tftpboot/PXEClient/conf/default/minimyth.conf to 192.168.188.116:35047

with MM_INIT_TYPE=sh:

Feb 15 18:28:46 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.0 to 192.168.188.116:2070
Feb 15 18:28:46 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.0 to 192.168.188.116:2071
Feb 15 18:28:46 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.cfg/ffffffff-ffff-ffff-ffff-ffffffffffff to 192.168.188.116:57089
Feb 15 18:28:46 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.cfg/01-00-02-a5-41-1d-a3 to 192.168.188.116:57090
Feb 15 18:28:46 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/minimyth-0.21.0-61/kernel to 192.168.188.116:57091
Feb 15 18:28:46 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/minimyth-0.21.0-61/rootfs to 192.168.188.116:57092
Feb 15 18:29:21 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/conf/cfi/minimyth.conf to 192.168.188.116:49455
Feb 15 18:29:35 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/conf-rw/cfi+codecs.sfs to 192.168.188.116:38579
Feb 15 18:29:36 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/minimyth-0.21.0-61/extras.sfs to 192.168.188.116:53036
Feb 15 18:29:36 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/conf/cfi/extras.sfs to 192.168.188.116:37105
Feb 15 18:29:36 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/conf/default/extras.sfs to 192.168.188.116:57117
Feb 15 18:29:44 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/minimyth-0.21.0-61/themes/G.A.N.T.sfs to 192.168.188.116:45095
Feb 15 18:29:49 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/minimyth-0.21.0-61/themes/Titivillus-OSD.sfs to 192.168.188.116:34644
Feb 15 18:29:49 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/conf-rw/cfi+themecache.sfs to 192.168.188.116:34989

For whatever reason, the entry for retrieving minimyth.conf starts off without "/" at the front of the path.

atftpd is running on my Ubuntu 8.04.1 server. atftpd is 0.7.dfsg-3

Any ideas how this can be resolved? Thanks!

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Mon Feb 16, 2009 5:00 pm

Could you try with version 64?

As version 64 does not support MM_INIT_TYPE='sh', be sure to save a copy of your current MiniMyth version.

Version 64 changes how TFTP gets/puts are done. MiniMyth uses cURL rather than wget for TFTP gets/puts. Looking at the older code that did TFTP gets using wget, it appears it had the same but as the bug fixed in the sh init script.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Tue Feb 17, 2009 3:01 am

Forgot to say that I had the minimyth.conf not found with version 64 - the fact that MM_INIT_TYPE=sh was no longer support led me to further diagnose this.

From the TFTP server, this time showing a different port used for minimyth.conf than version 61:

Feb 16 17:55:54 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.0 to 192.168.188.116:2070
Feb 16 17:55:54 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.0 to 192.168.188.116:2071
Feb 16 17:55:54 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.cfg/ffffffff-ffff-ffff-ffff-ffffffffffff to 192.16$
Feb 16 17:55:54 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/pxelinux.cfg/01-00-02-a5-41-1d-a3 to 192.168.188.116:57090
Feb 16 17:55:54 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/minimyth-0.21.0-64/kernel to 192.168.188.116:57091
Feb 16 17:55:55 ubuntu1 atftpd[4648]: Serving /usr/tftpboot/PXEClient/minimyth-0.21.0-64/rootfs to 192.168.188.116:57092
Feb 16 17:56:31 ubuntu1 atftpd[4648]: Serving usr/tftpboot/PXEClient/conf/cfi/minimyth.conf to 192.168.188.116:42067
Feb 16 17:56:31 ubuntu1 atftpd[4648]: Serving usr/tftpboot/PXEClient/conf/default/minimyth.conf to 192.168.188.116:50953

Here's what I got from the client:

root@cfi:/var/log # cat minimyth.log
Exiting eval via last at /etc/rc.d/rc.pl line 84.

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Tue Feb 17, 2009 3:16 am

I will look into this when I get a chance. However, if you are using 64, then bugs in atftpd are causing problems with the perl package WWW::Curl.

Have you filed a bug with the developers of atftpd?

What have they said?
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Post by mx-5 » Tue Feb 17, 2009 3:35 am

Thanks for the quick responses Pablo.

I guess I'm still determining what's causing this problem since this "minimyth.conf not found" error only started after version 59, and there had been a workaround by adding MM_INIT_TYPE=sh. So I haven't concluded that it's entirely atftpd.

atftpd is pretty popular though, no? I'm surprised I'm the only person experiencing this problem.

The other tidbit to add is that I'm using this with an OpenWRT router that's handling my DHCP using dnsmasq. I struggled with this when I first started using minimyth, but it's long resolved so I'm not sure if it's relevant at all: http://www.minimyth.org/forum/viewtopic.php?t=1669

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Post by Pablo » Sun Feb 22, 2009 4:18 pm

What is your dnsmasq configuration?
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

mx-5
Contributor
Posts: 52
Joined: Thu Jul 26, 2007 6:16 pm

Re: PXE boot stuck just prior to download kernel

Post by mx-5 » Tue May 19, 2009 7:12 am

Finally had time to look at this again, and I saw the followup to http://www.minimyth.org/forum/viewtopic.php?t=1669. Tried 0.21.0-67b6 and it's now resolved.
Thanks Pablo.

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Re: PXE boot stuck just prior to download kernel

Post by Pablo » Wed May 20, 2009 5:15 am

I am glad to hear that it is fixed for you as well.
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

Post Reply