SOLVED: Amahi7 installation problems

[zion2008]

I downloaded the amahi7 ISO and burned it toa disc. Rebooted my machine with the disk in it. went through the configuration steps. After a while it is finished and wants to reboot. I hit the button so the reboot of my machine is activated. During the POST phase I remove my DVD and the headless fedora19 starts up. I get to the logon screen. Then according to the instructions I have to let it finish its configuration and it will reboot again. However that second reboot NEVER appears. It is now almost 6 hours later and still no reboot. I also still have the initially assigned Ip adres via DHCP of my router and not the static IP adres which I configured at my Amahi control panel (default 192.168.0.10).

Annyone any idea's on this mystery?

Regards zion2008

[bigfoot65]

Check and make sure you got a good image file. I have installed many times with no issues. It could be almost anything, but making sure the image is good would be the first step.

[zion2008]

OK. I did a reboot with my image disk in it and chose "Test this media & install ..." It finished after a while with the message media check PASS

The original downloaded ISO I did also the MD5 integrity check on and the checksum I got was identival to the one in the wiki
https://wiki.amahi.org/index.php/Expres ... rification

I burned he disk with Nero and ended with a verification of the burning process. That ended all OK.

Any further suggestions?

Regards zion2008

[bigfoot65]

That's about all you can do. Might be worth trying the install again. It should not take more than 10-15 minutes max after the initial reboot to be ready for log in.

There are many things that could be causing issues, internet connection is probably the most likely. Maybe a second try will go better.

[zion2008]

I already tried a fres new install 2 times but eery time I get the same result. It never doe the second reboot after amahi configuration is executed completely (which ought to happen according to the wiki/install guide).

Are there any logfile on the fedora19 that might be worth investigating?

Or else is there still a way to do an Amahi6 install? (As you can see I'm quite eager to give the Amahi HDA a try).

zion2008

[bigfoot65]

You can check /tmp and /var/log directories for log files.

As for Amahi 6, you can install Ubuntu 12.04.2. Jusst have to keep in mind we will not longer be adding apps or features. Amahi 7 Express is the official version now.

I am running Ubuntu myself and works great.

[zion2008]

Okay so I gave it another try. Just to be sure it did not relate to the PC I took a different one.
But again after the succesfull install and the reboot the second reboot never appeared.

I looked at all the available log files and I found these messages.

Log file /root/hda-install-130811-202821.log
Retrieving install code …
/usr/bin/hda-install:543:in `block in check_install_code' : undefined local variable or method `last' for main:Object (NameError)
from /usr/bin/hda-install:536:in `each'
from /usr/bin/hda-install:536:in `check_install_code'
from /usr/bin/hda-install:1249:in `main'
from /usr/bin/hda-install:1274:in `<main>'

in the file /var/log/messages I see
amahi-installer[390]: WARNING: express installer failed to start
Networkmanager[323]: <warn> Dispatcher script timed out: Script …

However I am clueless if these are indeed the ones that need to be solved and more importantly HOW to resolve those.
Any help is welcoome.
Regards zion2008.

[bigfoot65]

Did you enter the correct install code? It almost looks like is was bad. Also ensure your amahi.org profile matches your network settings.

[zion2008]

yes the entered install code was the correct one.

regarding the other remark. The only difference I see is that in my amahi.org profile I entered

Home Domain ldqk.local
which might differ from the real home domain as used right now.

What would be the impact of that?

Should I look in my modem/router and see what domain is used there?
Regards zion2008

[bigfoot65]

Any of those could be a factor. This is an issue we have not seen by other users as of yet. It seems there are some networking issues on your end that might be the cause.