How to safely stop Foreman/Puppet services / reboot server

[Neeloj]

thanks for your replay @gvde

@gvde

I don’t know the topic you are referring to

here are two of them:

How to safely stop/start Foreman/Puppet services

Problem: All the Foreman/Puppet services are on the same server. Suppose your server needs maintenance (so you need to stop the services) or there is an power outage (then you may need to restart services). Are the following services a complete list in this case? Is there any sequence to stop/start them? Here are all the services I can think of: foreman-proxy apache2 postgresql puppetdb puppetserver puppet One thing I learned is that you should not run “foreman-installer” again: it wil…

After restart the server foreman doesnt work

hi all, after restart the Puppet/Foreman-Server foreman cannot be started, when I stop foreman-proxy, foreman.service & foreman.socket. Puppet work fine. What I see in journalctl -xe: Jul 04 11:57:09 mysite foreman[34668]: from /usr/share/foreman/bin/rails:9:in `<main>' Jul 04 11:57:09 mysite systemd[1]: foreman.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecS…

@gvde

You can always use foreman-maintain service stop to stop all services.

I dont have the command:

root@test-srv:~# foreman-maintain
foreman-maintain: command not found
root@test-srv:~# dpkg-query -l | grep foreman
ii  foreman                                3.5.1-1+ubuntu2004                amd64        Systems management web interface
ii  foreman-cli                            3.5.1-1+ubuntu2004                all          metapackage providing hammer CLI for Foreman
ii  foreman-debug                          3.5.1-1+ubuntu2004                all          provides support utility foreman-debug.
ii  foreman-dynflow-sidekiq                3.5.1-1+ubuntu2004                all          package providing dynflow sidekiq services for Foreman
ii  foreman-installer                      3.5.1-1+ubuntu2004                all          Automated puppet-based installer for The Foreman
ii  foreman-postgresql                     3.5.1-1+ubuntu2004                all          metapackage providing PostgreSQL dependencies for Foreman
ii  foreman-proxy                          3.5.1-1+ubuntu2004                all          RESTful proxies for DNS, DHCP, TFTP, and Puppet
ii  foreman-service                        3.5.1-1+ubuntu2004                all          package providing Foreman services running via puma
ii  ruby-foreman-column-view               0.4.0-2                           all          Foreman Column View Plugin
ii  ruby-foreman-deface                    1.9.0-2                           all          Foreman Deface Plugin Dependency
ii  ruby-foreman-puppet                    5.0.0-1                           all          Foreman Puppet Plugin
ii  ruby-hammer-cli-foreman                3.5.0-1+ubuntu2004                all          Foreman commands for Hammer
ii  ruby-hammer-cli-foreman-puppet         0.0.6-1                           all          Foreman Puppet plugin for Hammer CLI

@gvde

This is completely wrong. Running foreman-installer maintains the correct configuration for the system. I don’t know what problem you may see

After reboot my server without stopping any services. I could not login! and all my hosts, config groups, host groups was deleted! after check the log file I saw there was a postgres error, I logged in and the foreman role and foreman database was deleted! this happens to me on test & production server!