Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #9460

closed

pulp3-source-fedora34 can't start pulp with pstart/pstop or with `sudo systemctl restart pulpcore`

Added by bmbouter about 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
fao89
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
3.16.0
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Dev Environment
Sprint:
Quarter:

Description

  1. I am using HEAD from pulp_installer, i.e. commit 66239334.
  2. I vagrant up with vagrant up pulp3-source-fedora34
  3. I then enter the virtualenv with workon pulp.
  4. I observe that pstop and pstop don't work
$ pstop
systemctl stop
Too few arguments.

$ pstart
systemctl start
Too few arguments.
  1. I see pulp isn't working because pulp status yields
Error: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.20.1</center>
</body>
</html>

  1. I try to use the new pulpcore unit and it restarts without error sudo systemctl restart pulpcore

  2. The pulp status produces the same error.

Also when I watch the logs during restart I don't see it restarting (with either pstop/pstart or the systemd unit).

Actions
Send by e-mail Copy link

Also available in: Atom PDF