Project

General

Profile

Bug #1090

OpenVPN is not starting up properly

Added by bigfoot65 over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
VPN
Target version:
Start date:
08/17/2013
Due date:
% Done:

0%


Description

The app for Amahi 7 is broken. The service will not start due to some error with the init script. A comparison of the Fedora 14 OpenVPN setup with Fedora 19 shows some files possibly missing in the /etc/openvpn directory.

History

#1 Updated by cpg over 8 years ago

  • Subject changed from OpenVPN to OpenVPN is not starting up properly
  • Status changed from New to Feedback
  • Assignee changed from cpg to bigfoot65

This opened a small can of worms. I have made a number of fixes related to this issue. See commit:76c5dab48.

In any case, the servers area and OpenVPN needs a new platform to work. please install it to test:

http://alpha.amahi.org/tmp/hda-platform-7.1.1-1.x86_64.rpm

#2 Updated by bigfoot65 over 8 years ago

Tested with new platform and all works except the service in the servers tab is showing stopped. Verified the service is running.

Awesome job!

#3 Updated by cpg over 8 years ago

  • Status changed from Feedback to Assigned
  • Assignee changed from bigfoot65 to cpg

Will take a look at the status issue.

#4 Updated by cpg over 8 years ago

  • Status changed from Assigned to Feedback
  • Assignee changed from cpg to bigfoot65

openvpn makes the directory where the PID is only readable by root.

so we would need some amount of complexity to make this as it is.

there is a simpler solution: a change in the installer to open up the directory.

it appears to work. please verify and if it works, please close.

#5 Updated by bigfoot65 over 8 years ago

  • Status changed from Feedback to Assigned
  • Assignee changed from bigfoot65 to cpg

I installed and checked the service in servers tab. It was stopped. Checked the /var/run/optnvpn folder and it was empty.

I did:

systemctl restart openvpn@amahi.service

and the amahi.pid was created in that folder.

Might need to do that in the script as it does not seem to be creating the pid file on install.

#6 Updated by cpg over 8 years ago

i think that may be a separate bug in general.

i see no way other than monit that a newly installed service would get started upon installation.

was monit running on this machine?

#7 Updated by bigfoot65 over 8 years ago

Yes monit is running.

#8 Updated by cpg over 8 years ago

can you then check /var/log/monit.log and see if it tried to start it and fail?

it may have not even tried to start it.

#9 Updated by bigfoot65 over 8 years ago

Not sure what this means, but something is amiss:

[CDT Aug 18 15:56:22] info     : Shutting down monit HTTP server
[CDT Aug 18 15:56:22] info     : monit HTTP server stopped
[CDT Aug 18 15:56:22] info     : monit daemon with pid [676] killed
[CDT Aug 18 15:56:22] info     : 'system_localhost' Monit stopped
[CDT Aug 18 15:56:22] info     : Starting monit daemon with http interface at [localhost:2812]
[CDT Aug 18 15:56:22] info     : Starting monit HTTP server at [localhost:2812]
[CDT Aug 18 15:56:22] info     : monit HTTP server started
[CDT Aug 18 15:56:22] info     : 'system_localhost' Monit started
[CDT Aug 18 15:56:22] error    : 'amahi' process is not running
[CDT Aug 18 15:56:22] info     : 'amahi' trying to restart
[CDT Aug 18 15:56:22] info     : 'amahi' start: /usr/bin/systemctl
[CDT Aug 18 15:56:52] error    : 'amahi' failed to start
[CDT Aug 18 15:57:52] error    : 'amahi' process is not running
[CDT Aug 18 15:57:52] info     : 'amahi' trying to restart
[CDT Aug 18 15:57:52] info     : 'amahi' start: /usr/bin/systemctl
[CDT Aug 18 15:58:22] error    : 'amahi' failed to start
[CDT Aug 18 15:59:22] info     : 'amahi' process is running with pid 12600

Not sure if this occurred when I installed OpenVPN or afterwards.

#10 Updated by cpg over 8 years ago

  • Assignee changed from cpg to bigfoot65

looks like you do not have the hda-platform listed above (in the alpha site).

the platform now handles services of this name openvpn@amahi. the latest public platform would choke at the @ and not parse the openvpn@, taking amahi as the name of the service.

please try again with that platform :)

#11 Updated by bigfoot65 over 8 years ago

Crap, you are right. I reverted my VM to a snapshot and forgot to add it. I will try again.

#12 Updated by bigfoot65 over 8 years ago

  • Status changed from Assigned to Closed

Just reinstalled after adding the new platform and it's now working correctly. This one should be ready for LIVE conditional on the release of the new platform.

Also available in: Atom