RESOLVED: OpenVPN ALS installation broke server

[bigfoot65]

This may have become a bigger issue. Did you have a power outage or turn off the HDA without shutting down?

Seems like some files got corrupted or are missing. I presume the httpd output now does not show any warnings.

Seems to be a coincidence that it happened after the OpenVPN ALS install. There is nothing that an app modifies or changes in those areas.

The only other option prior to reinstall is to check logs in /var/log for any other issues that we may not have seen.

[intellected]

I did and it did not work.

[bigfoot65]

Please see my previous post. Also have you restarted the HDA since doing all this?

[intellected]

which logs in particular?

[intellected]

https://www.wetransfer.com/downloads/c5 ... 843/341e9c

[bigfoot65]

Will take a look and get back with you.

[ Post made via Android ]

[bigfoot65]

Ok, I see a few things going on here. Seems there is a lot of different errors in the logs.

a. monit.log: indicates vnstat is failing.
b. messages: shows numerous issues with different things. Did you have a power outage or power off the server without a normal shutdown?
c. amahi-sync.log: Shows you have it installed, but the share name is incorrect. Should be /var/hda/files/Public and not /var/hda/files/public
d. The update to the kernel on 27 Feb looks suspicious. A kernel update could be part of the issue. Did you reboot after the update?

Feb 27 22:53:32 Installed: kernel-3.12.11-201.fc19.x86_64

e. greyhole.log: Log file indicates you are not using Greyhole. If not, suggest you disable it and stop the service. It will continue to generate logs if you don't.
f. amahi-app-installer.log: Shows some errors as well. Not sure if they are relevant, but some do cause concern.
g. monitorix.log: Shows this error about a disk being unavailable. Did this ever exist?

Use of uninitialized value in lc at /usr/lib/monitorix/disk.pm line 58.
Sat Mar 1 20:33:08 2014 - disk::disk_init: ERROR: invalid or inexistent device name '/dev/sdb'.
Sat Mar 1 20:33:08 2014 - disk::disk_init: 'accept_invalid_disk' option is not set.
Sat Mar 1 21:18:12 2014 - SIGTERM caught.
Sat Mar 1 21:18:12 2014 - Exiting.
Sat Mar 1 21:18:58 2014 - Starting Monitorix version 3.4.0 (pid 393).

All in all, things look like one big mess. Not sure what the cause of your issue can be as there are so many things that appear out of sorts. It may be tough to track down.

Have you considered doing a reinstall? I know it can be painful and not the best solution, but it may take hours to find the issue. I don't know where to even begin.

[intellected]

Thanks alot for the much appreciated effort to help me out !

a. Never used it, so I dont know why and how.
b. I think this could be the case, yes.
c. I can reach shares with no problem tho.
d. Yes I did, I posted you then.
e. I dont really use it but could be related to g. no?
f. Are these caused by install HDA?
g. I think so, mounted external usb hd drive?

Yes, I will reinstall.
Too much a mess and learned enough for now.
I will let you know the outcome thanks again for your time!

[bigfoot65]

Thanks for the response. Sorry that it appears a reinstall is the best option. Hoepfully you will be back up and running in no time.

Certainly should be a lot less issues this time

[justtapout]

I have had to fix this myself a few times.
Install adito/openvpn from amahi apps store.
login to adito then choose management console in the top right corner.
choose server option
change the port option to something else (mine is 4443)
change the bind address to only the ip address of the box (defaulted to all interfaces. mine is 192.168.1.3)
change http port to anything else (defaulted to 80 which is a cause of the problem)
now sudo service httpd restart( you will get an error)
now sudo yum -y update
once finished run sudo service httpd restart again. error should be gone


This has worked for me several times. I make it a point when setting up a new amahi box to do this first.