I have RHEL 6.8 Machine installed in a VM. I moved one file libc.so.6 from /lib64/ to /lib64/backup/. Since then I am not able to connect to that machine through Putty or WinSCP. Both the tools give the same error. Software caused connection abort.
As I haven't created this VM, I don't have permission to restart it. But will restarting the machine, solve the issue ? What can be the solution for this situation, except re-installing the OS ?
libc.so.6 is the standard C library and by moving it you borked your system quite well.
The error you get means that SSH connection cannot be established.
All you can do now is access the machine via the console and restore the file in its original position.
The time-saving workaround is to reinstall the OS.
Note :- Reinstalling the OS will solve the issue, but you'll lose all the installed software and the data. That's why it is a workaround and not the solution.
Related
I've recently started working with STAF and couldn't get 2 machines to communicate with each other. One of those machines is a Linux ec2-instance on AWS and can't be pinged.
I was planning on pinging STAF from one virtual machine to another to see if the company firewall could be the cause of this but I can't seem to use commands on linux (like "staf local ping ping" on windows for example). When I try to run STAFProc with gdb (in /usr/local/staf/bin) I get the following error.
(gdb) run
Starting program: /usr/local/staf/bin/STAFProc
/bin/bash: /usr/local/staf/bin/STAFProc: No such file or directory
(The STAFProc file is there though. Does gdb work from another directory?)
I'm not exactly experienced with STAF, AWS or even Linux so any help to get me started with debugging would be greatly appreciated.
Though it is a bit long since the question is asked and the op seem to figure it out already, I might still post my solution as well.
There is a possibility that it is caused by trying to open a 32bit binary on a 64bit device.
If you are working on Debian based os, try
sudo apt-get install lib32stdc++6
I need to have access to Virtualbox from within the WSL, I have tried to sudo apt-get install virtualbox but I end up with the following error:
WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-3.4.0+.
You will not be able to start VMs until this problem is fixed.
4.3.36_Ubuntur105129
Vagrant is now capable of detecting that it is running on WSL.
How to configure Windows and WSL to enable this feature is described on Vagrant website
They claim it's an advanced feature but the configuration seems quite straightforward.
Unfortunately, that will not work (at least for now), as explained here: https://github.com/Microsoft/BashOnWindows/issues/549
Okay so I'm very new at all of this so please forgive me if I don't provide enough information but feel free to ask for more.
I had to install ParaView from source on my linux system. ParaView requires Qt to be installed to be able to compile and install it. So I installed Qt on my linux system from source as well (version 4.8.6 to be precise). My ParaView is now installed but I can't seem to run it. The first time I tried I got the following output:
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
QWSSocket::connectToLocalFile could not connect:: Connection refused
No Qt for Embedded Linux server appears to be running.
If you want to run this program as a server,
add the "-qws" command-line option.
When I ran it as sudo, I got the following output:
Qt for Embedded Linux data directory is not owned by user 0: /tmp/qtembedded-0
I have no idea what this means or how to fix it, any help will be much appreciated.
Extra info: I installed ParaView version 4.4
my Qt dir is /usr/local/Trolltech/QtEmbedded-4.8.6/bin
my ParaView dir is /usr/local/bin
I couldn't find anything on google or on here and that's why I'm asking.
If you want to run this program as a server,
add the "-qws" command-line option.
You really need this; append it to the line where you call your binary. When trying to start it on a machine that runs X11 you'll need QVFb installed and running, too, plus support for it (graphics, mouse and keyboard) compiled into the Qt libs.
I strongly advise against starting with root privileges.
It seems that you ran the application under the user, then killed it, switched to root and tried to run it again.
You can just remove the temporary folder.
rm -rf /tmp/qtembedded-0
I just removed
rm -rf /tmp/qtembedded-0
and then restarted the framebuffer and it works for me.
Mistake: I changed the permission of /tmp/qtembedded-0 while framebuffer was running.
I had a fully patched 15.04 installation and did the do-release-update. It's a VM with a popular US hoster, I have root and have performed earlier similar upgrades on this machine with no problems. At the end of the update I was advised to reboot, as usual, so I just entered "reboot" but only got the message in the title and am back at the prompt.
I have Plesk access to the container so thought I'd reboot from there - bad mistake: after the shutdown nothing came up and I couldn't even SSH in. The tech support guys "did something to MySQL" (sorry to be vague, that's all I got) and I'm back up now. However, I think I'm back in the same situation because trying "reboot" just gives the same "Failed to talk to init daemon" message.
The server seems stable enough in that it is serving sites OK, but I'm not happy with is being so fragile. I can't now update my kernel, amongst other things.
What the heck happened during this update?
Turns out this was down to the VM image the hosting provider was running not being fully compatible with 15.10. I'm sure this isn't a widespread Ubuntu issue.
my environment:
kubuntu : 3.2.0-generic-pae
vmware player: VMware-Player-4.0.4-744019.i386.bundle
And i have been installed it.
$sh VMware-Player-4.0.4-744019.i386.bundle
I have a problem, when i launch "menu->system->VMware Player"
it launch a window and start compiling:
[ok] Virtual Machine Monitor
[failed] Virtual Network Device
[ok] VMware Blocking Filesystem
[ok] Virtual Machine Communication Interface
[ok] VMCI Sockets
[result fail]Starting Vmare Services
See log file /tmp/vmware-root/modconfig-2722.log for detail
from log file:
[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config":
No such file or directory.
[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences"
No such file or directory.
Failed to find /lib/modules/preferred/build/include/linux/version.h
Failed to compile module vmnet!
Could some people tell me what's wrong ?
I suppose that there are no linux headers installed on your machine, that is why it is impossible to build the vmnet module. You must install headers and then try once again.
Ok, I've had the same problem this evening when upgrading from 4.0.3 to 4.0.4. What I've found to work is to first download the patch from this VMWare community thread - http://communities.vmware.com/thread/344213
Unzip it and then open the patch-modules_3.2.0.sh in gedit. There will be three lines at the top that read:
fpatch=vmware3.2.0.patch
vmreqver=8.0.2
plreqver=4.0.2
You have to change the plreqver=4.0.2 to plreqver=4.0.4
Then, open your terminal and run
sudo ./patch-modules_3.2.0.sh
As a side note, keep that file handy, because I found that I had to do the same thing when upgrading from 4.0.2 to 4.0.3 in Ubuntu 12.04. However, when you try the same again in the next upgrade (e.g. change the plreqver to 4.0.5 and run the script), it will say that the file is already patched and it won't work.
To get around this, you need to go to the "/usr/lib/vmware/modules/source/" folder, find the hidden file called ".patched", and delete it (easiest option is to "sudo nautilus" in terminal and hunt through the folder structure). Then it thinks that it hasn't been patched and does the process again.
Hope this gets your VMWare back up and running.