Install was smooth, then trouble

[jonathankonrad]

Sorry, that did sound a bit pouty. All the Amahi team does amazing work and I have loved my HDA for the last few years. Also, bigfoot65, you give great advice.

My clients are certainly getting all their network information from the HDA and only the HDA. I'm at another box here than my usual office and this is what it reads;

Connection-specific DNS Suffix . : heritage.com
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.28.160(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, December 22, 2013 4:43:10 PM
Lease Expires . . . . . . . . . . : Sunday, December 22, 2013 8:43:08 PM
Default Gateway . . . . . . . . . : 192.168.28.1
DHCP Server . . . . . . . . . . . : 192.168.28.10

Ugh. Just did the Interactive network test again and this time it failed checking for the dashboard. Just to be clear, it did not fail there earlier. I ran that series of commands several times. Something has gone wrong, but aside from installing a couple of apps and then discovering the problem I had access them in the dashboard as I indicated above, I did nothing (aside from reboot lots). So now it is failing this part of the test

curl http://hda
curl: (7) Failed connect to hda:80; Connection refused

When I run this on the server itself (SSH into the box). So something is not right.

[bigfoot65]

Not a problem and thanks for the kind words. I try to be helpful

Everything looks good in the client info you pasted except it does not show the DNS servers. I presume the are also pointed to 192.168.28.10.

Check the status of httpd. Have been hearing rumblings of something causing it to stop and/or break.

[jonathankonrad]

Sorry, yes further down on the screen it did indicate DNS was pointing to 192.168.28.10 and only there.

So I do have some kind of problem with the httpd service. I ran this at a command prompt: service httpd status

This was the result:

Redirecting to /bin/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-12-22 19:30:47 MST; 48s ago
Process: 2523 ExecStop=/usr/sbin/httpd $OPTIONS -k graceful-stop (code=exited, status=1/FAILURE)
Process: 2521 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)

Dec 22 19:30:47 localhost.localdomain httpd[2521]: httpd: Syntax error on line 56 of /etc/httpd/conf/httpd.conf: Syntax error on line 6 of /etc/httpd/c...reference
Dec 22 19:30:47 localhost.localdomain systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Dec 22 19:30:47 localhost.localdomain httpd[2523]: httpd: Syntax error on line 56 of /etc/httpd/conf/httpd.conf: Syntax error on line 6 of /etc/httpd/c...reference
Dec 22 19:30:47 localhost.localdomain systemd[1]: httpd.service: control process exited, code=exited status=1
Dec 22 19:30:47 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server.
Dec 22 19:30:47 localhost.localdomain systemd[1]: Unit httpd.service entered failed state.

[bigfoot65]

I have seen that issue before, but unfortunately don't know how to fix it. The last person who had the problem did a reinstall. I had it happen to me once with a VM, but restored to a snapshot.

Please file a bug in the issue tracker.
bugs.amahi.org

We will need to investigate.

[jonathankonrad]

I added the bug. I may get my old HDA running for the next week. Just need to have it back up for the holidays. This is a VM HDA too but I was waiting to get it stable before I took a snap shot. I wanted some of my "base level" apps and some network tweaks. I'll try again in a bit. Thanks again for the help.

[bigfoot65]

No problem. Please check the bug you filed. I believe cpg has given you a work around that will fix the issue.

[jonathankonrad]

OK. The Amahi team does it again! That tip fixed it. I have my dashboard back. I still had the problem with the Linfo app where it was taking me to a new instance of the dashboard instead of loading the page with Linfo. However, I just uninstalled it using the dashboard. Then re-installed it and it works! I'm going to do a few more base app installs then I will officially have a 7.1 HDA running on Xenserver. One thing I was hoping to run here was a Plex server. I see that it is not released for Amahi. Could I become a tester? If not, I'll try to just install it on my own straight from their site. Cooler to have it in Amahi though. Thanks again for the tip. So glad to see it all running again!

[jonathankonrad]

Another problem I just discovered with Amahi 7.1 installed from the express CD on Fedora 19. During the installation I had only one 750GB disk attached. I let the installer do all the partitioning, I did not change anything. I realize now that was a mistake. It defaulted to:

/dev/sda1 190 MB /boot
/dev/sda2 686 GB /home
/dev/sda6 47.4 GB ) /

So of course I have run out of room, since all the HDA shares are /var/hda/files which would be a part of the "/" partition.

Is there a way to dynamically change the partition scheme? I feel like I need to do a re-install, but I've worked on this install for a while now and I would rather not start from scratch again.

[bigfoot65]

You may be able to boot with gParted Live CD and change the size.

[repat]

Bug in question here is:

https://bugs.amahi.org/issues/1231#change-3125

fix was :

Code: Select all

yum -y update openssl