litespeedtech / litespeedtech/openlitespeed
OpenLiteSpeed starts unconditionally on upgrade
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 233
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 5
Description
Hi!
We're using OLS in some of our cloud servers and we give our customers the choice to use it instead o Apache, which means that the web server not in use is masked via systemctl.
My problem is that, upon upgrading OLS via yum it starts unconditionally, regardless of if it was running or Apache was, which generates conflicts as it tries to bind to ports 80 and 443.
Is there a way to stop this behaviour? Is it a packaging issue? (We're using the oficial repos from LiteSpeed Tech).
Thanks in advance.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are mentioned. Start by reproducing a yum upgrade with OpenLiteSpeed masked by systemctl while Apache is active, then inspect the package's service startup entry points; done means upgrades preserve the masked or stopped state and do not cause port conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100