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

Restart web server after it's added to bluecherry group #671

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andrey-utkin
Copy link
Contributor

The current problem is that running web requests immediately after install gives "Fatal error: could not read configuration file."

@andrey-utkin
Copy link
Contributor Author

Current patch causes a new problem :(

Preparing to unpack .../109-bluecherry_3%3a3.1.0-rc10_amd64.deb ...
sed: can't read /etc/bluecherry.conf: No such file or directory
Failed to stop apache2.service: Unit apache2.service not loaded.
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xeu nginx.service" for details.
dpkg: error processing archive /tmp/apt-dpkg-install-58cAKI/109-bluecherry_3%3a3.1.0-rc10_amd64.deb (--unpack):
 new bluecherry package pre-installation script subprocess returned error exit status 1

@andrey-utkin
Copy link
Contributor Author

The problem seem to be coming from the fact that we haven't saved a config file yet. So I looked at the postinst.

Looking at debian/bluecherry.postinst and misc/postinstall.sh, we seem to be already stopping and starting nginx. But evidently it's not bringing the desired nginx behaviour.

The current problem is that running web requests immediately after
install gives "Fatal error: could not read configuration file."
@andrey-utkin andrey-utkin force-pushed the fix-web-immediately-after-install branch from 11d1dc4 to b37c578 Compare March 7, 2024 16:55
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

Successfully merging this pull request may close these issues.

None yet

1 participant