CentOS7: Failed to start gunicorn.service: Unit not found.

Open
#364 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
centos, linux
Domain
devops

Research direction

Reproduce the declared python and python::gunicorn resources on CentOS 7 and inspect the service behavior around the reported systemctl invocation. Compare the module's Gunicorn management behavior with the expected service unit; done means the declaration creates a startable gunicorn.service without the reported Unit not found error.

Written by the indexing model from the issue text.

Description

using master:HEAD on CentOS7 having declared:

class { 'python':
   version    => 'system',
   pip        => 'present',
   dev        => 'absent',
   virtualenv => 'absent',
   gunicorn   => 'present',
   manage_gunicorn => true,
 }

and:

python::gunicorn { 'puppet_reports':
   ensure      => present,
   mode        => 'wsgi',
   dir         => $dir,
   bind        => "0.0.0.0:${port}",
   accesslog   => "${log_dir}/access.log",
   errorlog    => "${log_dir}/error.log",
   appmodule   => 'puppet_reports:app',
   timeout     => 30,
   owner       => $owner,
   require     => Vcsrepo[$dir],
 }

I get:

Error: Could not start Service[gunicorn]: Execution of '/bin/systemctl start gunicorn' returned 5: Failed to start gunicorn.service: Unit not found.
Wrapped exception:
Execution of '/bin/systemctl start gunicorn' returned 5: Failed to start gunicorn.service: Unit not found.
Error: /Stage[main]/Python::Config/Service[gunicorn]/ensure: change from stopped to running failed: Could not start Service[gunicorn]: Execution of '/bin/systemctl start gunicorn' returned 5: Failed to start gunicorn.service: Unit not found.
Notice: /Stage[main]/Python/Anchor[python::end]: Dependency Service[gunicorn] has failures: true
Warning: /Stage[main]/Python/Anchor[python::end]: Skipping because of failed dependencies
Dominant language
Ruby
Stars
196
Forks
372
Avg merge
1d 18m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voxpupuli/puppet-python

All issues in voxpupuli/puppet-python

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.