After Installing RDO (OpenStack Packstack) on CentOS 7.2 (7.2.1511) I always end up with following:
Once OpenStack is successfully installed I can use OpenStack as intended.
Even that openstack-status returns:
..
openstack-nova-network: inactive (disabled on boot)
openstack-keystone: inactive (disabled on boot)
mysqld: inactive (disabled on boot)
.. (and some more)
After a reboot of the system I cannot access Keystone anymore (since it's disabled on boot) but also if I try to start the service manually with:
service openstack-nova-network restart
or all services with
openstack-service start
end in a timeout. So basically - once I've reboot the VM where I installed OpenStack I cannot use OpenStack anymore..
I installed with following commands:
sudo -i
systemctl disable NetworkManager firewalld
systemctl enable network
vi /etc/selinux/config
SELINUX=permissive
sync;reboot
vi /etc/enviroment
LANG=en_US.utf-8
LC_ALL=en_US.utf-8
yum install -y centos-release-openstack-mitaka
yum update -y
yum install -y openstack-packstack
packstack --allinone
I had the some issue with openstack mitaka on centos 7 and this solved the issue:
systemctl restart httpd.service
Since those services are disabled, they will not start when rebooted. You first need to enable the service and then start it. Refer to this.
systemctl enable openstack-keystone.service
systemctl start openstack-keystone.service
Related
I am trying to install OpenStack on CentOS 7 using PackStack. The commands I am using for installation are:
sudo systemctl disable NetworkManager
sudo systemctl stop NetworkManager
sudo systemctl disable firewalld
sudo systemctl stop firewalld
sudo systemctl enable network
sudo systemctl start network
sudo yum update -y
sudo yum install centos-release-openstack-train
sudo yum install -y openstack-packstack
After this I am editing Neutron Db Sync timeout form 300 to 900, by using the command:
sudo nano /usr/share/openstack-puppet/modules/neutron/manifests/db/sync.pp
The last command I am using for installation is
sudo packstack --allinone
All installation goes well, but in the end getting the following error:
ERROR : Error appeared during Puppet run: 10.0.2.15_controller.pp
Error: /Stage[main]/Cinder::Db::Sync/Exec[cinder-manage db_sync]: Failed to call refresh: Command exceeded timeout
You will find full trace in log /var/tmp/packstack/20210527-145513-WSj_DO/manifests/10.0.2.15_controller.pp.log
Please check log file /var/tmp/packstack/20210527-145513-WSj_DO/openstack-setup.log for more information
Additional information:
* Parameter CONFIG_NEUTRON_L2_AGENT: You have chosen OVN Neutron backend. Note that this backend does not support the VPNaaS or FWaaS services. Geneve will be used as the encapsulation method for tenant networks
* A new answerfile was created in: /root/packstack-answers-20210527-145514.txt
* Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
The content of /var/tmp/packstack/20210527-145513-WSj_DO/manifests/10.0.2.15_controller.pp.log is uploaded here:
The content of /var/tmp/packstack/20210527-145513-WSj_DO/openstack-setup is uploaded here
Can someone help me out to resolve this error? Thanks in advance.
mongo connection failed in terminal every time after ubuntu startup then after running the command sudo service mongod start it is working fine. I am using ubuntu 18.04. How to fix it that it may run always without the above command?
Try below:
sudo systemctl enable mongod
Reboot your machine and check if the service is up.
sudo systemctl status mongod
Checking out the manpage will give you a lot of information.
See systemctl manpage
http://manpages.ubuntu.com/manpages/cosmic/en/man1/systemctl.1.html
Earlier I had installed apache without issues. But after formatting my laptop, I am facing this problem.
According to the error messages I search the solution codes and go through those codes. But it is not working.
You can easily install Apache into your Ubuntu 16.04, by the following steps.
In ubuntu first, we need to update and upgrade by using the following commands
sudo apt-get update
sudo apt-get upgrade
then you can install Apache2 by following the command
sudo apt-get install apache2
After the installation you can check in the browser.
http://your_server_ip
there you can see the apache2 page over there.
sudo apt-get install apache2 -y
sudo apt-get install libpcre3 libpcre3-dev libapr1 libapr1-dev libaprutil1 libaprutil1-dev
wget http://mirrors.fibergrid.in/apache//httpd/httpd-2.4.37.tar.gz
tar -xvzf httpd-2.4.37.tar.gz
cd httpd-2.4.37
./configure --prefix=/usr/local/apache
make
make install
Apache will be installed at prefix given i.e. /usr/local/apache/
Install Apache In Ubuntu
sudo apt-get update
sudo apt-get install apache2
sudo ufw app list
sudo ufw allow 'Apache Full'
sudo ufw status // Status will be inactive.
sudo systemctl status apache2 // Apache server will be Active.
Check Apache Server
You can check your apache server is properly working or not via your IP.
Enter in your Browser
http://server_domain_or_IP
You will find the Default page.
Mange Apache Process
sudo systemctl stop apache2 // Stop Apache Server
sudo systemctl start apache2 // Start Apache Server
sudo systemctl restart apache2 // Restart Apache Server
sudo systemctl reload apache2 // Reload Apache Server
sudo systemctl disable apache2 // Disable Auto Start Server
sudo systemctl enable apache2 // Enable Auto Start Server
sudo apt-get update
sudo apt-get install apache2
sudo vim /etc/apache2/apache2.conf
Options Indexes FollowSymLinks
AllowOverride all (Change from none to all)
Require all granted (Change require all to granted)
AccessFileName .htaccess
Require all granted (Change none to all)
sudo chmod -R 777 /var/www/html/
sudo a2enmod rewrite
sudo systemctl restart apache2
Done..
check with your ip (localhost)
http://server_domain_or_IP
I am trying to install kubernetes on localhost using LXD but facing issue. I am using conjure-up for this but on proceeding localhost option is not highlighted stating that LXD not found.
[Error]
I have installed LXD as per commands given. Do I need to provide path somewhere so that conjure-up finds the path or is there some other issue?
This worked for me:
sudo apt install snapd
sudo snap install lxd
sudo snap install conjure-up --classic
sudo lxd init --auto
/snap/bin/lxc network create lxdbr0 ipv4.address=auto ipv4.nat=true ipv6.address=none ipv6.nat=false
conjure-up kubernetes
Edit: I had to sudo apt purge lxd first
Then
sudo apt upgrade
After installing lxd as suggested on conjure
sudo snap install lxd
/snap/bin/lxd init
Disabled IPV6 with the wizard
And then conjure-up
Don't forget to logout and login after adding the user to the group
(I actually did a reboot)
You'll also need to create an LXD "dir" storage. Else no pods will launch correctly. This is a known issue with conjure-up. You can specify this when you run lxd init.
https://docs.conjure-up.io/stable/en/spellbooks/kubernetes#limitations
How do I check whether a service is running or not on Linux Mint?
If that service is not running, I need to start it.
I have tried using
service <service-name> status
But for some services it is not returning any results.
service --status-all is not of much use either as it has ? marks for some services.
In Linux Mint 16 and 17, by default you should be able to use a combination of sudo service <options> and sudo update-rc.d <options>.
For example, to get a list of services, try:
sudo service --status-all (as you said).
On the displayed list, + = started, - = stopped and ? is unknown.
To disable a listed service from starting at boot try:
sudo update-rc.d <service name> disable
To enable a service to start at boot:
sudo update-rc.d <service name> enable
There are many more options for update-rc.d, try man update-rc.d for details.
A service that has been disabled (or stopped) can be manually started with:
sudo service <service name> start
A service (started manually or at boot) can stopped with:
sudo service <service name> stop
Many services also have other options like restart and force-reload but all should have start and stop.
update-rc.d - install and remove System-V style init script links
sysv-rc-conf - Run-level configuration for SysV like init script links
sudo apt-get install sysv-rc-conf
sudo sysv-rc-conf
top - display Linux processes
sudo apt-get install top
bum Boot-Up Manager - Graphical runlevel configuration tool
There are two methods of starting and managing services in Ubuntu/Mint. The old System-V style init way and upstart.
Your service can either be managed by upstart or not. If you don't see it with
service --status-all that means it is. To list services managed by upstart, use sudo initctl list. For more info, check the man pages for service and initctl.