Network Initialization Fails During Amahi Install
Network initialzation fails during install of Amahi at 42%, the following logs and info are listed below.
Output of hda-install log: http://fpaste.org/f6HH/
Output of --sysinfo: http://fpaste.org/bJFm/
Output of ifconfig: http://fpaste.org/2FQR/
Output of route -n: http://fpaste.org/aZ2a/
Output of ifcfg-eth0: http://fpaste.org/z7eo/
Correect ifcfg-eth0: http://fpaste.org/maPR/
#1 Updated by cpg about 10 years ago
the symptom is that hda_production is created, however, it has NO tables in it:
echo show tables | mysql -u root -phda hda_production
tables are not created prolly due to rails (and pluginfactory) not being installed properly or at all.
rails/pf may be missing due to a lack of network connectivity.
the core of this issue is lack of network connectivity to continue the install.
the erroneous ifcfg-eth0 is really a bug in hdactl, where hdactl SHOULD NEVER EVER generate something with garbage. even if it's called and started, and it might look like hda_production is there, it should CHECK that the DB returns something meaningful. granted that's rare, but it's always the case in this situation.
(BK, could you file a separate bug for this one?)
why is there network connectivity lost even before rails comes into play??
i'd suspect that NetworkManager.
it could be that the installer is doing something like tickling some setting somewhere that trips Network Manager and it goes bezerk. one possibility is that the installer unisntalls NetworkManager and it now (sometimes?????) turns off networking?
#3 Updated by eFfeM about 10 years ago
- Assignee changed from eFfeM to cpg
Well the pasties are expired or about to expire. Better put stuff in a log file and attach that to the bug report.
I've seen this behaviour in one situation:
if hdactl was installed under debian the hdactl daemon starts automatically. This happens before the actual hda-install is done.
In that case what happened was that hdactl tried to query the db and did not get the proper values and went on using the empty/uninitialized values it received.
This is similar to the analysis of cpg.Possible solutions:
- avoid that hdactl is started before the database is filled. That is what I did for debian in http://git.amahi.org/?p=amahi.git;a=commit;h=51ba3875a37ea738ccfc569ef8158ba8abd6c5a1
For debian I did it in the init script but it is probably better to do it in hdactl itself when it starts.
- within hdactl check for meaningful values (which is a good idea anyway)
- when starting hda-install make sure that the hdactl service is stopped.
Best solution is to implement all three of these as they are all three faulty situations (and some may happen in other places as well.
#4 Updated by bsk about 10 years ago
A current workaround to this would be to get network back, install rails 2.3.4 and pluginfactory then run hda-install CODE
/etc/sysconfig/networking/devices/ifcfg-eth0 with correct information.
service network restart
Install Rails 2.3.4
gem install --no-ri --no-rdoc rails -v 2.3.4
gem install --no-ri --no-rdoc pluginfactory
Then run the installer again
#6 Updated by cpg about 10 years ago
possible fix at
(32bits and 64 bits)
rpm -Uvh http://alpha ...
killall -9 hdactl
immediately before running the amahi installer (i.e. after entering the desktop for the first time but before installing amahi)
Also available in: Atom