I installed TigerVNC on 2 of my CentOS Linux-Workstations with the following command:
sudo yum install tigervnc -y
After rebooting both workstations, I did only execute the following command on one of the workstation:
sudo vncviewer
Now I inserted the ip-address of the other workstation and tried to connect to it.
No useful address for host
Does anybody have an idea to resolve that problem?
Thank you guys so much!
PS: I guarantee that the two workstations can communicate with each other (tested with ICMP --> Ping)
So thank you guys for the detailed explanation....
The solution to this problem is to specify the display with ":1".
192.168.1.1:1
Related
Issue
when vagrant up it says "It appears your machine doesn't support NFS"
Setups
Debian GNU/Linux 8 (jessie）
Vagrant 1:2.0.0
Virtualbox 5.1.30 r118389
Detail
After using apt-get to update and upgrade the system, I basically followed the instruction from the Mediawiki page, since I wanted to install Mathoid to render LaTeX equations locally for mediawiki page.
However, when I vagrant up it echos the following:
It appears your machine doesn't support NFS, or there is not an
adapter to enable NFS on this machine for Vagrant. Please verify
that `nfsd` is installed on your machine, and try again. If you're
on Windows, NFS isn't supported. If the problem persists, please
contact Vagrant support.
I checked if nfsd is correctly working on the host, and it says it's enabled.
# /etc/init.d/nfs-kernel-server status
nfs-kernel-server.service - LSB: Kernel NFS server support
Loaded: loaded (/etc/init.d/nfs-kernel-server)
Active: active (running) since Sun 2017-10-15 07:56:32 -02; 2 weeks 0 days ago
CGroup: /system.slice/nfs-kernel-server.service
??1277 /usr/sbin/rpc.mountd --manage-gids
I also tried google, and did not find a solution that fits my problem and I couldn't find any hint to resolve this. For instance, I tried to install the package
sudo apt-get install nfs-common
But it has been already installed.
Thank you in advance.
The command mentioned below works for linux mint 18.3:
sudo apt-get install nfs-common nfs-kernel-server
For Windows users seeing that error, run the following command to add support for NFS for Vagrant:
vagrant plugin install vagrant-winnfsd
The GitHub repo for this plugin is found here.
Also, to see the currently installed Vagrant plugins run this:
vagrant plugin list
Can be fixed by adding any exports to /etc/exports.
by :
modprobe nfs
modprobe nfsd
then running vagrant, which will add /etc/exports, then reloading
kernel-server and restarting vagrant.
issue http://jb-blog.readthedocs.io/en/latest/posts/0021-vagrant-nfs-problems.html
instead of installed NFS cos really no supported :
Try just removing type: nfs from the vagrant_synced_folders
More : https://www.vagrantup.com/docs/synced-folders/nfs.html
At the moment I have a little issue with installing/downloading puppet on CentOS 7.
The command that have been used is:
'sudo rpm -ivh https://yum.puppetlabs.com/puppetlab...l-7.noarch.rpm'
Then I'm getting the following error:
'Retreiving https://yum.puppetlabs.com/puppetlab...l-7.noarch.rpm
curl: (6) could not resolve host: yum.puppetlabs.com; unkown error
error: skipping https://yum.puppetlabs.com/puppetlab...l-7.noarch.rpm transfer failed'
The link (above) is working whenever I try to download it outside of Linux / VirtualBox, but not inside.
Also ping some random website doesn't work but I have read that's a commmon issue at VirtualBox.
It even can't ping my own router, and it's giving me this error:
'connect: Network is unreachable'
At the moment I have put the network options to NAT.
I'm running CentOS inside VirtualBox.
Anyone know the issue of this error ?
Thanks in advance.
Tagging your post with VirtualBox might help.
But anyway, the most common cause of this is VirtualBox DNS problems, I usually just change the nameserver in /etc/resolv.conf to 8.8.8.8 and that fixes it. You can also just reload the VM.
The solution to this problem is by simply reïnstalling. Installed some packages and turning the internet connection switch on before the installation (doh)
I am trying to invoke the tool on Centos server from the Ubantu terminal.I am getting the following error.
Tk initialization failed: no display name and no $DISPLAY environment variable.
Please Help me with this.Thanks in advance.
Connect to your CentOS machine with ssh -Y which (per man ssh)
Enables trusted X11 forwarding. Trusted X11 forwardings are not subjected to the X11 SECURITY extension controls.
That will allow your Tk process to connect to X11 on your Ubuntu machine.
I work on Ubuntu. I had the same problem while using gitk on remote machines.
So I tried following
ssh <username>#ip and ran gitk& got the "no display name and no $DISPLAY environment variable." error
ssh -X <username>#ip and ran gitk& it worked!
ssh -Y <username>#ip and ran gitk& it worked!
Thanks for the solution by Elliott Frisch.
I was having same issue using gitk on a new local machine with Ubuntu 21.04 and this solved my problem
export DISPLAY=:0
I have to setup ipmitool on my local vm for testing and learning purposes.
I followed simple steps of mentioned in the link, https://www.hugeserver.com/blog/tutorials/how-to-ipmitool-linux/
sudo yum install ipmitool
sudo modprobe ipmi_devintf
The first command will install ipmitool and the second command will install ipmi device drivers/interfaces.
After installing these two things I should be ready to use ipmitool. But I am getting errors whenever I try to run any ipmitool command.
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
I am stuck here.
I have also tried to re-install OpenIpmi and also rebooted the system.
Please help!
If this error comes in actual machine then the following post will give you the solution.
https://serverfault.com/questions/480371/ipmitool-cant-find-dev-ipmi0-or-dev-ipmidev-0
But In virtual machine, ipmitool commands will work straight away without these drivers. I faced same issue & worked for me without installing any drivers on my VirtualBox.
I have a raspberry pi running arch linux connected to the TV and want to run commands on that screen by SSH'ing from my Ubuntu machine elsewhere.
I have tried running the command SSH -Y root# and starting xclock as a test. However I get the following error:
No protocol specified
Error: Can't open display: :0
I then tried running "export DISPLAY=:0" on the arch machine, but this doesn't solve the issue.
I have X running fine and can see it on the TV and I have edited the file /etc/ssh/ssh_config to allow X11 forwarding.
Anyone know what I am doing wrong?
Many thanks
The ArchLinux wiki has some good instructions on setting things up. I struggled for a while until I found them, but for me the key was to set up SSH forwarding within sshd_config (most distros seem to enable this by default, but Arch doesn't).
Once you've enabled X forwarding in SSHD, I also found it helpful to install the dummy video driver for Xorg ("pacman -S xf86-video-dummy"), which gets rid of irritating errors about missing the RANDR extension. This might not be necessary if you already have it running a real X server locally on the Pi - personally, I'm running mine completely headless.
I've found that I don't have to worry about setting up the DISPLAY variable, or xhost, when running with 'ssh -X' from an iMac. I'd expect Ubuntu to behave the same.
looks like an authentication problem. The answer used to be
xhost +
on the console of the X display. Might help.
You probably want to set
export DISPLAY=[IP_ADDRESS_OF_ARCH_BOX]:0
on your Ubuntu box, then when you run xclock from your Ubuntu box, it'll forward the screen to the Arch box.