Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rake Export does not work from Manual Install #2838

Closed
degan6 opened this issue Jul 12, 2020 · 2 comments
Closed

Rake Export does not work from Manual Install #2838

degan6 opened this issue Jul 12, 2020 · 2 comments
Assignees

Comments

@degan6
Copy link
Contributor

degan6 commented Jul 12, 2020

While prepping a dev box to work on the feature I want to add from #2813, I have been unable to get the rake export step to work.

Following the official instructions:
https://github.com/huginn/huginn/blob/master/doc/manual/installation.md

I've tired on a few times on Ubuntu and Debian VPS's on DigitalOcean with the same issue every time.
OS:

  • Debian 9.12 x64
  • Ubuntu 18.04.04 x64

Everything goes great until I get run:

sudo bundle exec rake production:export

I get the output:

/usr/local/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/rubygems_integration.rb:200: warning: constant Gem::ConfigMap is deprecated /usr/local/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/rubygems_integration.rb:200: warning: constant Gem::ConfigMap is deprecated Stopping huginn ... Exporting new services ... /usr/local/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/rubygems_integration.rb:200: warning: constant Gem::ConfigMap is deprecated

From the reading I've done on this looking at other issues (1563 & 1352) I should get two files at /etc/service but I never get those files made. So Huginn never runs.

I've tired running the export with the following command that seemed to work for some people but I just got now out.
sudo foreman export runit -a huginn -l /home/huginn/huginn/log /etc/service

I am able to reproduce this result every time I following the instructions linked above.

I would expect these results to be reproachable by creating an VPS and following the install instructions.

Any help or more insight to the problem would be greatly

@dsander
Copy link
Collaborator

dsander commented Jul 12, 2020

Thanks for the report, I haven't tested the manual installation in some time. It is possible that something broke something else.

I am assuming you modified the Procfile and removed all leading spaces from the services you commented in?

@dsander dsander self-assigned this Jul 12, 2020
@degan6
Copy link
Contributor Author

degan6 commented Jul 13, 2020

OMG, I feel so dumb. That did it. I had a space in the Profile file. I removed those spaces, re-exported and everything is working!

I can't believe it, Thank you!!

I think that is worth adding as a note in the instructions, calling that point out.

I'll make a pull request add just adds:

Note: Ensure you have no leading spaces before web: or jobs: in your Procfile file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants