How to fix salt-minion service entering "reloading" state after executing apache.modules - apache

Facing a strange issue!
On listing apache modules on minion by executing following command from salt-master,
# salt 'target' apache.modules
on minion, salt-minion service enters "reloading" state.
# systemctl status salt-minion
● salt-minion.service - The Salt Minion
Loaded: loaded (/usr/lib/systemd/system/salt-minion.service; enabled; vendor preset: disabled)
Active: reloading (reload) since Wed 2021-09-29 00:48:29 PDT; 2 weeks 2 days ago
Docs: man:salt-minion(1)
file:///usr/share/doc/salt/html/contents.html
https://docs.saltstack.com/en/latest/contents.html
Main PID: 3582 (salt-minion)
Status: "Reading configuration..."
Few details:
Important to note that previously it was Apache/2.4.6 (CentOS) and this issue started after upgrading to Apache/2.4.48 (IUS)
salt-master and salt-minion both the versions are 3003.1
It is Centos 7 VM
service remains in "reloading" state until restarted
minion logs does not log anything on change of service state

Related

Redis Won't Start Scheduled restart job, restart counter is at 5

My working and functional redis server 5.0.7 installation on Ubuntu 20.04, simply refuses to start without any changes having be made to the config file. It is identical to a config on a different different server running redis that starts, therefore I think the error message is systemd related
● redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-07-30 23:09:49 HKT; 32s ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Process: 8141 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=1/FAILURE)
redis-server.service: Control process exited, code=exited, status=1/FAILURE
redis-server.service: Failed with result 'exit-code'.
Failed to start Advanced key-value store.
redis-server.service: Scheduled restart job, restart counter is at 5.
Stopped Advanced key-value store.
redis-server.service: Start request repeated too quickly.
redis-server.service: Failed with result 'exit-code'.
Failed to start Advanced key-value store.
Any ideas?
Thanks

How to restart redis server with authentication?

I am trying to restart a redis server using the following command:
service redis-server restart
And I am getting the error:
Failed to restart redis-server.service: Interactive authentication required.
See system logs and 'systemctl status redis-server.service' for details.
I know the redis password but I am not sure how to pass it in in the line of code that I mentioned.
The recommended logs are like this and not very helpful:
● redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-04-05 13:31:23 UTC; 12min ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Process: 358704 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=1/FAILURE)

Cloudstack KVM installation failed

I'm installing cloudstack on ubuntu 20.04 by following this document.
I installed qemu-kvm and cloudstack-agent successfully but I'm not able to start libvirtd.service, on seeing the status I'm getting following errors
● libvirtd.service - Virtualization daemon
Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-03-16 18:00:09 IST; 1min 28s ago
TriggeredBy: ● libvirtd-admin.socket
● libvirtd.socket
● libvirtd-ro.socket
Docs: man:libvirtd(8)
https://libvirt.org
Process: 232313 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, status=6)
Main PID: 232313 (code=exited, status=6)
Mar 16 18:00:09 host systemd[1]: libvirtd.service: Scheduled restart job, restart counter is at 5.
Mar 16 18:00:09 host systemd[1]: Stopped Virtualization daemon.
Mar 16 18:00:09 host systemd[1]: libvirtd.service: Start request repeated too quickly.
Mar 16 18:00:09 host systemd[1]: libvirtd.service: Failed with result 'exit-code'.
Mar 16 18:00:09 host systemd[1]: Failed to start Virtualization daemon.
on seeing the log of journalctl -xe it is showing cloudstack-usage.service: Failed with result 'exit-code'
can any one suggest what whould be the issue.
Are you trying this on a virtualised VM, or baremetal host, or on a raspberrypi? This means some other service hasn't started which libvirtd may depend on. See if you can run "systemctl daemon-reload" and try to start libvirtd manually "systemctl start libvirtd", and then try rest. The cloudstack-usage service can be started once the mysql server is running. If you've further questions I encourage you to join the CloudStack users mailing list and ask questions there - http://cloudstack.apache.org/mailing-lists.html
I got that same error message when following the official install guide when starting the mysql server. The problem was for me that [mysqld] was missing in the my.conf file before the config snippet. The documentation is misleading in that case (like the secion header is only relevant when editing that alternative mysql config file mentioned later there).

Apache HTTP server is not running

I have build a website on Ubuntu 18.04 and tried to install SSL (Let's Encrypt) for the domain. So I installed everything from the guides, but after it I could not access admin panel for my website, as well as cannot upload or download any files from FTP server.
So I decided to delete everything related to SSL (from some guides on internet) and I was thinking that somehow it will come back to previous situation. However, it did not happened.
Now I cannot upload anything to the FTP or download from it. Cannot access the admin page as well. I have a access to server root, so this is the only way (as I understand) to fix the problem.
I have tried to do this:
sudo certbot --apache -d domain.lt -d www.domain.lt
However I get the error:
Error while running apache2ctl configtest.
Action configtest failed. The Apache error log may have more information.apache2:
Syntax error on line 225 of /etc/apache2/apache2.conf: Syntax error on line 13 of /etc/apache2/sites-enabled/opencart-le-ssl.conf: Could not open configuration file /etc/letsencrypt/options-ssl-apache.conf: No such file or directory
I see that Apache is not running and do not know how to make it run.
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since Fri 2020-10-16 13:16:42 EEST; 11min ago
Process: 18181 ExecStop=/usr/sbin/apachectl stop (code=exited, status=1/FAILURE)
Process: 18186 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Main PID: 366 (code=exited, status=0/SUCCESS)
Oct 16 13:16:42 domain.lt systemd[1]: Starting The Apache HTTP Server...
Oct 16 13:16:42 domain.lt apachectl[18186]: apache2: Syntax error on line 225 of /etc/apache2/apache2.conf: Syntax error on line 13 of /etc/apache2/sites-enabled/opencart-le-ssl.conf:
Oct 16 13:16:42 domain.lt apachectl[18186]: Action 'start' failed.
Any help how to enable ssl and make it work again is appreciated. I am not very good as sysadmin, just following the guides.
Managed to enter the website however still cannot log in into /admin panel. I am entering username and password, however nothing happens.
FTP still remains only for navigation, cannot upload or download files.

why i get problem while running apache2 in ubuntu?

Here is my details about the apache error, hope you will can find out the problems
apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; disabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since Tue 2020-02-25 12:06:14 +0545; 13min ago
Process: 25134 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Please check first : /var/log/apache2/error.log
After you have comprehended which procedure utilizes port 80, you can choose in the event that you need to end it or on the off chance that you have an unsupported setup and can't utilize Apache on port 80
To check for that:- netstat -anp | grep ':80\s'