You seem to have a hard time with timezones. Weird. I have tried twice today and did not get this error.
I believe fedora now tries to do some geoip identification. Maybe it's trying to guess your machine's approximate location based on the IP and it gets confused?
Can you try again?
Amahi 7 Express disk RC3!
Re: Amahi 7 Express disk RC3!
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
Re: Amahi 7 Express disk RC3!
Ok, installed this time. On first reboot, the screen was blank. I hit a few keys and text showed up. Once it finished, it rebooted.
Amahi did not work until I rebooted. Then had to restart httpd and hda-ctl to get the dashboard up and running.
Checked the logs and nothing looked wrong.
Amahi did not work until I rebooted. Then had to restart httpd and hda-ctl to get the dashboard up and running.
Checked the logs and nothing looked wrong.
ßî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 Express disk RC3!
now -- did you restart hda-ctl because it was stopped? Did you check if it was running?
it's supposed to be running, since it's enabled by default.
how about httpd -- same thing ... was it running?
how did you realize it needed to be restarted? or just did it intuitively?
i think this one it working reliably for me (despite the reboot needed to restart the network).
we need a checklist to release Amahi 7 -- in your view, what items are "must fix" to release?
it's supposed to be running, since it's enabled by default.
how about httpd -- same thing ... was it running?
how did you realize it needed to be restarted? or just did it intuitively?
i think this one it working reliably for me (despite the reboot needed to restart the network).
we need a checklist to release Amahi 7 -- in your view, what items are "must fix" to release?
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
Re: Amahi 7 Express disk RC3!
Looks like httpd failed to start. I restarted the HDA, but it still did not start. Did a restart of the service and it is running now.
I rebooted the HDA again and it failed to start. Looking for logs to indicate why it is not starting. httpd error log indicates a problem.
http://ur1.ca/emg4t
I rebooted the HDA again and it failed to start. Looking for logs to indicate why it is not starting. httpd error log indicates a problem.
http://ur1.ca/emg4t
ßî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 Express disk RC3!
useful. this may have changed in f19.
can you take a look at /etc/http.d/* and */* in there for references to F18-VM-64 (not case sensitive - use grep -i F18-VM-64 * */*).
not sure if that reference to your HDA DNS name is somehow created by apache on the fly or it's something fedora makes up, or it's something the amahi installer does.
can you take a look at /etc/http.d/* and */* in there for references to F18-VM-64 (not case sensitive - use grep -i F18-VM-64 * */*).
not sure if that reference to your HDA DNS name is somehow created by apache on the fly or it's something fedora makes up, or it's something the amahi installer does.
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
Re: Amahi 7 Express disk RC3!
This is what I got from the grep:
logs/error_log:[Fri Jul 12 18:53:58.374495 2013] [unique_id:alert] [pid 371] (11)Resource temporarily unavailable: AH01564: unable to find IPv4 address of "F18-VM-64.olympus.com"
logs/error_log:[Fri Jul 12 18:56:48.342399 2013] [unique_id:alert] [pid 372] (11)Resource temporarily unavailable: AH01564: unable to find IPv4 address of "F18-VM-64.olympus.com"
logs/error_log:[Fri Jul 12 18:58:36.956904 2013] [unique_id:alert] [pid 370] (11)Resource temporarily unavailable: AH01564: unable to find IPv4 address of "F18-VM-64.olympus.com"
logs/error_log:[Fri Jul 12 19:14:01.087093 2013] [unique_id:alert] [pid 370] (11)Resource temporarily unavailable: AH01564: unable to find IPv4 address of "F18-VM-64.olympus.com"
ßî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 Express disk RC3!
no, no ... cd into /etc/http.d/
i am interested in the configuration files.
i want to see the source of this issue. (i do not get this in my install)
i am interested in the configuration files.
i want to see the source of this issue. (i do not get this in my install)
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
Re: Amahi 7 Express disk RC3!
That's where I ran the grep from, well /etc/httpd as there is no http.d directory that I could see.
This is what is in that directory.
This is what is in that directory.
drwxr-xr-x. 2 root root 4096 Jul 12 18:48 conf
drwxr-xr-x. 2 root root 4096 Jul 12 18:52 conf.d
drwxr-xr-x. 2 root root 4096 Jul 12 18:48 conf.modules.d
lrwxrwxrwx. 1 root root 19 Jul 12 18:48 logs -> ../../var/log/httpd
lrwxrwxrwx. 1 root root 29 Jul 12 18:48 modules -> ../../usr/lib64/httpd/modules
ßî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 Express disk RC3!
you are correct! my bad (i should have looked it up).
i see there is no reference in the config files, so maybe apache looks up the name somehow ... perhaps from running hostname, and in the case of this VM that name does not exist in the DNS server and it bails out ..
it's a little brittle from apache doing this. perhaps we should default all hostnames to localhost, just to make sure this does not occur. if we see this issue coming up more we will have to do that.
thanks for the info.
now, let's put this one in the back-burner and see what else we need to release this baby!
i see there is no reference in the config files, so maybe apache looks up the name somehow ... perhaps from running hostname, and in the case of this VM that name does not exist in the DNS server and it bails out ..
it's a little brittle from apache doing this. perhaps we should default all hostnames to localhost, just to make sure this does not occur. if we see this issue coming up more we will have to do that.
thanks for the info.
now, let's put this one in the back-burner and see what else we need to release this baby!
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
Re: Amahi 7 Express disk RC3!
In my test VM, both start ok.
Next issue is creating a user upon initialization ... because the express install does NOT force the person installing to create a regular user ...
this requires a change in the platform.
Next issue is creating a user upon initialization ... because the express install does NOT force the person installing to create a regular user ...
this requires a change in the platform.
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
Who is online
Users browsing this forum: No registered users and 6 guests