ram minimyth not parsing minimyth.conf file

Help with booting MiniMyth

Moderator: Pablo

Post Reply
waaminimyth
New Member
Posts: 3
Joined: Sat Nov 14, 2009 8:46 pm
Location: North Western Connecticut, USA

ram minimyth not parsing minimyth.conf file

Post by waaminimyth » Sun Nov 15, 2009 1:35 am

Since upgrading to ram-minimyth-0.22.0-72 yesterday, clients stop during boot with the following onscreen messages: (also in /var/log/messages on client)

--[snip]--
Nov 14 15:24:30 (none) local0.info minimyth: processing configuration file ...
Nov 14 15:24:31 (none) local0.err minimyth: 'MM_X_OUTPUT_HDMI', 'MM_X_OUTPUT_DVI', 'MM_X_OUTPUT_VGA' and 'MM_X_OUTPUT_TV' are all disabled.
Nov 14 15:24:31 (none) local0.err minimyth: MM_THEME_NAME='' is not valid.
Nov 14 15:24:32 (none) local0.err minimyth: 'TCode' (or 'MM_DHCP_TCODE') not configured.
Nov 14 15:24:32 (none) local0.err minimyth: MM_THEMEOSD_NAME='' is not valid.
Nov 14 15:24:32 (none) local0.info minimyth: init failed. check '/var/log/messages' for further details.
--[snip]--

my tftp server log clearly shows that the correct files being served to the client:

--[snip]--
Nov 14 14:16:56 newby atftpd[5378]: Serving PXEClient/ram-minimyth-0.22.0-72/kernel to 192.168.254.39:57100
Nov 14 14:16:56 newby atftpd[5378]: Serving PXEClient/ram-minimyth-0.22.0-72/rootfs to 192.168.254.39:57101
Nov 14 14:17:42 newby atftpd[5378]: Serving PXEClient/conf/myth1/minimyth.conf to 192.168.254.39:59904
--[snip]--

AND when I telnet into the client I can see that the "PXEClient/conf/myth1/minimyth.conf" file it tftp'd from my tftp server now resides in /etc/minimyth.d/minimyth.conf on the client machine's root filesystem

So, these options ARE set in the minimyth.conf file, I know the client is getting the config file, and I know it is the correct file. It seems that it is just not parsing it correctly (or at all it seems)

Can someone help with this? Thanks!

--
Bill Arlofski

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

Re: ram minimyth not parsing minimyth.conf file

Post by Pablo » Sun Nov 15, 2009 4:06 am

Could you post your minimyth.conf file?
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

gtr33m
Contributor
Posts: 67
Joined: Mon Jan 21, 2008 9:23 am
Location: Sydney, Australia

Re: ram minimyth not parsing minimyth.conf file

Post by gtr33m » Sun Nov 15, 2009 6:54 am

I had exactly the same problems when I started with a blank minimyth.conf file.

I was not able to get it running, but I was able to eliminate each of the error messages.

First, you need to specify at least one of the 'MM_X_OUTPUT_HDMI', 'MM_X_OUTPUT_DVI', 'MM_X_OUTPUT_VGA' and 'MM_X_OUTPUT_TV' and set it to ='yes'

The TCODE also needs to be set and should match your server. Check you server by using 'date'. You'll get a response like "Sun Nov 15 16:50:56 EST 2009" where "EST" is the timezone of your server. Use this value as you TCODE value.

The other two relating to the THEME are the name of the theme file is the themes folder on your tftp server. I could not get this to work through tftp and ended up having to put them on the web server and specify the THEME URL as well. The relevant section is below:

Code: Select all

MM_THEME_NAME='MythCenter-wide'
MM_THEMEOSD_NAME='Gray-OSD'
MM_THEME_URL='http://192.168.4.2/minimyth/themes/MythCenter-wide.sfs'
MM_THEMEOSD_URL='http://192.168.4.2/minimyth/themes/Gray-OSD.sfs'
MM_THEMECACHE_URL='http://192.168.4.2/minimyth/confrw/'
Please note that I still had problems getting minimyth to boot after this, but it did take care of the errors.
GA-PCV2 mini-itx
512 MB RAM
DVico Ultraview Remote

waaminimyth
New Member
Posts: 3
Joined: Sat Nov 14, 2009 8:46 pm
Location: North Western Connecticut, USA

[SOLVED] ram minimyth not parsing minimyth.conf file

Post by waaminimyth » Mon Nov 16, 2009 3:47 pm

Pablo, gtr33m... I am sorry that this slipped past me... I had solved my issue only moments after I made my initial post. I had even created a follow-up post (I was 1st and 2nd in this thread) and I MUST have not clicked the submit button after I previewed my post!

Thank you both for your comments, but in the end I saw this in the /var/log minimyth file which practically told me exactly what was wrong:

--[snip]--
# cat /var/log/minimyth.log
/bin/sh: /etc/minimyth.d/minimyth.conf: line 45: syntax error: unterminated quoted string
/bin/sh: /etc/minimyth.d/minimyth.conf: line 45: syntax error: unterminated quoted string
Use of uninitialized value $value in pattern match (m//) at /etc/rc.d/init/conf/MM_X.pm line 330.
Use of uninitialized value $value in pattern match (m//) at /etc/rc.d/init/conf/MM_X.pm line 335.
Use of uninitialized value $value in concatenation (.) or string at /etc/rc.d/init/conf/MM_X.pm line 342.
Use of uninitialized value in string eq at /etc/rc.d/init/conf/MM_EXTRAS.pm line 26.
Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.10.1/MiniMyth.pm line 249.
Exiting eval via last at /etc/rc.d/rc.pl line 81.
--[snip]--


So basically, I had misquoted one of the variables in my minimyth file! I had accidentally quoted a variable with a double-quote and closed it with a single quote.

--
Bill Arlofski

Post Reply