Based on the latest alpha 2 release I attempted to install A7 again:
- I made sure the all mysql packages were removed, all hda install packages were removed, all mariadb packaged were removed.
- I did a yum clean all, installed mariadb packages, installed hda install packages, did an hda install.
- After the reboot I tried connecting to the hda and no browser connection. I could ping and ssh in to the server.
- I looked at the hda-install log and noticed some errors, not sure how relevant some of them were. however I noticed just after "Initializing MySQL" the following:
mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost' (using password: NO)'
Could this be the problem? I have attached the hda-install log.
Amahi 7 alpha 2 release
-
- Posts: 134
- Joined: Sun Mar 07, 2010 9:54 am
Re: Amahi 7 alpha 2 release - hda-install log errors
- Attachments
-
- hda-install-130331-081255.log
- (9.9 KiB) Downloaded 564 times
Re: Amahi 7 alpha 2 release
@northridgegrp The log indicates all is normal during install. The error you cite is normal on the first install (because the installer tries to re-initialize the DB, but it does not exist the first time).
So, upon reboot, it would be good to look at whether httpd is running. If it's not, it's bad news and the logs for httpd is needed to debug further. If it's running, looking at this code will help
So, upon reboot, it would be good to look at whether httpd is running. If it's not, it's bad news and the logs for httpd is needed to debug further. If it's running, looking at this code will help
Code: Select all
/var/hda/platform/html/log/production.log
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
Re: Amahi 7 alpha 2 release
Is the basic amahi functionality working properly (shares + greyhole) with the x86 or x64 install ?
I only need shares and greyhole to be working, the rest can come later. If it's working I'll upgrade my fedora 16 (with a fresh install as this was already an upgrade of fedora 14).
Thanks for the updates!
I only need shares and greyhole to be working, the rest can come later. If it's working I'll upgrade my fedora 16 (with a fresh install as this was already an upgrade of fedora 14).
Thanks for the updates!
Re: Amahi 7 alpha 2 release
@bigmango shares work. greyhole is not implemented yet.
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
-
- Posts: 134
- Joined: Sun Mar 07, 2010 9:54 am
Re: Amahi 7 alpha 2 release
I did a complete new install of my bench machine:@northridgegrp The log indicates all is normal during install. The error you cite is normal on the first install (because the installer tries to re-initialize the DB, but it does not exist the first time).
So, upon reboot, it would be good to look at whether httpd is running. If it's not, it's bad news and the logs for httpd is needed to debug further. If it's running, looking at this code will helpCode: Select all
/var/hda/platform/html/log/production.log
- The install errors are gone.
- The httpd server is still not running. Here is some information if that will help:
/var/hda/platform/html/log/production.log 723/723 100%
Connecting to database specified by database.yml
Migrating to CreateUsers (20120803010000)
Migrating to CreateSettings (20120803010100)
Migrating to CreateAppDependencies (20120803010200)
Migrating to CreateApps (20120803010300)
Migrating to CreateCapAccesses (20120803010400)
Migrating to CreateCapWriters (20120803010500)
Migrating to CreateDbs (20120803010600)
Migrating to CreateFirewalls (20120803010800)
Migrating to CreateHosts (20120803010900)
Migrating to CreateServers (20120803011000)
Migrating to CreateShares (20120803011200)
Migrating to CreateThemes (20120803011300)
Migrating to CreateDnsAliases (20120803011400)
Migrating to CreateWebappAliases (20120803011500)
Migrating to CreateWebapps (20120803011600)
Checking status of http
=======================
systemctl status httpd.service
httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
Active: failed (Result: exit-code) since Sun, 2013-03-31 15:58:26 MDT; 5min ago
Process: 1308 ExecStop=/usr/sbin/httpd $OPTIONS -k graceful-stop (code=exited, status=0/SUCCESS)
Process: 1306 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/httpd.service
Mar 31 15:58:26 northridgesv03 systemd[1]: Starting The Apache HTTP Server...
Mar 31 15:58:26 northridgesv03 httpd[1306]: AH00557: httpd: apr_sockaddr_info_get() failed for northridgesv03
Mar 31 15:58:26 northridgesv03 httpd[1306]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name,...message
Mar 31 15:58:26 northridgesv03 systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Mar 31 15:58:26 northridgesv03 httpd[1308]: AH00557: httpd: apr_sockaddr_info_get() failed for northridgesv03
Mar 31 15:58:26 northridgesv03 httpd[1308]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name,...message
Mar 31 15:58:26 northridgesv03 httpd[1308]: httpd (no pid file) not running
Mar 31 15:58:26 northridgesv03 systemd[1]: Failed to start The Apache HTTP Server.
Mar 31 15:58:26 northridgesv03 systemd[1]: Unit httpd.service entered failed state
-
- Posts: 134
- Joined: Sun Mar 07, 2010 9:54 am
Re: Amahi 7 alpha 2 release
Ok! I just got Apache to start on my minimal F18 bench machine! I consulted the great oracle Dr. Google and had to do the two following things (I don't know why):I did a complete new install of my bench machine:@northridgegrp The log indicates all is normal during install. The error you cite is normal on the first install (because the installer tries to re-initialize the DB, but it does not exist the first time).
So, upon reboot, it would be good to look at whether httpd is running. If it's not, it's bad news and the logs for httpd is needed to debug further. If it's running, looking at this code will helpCode: Select all
/var/hda/platform/html/log/production.log
- The install errors are gone.
- The httpd server is still not running. Here is some information if that will help:
/var/hda/platform/html/log/production.log 723/723 100%
Connecting to database specified by database.yml
Migrating to CreateUsers (20120803010000)
Migrating to CreateSettings (20120803010100)
Migrating to CreateAppDependencies (20120803010200)
Migrating to CreateApps (20120803010300)
Migrating to CreateCapAccesses (20120803010400)
Migrating to CreateCapWriters (20120803010500)
Migrating to CreateDbs (20120803010600)
Migrating to CreateFirewalls (20120803010800)
Migrating to CreateHosts (20120803010900)
Migrating to CreateServers (20120803011000)
Migrating to CreateShares (20120803011200)
Migrating to CreateThemes (20120803011300)
Migrating to CreateDnsAliases (20120803011400)
Migrating to CreateWebappAliases (20120803011500)
Migrating to CreateWebapps (20120803011600)
Checking status of http
=======================
systemctl status httpd.service
httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
Active: failed (Result: exit-code) since Sun, 2013-03-31 15:58:26 MDT; 5min ago
Process: 1308 ExecStop=/usr/sbin/httpd $OPTIONS -k graceful-stop (code=exited, status=0/SUCCESS)
Process: 1306 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/httpd.service
Mar 31 15:58:26 northridgesv03 systemd[1]: Starting The Apache HTTP Server...
Mar 31 15:58:26 northridgesv03 httpd[1306]: AH00557: httpd: apr_sockaddr_info_get() failed for northridgesv03
Mar 31 15:58:26 northridgesv03 httpd[1306]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name,...message
Mar 31 15:58:26 northridgesv03 systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Mar 31 15:58:26 northridgesv03 httpd[1308]: AH00557: httpd: apr_sockaddr_info_get() failed for northridgesv03
Mar 31 15:58:26 northridgesv03 httpd[1308]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name,...message
Mar 31 15:58:26 northridgesv03 httpd[1308]: httpd (no pid file) not running
Mar 31 15:58:26 northridgesv03 systemd[1]: Failed to start The Apache HTTP Server.
Mar 31 15:58:26 northridgesv03 systemd[1]: Unit httpd.service entered failed state
1. /etc/httpd/conf/httpd.conf:
I had to add "ServerName northridgesv03".
2. /etc/hosts on the 127.0... line:
I had to add northridgesv03.
Now the question I have I entered the host name during the F18 install. Should I have set the host name to "localhost"? The F18 install did not have "localhost" as a default.
Re: Amahi 7 alpha 2 release
Did you follow the Fedora 18 wiki guidance for install?
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
- Posts: 134
- Joined: Sun Mar 07, 2010 9:54 am
Re: Amahi 7 alpha 2 release
Yes I followed the guidance but I don't remember seeing anything referring to any details such as the hostname. However I have done A6/F14 installs several times installing via the graphical with a GNOME desktop and entered the host and that never seemed to be a problem.Did you follow the Fedora 18 wiki guidance for install?
Re: Amahi 7 alpha 2 release
Yea, I don't recall it asking for a host name when I installed.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Re: Amahi 7 alpha 2 release
Did a fresh install on my Pi. It failed at the same place as yesterday. The only deviation from the suggested install method was to install SSH and perform the whole process through Putty. I have the putty log but it won't attach to the forum post.
Verbose log file at '/root/hda-install-130331-232827.log'.
Retrieving install code ...
Install code looks good
Stopping background software updates ...
Background software updates stopped
Installing 4 packages ...
RPM packages installed
Starting MySQL
Initializing MySQL
*************** TBD: Initialize storage pooling ... *******************
Initializing Ruby on Rails and DB
Activating your HDA's settings
ERROR 1146 (42S02) at line 1: Table 'hda_production.settings' doesn't exist
Initializing settings
/usr/bin/hda-install:212:in `query': Table 'hda_production.settings' doesn't exist (Mysql::Error)
from /usr/bin/hda-install:212:in `get_db_settings'
from /usr/bin/hda-install:832:in `do_full_install'
from /usr/bin/hda-install:1264:in `main'
from /usr/bin/hda-install:1267:in `<main>'
http://paste.fedoraproject.org/6401/36478817
Verbose log file at '/root/hda-install-130331-232827.log'.
Retrieving install code ...
Install code looks good
Stopping background software updates ...
Background software updates stopped
Installing 4 packages ...
RPM packages installed
Starting MySQL
Initializing MySQL
*************** TBD: Initialize storage pooling ... *******************
Initializing Ruby on Rails and DB
Activating your HDA's settings
ERROR 1146 (42S02) at line 1: Table 'hda_production.settings' doesn't exist
Initializing settings
/usr/bin/hda-install:212:in `query': Table 'hda_production.settings' doesn't exist (Mysql::Error)
from /usr/bin/hda-install:212:in `get_db_settings'
from /usr/bin/hda-install:832:in `do_full_install'
from /usr/bin/hda-install:1264:in `main'
from /usr/bin/hda-install:1267:in `<main>'
http://paste.fedoraproject.org/6401/36478817
Who is online
Users browsing this forum: No registered users and 1 guest