I am currently new with OpenStack/packstack, I have successfully installed it on Centos 7 (VM). But when I turn off and power on the VM again, I need to have to repeat the long installation process of packstack. I need to run this specific code packstack --answer-file 24.01.19.conf in order for me to access the Openstack Web Interface. I tried running openstack-service restart|start|stop|status but this causes an error "command not found". Any other way around to access the web interface without running the packstack --answer-file every time I start my VM? Thanks in advance
To use openstack-service, install "openstack-utils"
sudo yum install -y openstack-utils
This is happening because the IP address of controller node changes after reboot and if IP address changes you need to re-run the packstack.
My recommendation is to statically bind the IP address to the VM where the packstack is running.
Link to bind IP address to VM/Mac in KVM: here!
How can i configure my volume in ~/.pam_mount.conf.xml so set a different port for ssh?
Currently, default (using port 22) this works:
<volume options="nosuid,nodev"
user="yourUsername"
mountpoint="~/mountpoint"
path="sshfs#%(USER)#server:" fstype="fuse" />
Thanks for hints.
G. does help and manpage shows not the right way for me to find out.
Kind regards
flobee
I got it.
A working local ssh config must exists. Than it works :-)
NFS Mount is not working in my RHEL 7 AWS instance.
When I do a
mount -o nfsvers=3 10.10.11.10:/ndvp2 /root/mountme2/
I get the error:
mount.nfs: requested NFS version or transport protocol is not supported
Can anyone point me where I am wrong?
Thanks.
Check the nfs service is started or reboot the nfs service.
sudo systemctl status nfs-kernel-server
In my case this package was not running and the issue was in /etc/exports file where i was having same IP address for two machines.
So i commented one ip address for the machine and restarted nf-kernel-server using
sudo systemctl restart nfs-kernel-server and reload the machine.
It worked.
A precision which might be useful for the dump (like me): systemctl status nfs-server.service and systemctl start nfs-server.service must be executed on the server!
Some additional data
If, like me, you've deleted a VM without shutting it down right you might also need to manually edit the file /etc/exports because NFS is trying to connect to it and fails but doesn't continue with the next, it just dies.
After that you can manually restart as mentioned in other answers.
In my case, a simple reload didn't suffice. I had to perform a full restart:
sudo systemctl status nfs-kernel-server
In my case, it didn't work correctly with version NFS 4.1.
So in Vargantfile in each place where is type: 'nfs' I added coma and nfs_version: 4, nfs_udp: false
Here is more detailing explanation NFS
If you're giving a specific protocol to connect with, also check to make sure your NFS server has that protocol enabled.
I got this error when trying to start up a Vagrant box, and my nfs server was running. It turns out that the command Vagrant uses is:
mount -o vers=3,udp,rw,actimeo=1 192.168.56.1:/dir/on/host /vagrant
Which specifically asks for UDP. My server was running but it was not configured to enable connecting over UDP. After consulting /etc/nfs.conf, I created /etc/nfs.conf.d/10-enable-udp.conf with the following contents to enable udp:
[nfsd]
udp=y
The name of the file doesn't matter, as long as it's in the conf.d directory and ends in .conf. Depending on your distribution it may be configured differently. You can directly edit nfs.conf, but using a conf.d file is more likely to preserve the changes after upgrading your system.
Try to ping IP address of the server "ping " from client "ping , if you get reply then install nfs server on the host. Then edit /etc/exports file don't forget to add port along with IP address
I got the solution: make an entry in nfs server /etc/nfsmount.conf with Defaultvers=3 .
There will # Defaultvers=3 just unhash it and then mount on nfs client.
Issue will be resolved!
I have tried all ways to configure the X11 forward .but it still failed .
the X11forward yes ,and Xauth is installed and so on .
but when I type ssh -Xv mydomain
it still have error
"X11 forwarding request failed on channel 0"
i feel really confused the reason why it has error
could you help on this please
thanks
This is not documented well and the option is no longer in the default config, which further complicates the issue. You need to add the config entry that enables Xforwarding from any host not just localhost.
Try adding
X11UseLocalhost no
to
/etc/ssh/sshd_config
I did an update on my opensuse box and networking stopped working. The system is trying to use networkmanager, even though it isn't installed. I am using yast to try and get it to use ifup, but it complains about no network connection. I tried running:
ifup eth0
and I get back:
Network is managed by '' -> skipping
Does anyone out there know why it is coming back empty and if there is a config file that I can manually tweak to fix this?
I'm assuming you are running 12.3 or 13.1 with systemd.
Disable network manager if it exists:
systemctl disable networkmanager.service
Enable network.service:
systemctl enable network.service
Make sure ifcfg-eth0 exists with a configuration in /etc/sysconfig/network/
Run ifup eth0
Hope this will help someone.
1. Disable NetworkManager, Stop is and then enable it and restart it respectively.
2. All this happens in console. Check the status for NetworkManager and in the status messages it should show that the interface(wierless) is disconnected. Confirm this by typing command "sudo nmcli c"
3. Type command "sudo iwlist (wireless-interface) scan" to show you the available wireless networks
4. If you see the network that you want to connect to listed, type command "nmcli a" and enter the corresponding connect phrase/password to connect