Virtualbox 6.1 Code NS_ERROR_SOCKET_FAIL (0xC1F30200) - IPC daemon socket error (extended info not a

[AndreTr]

Hallo,

I am running OpenSUSE Leap 15.3 and Virtualbox used to work fine. Then, After some updates, it would not start as a normal user (only start as user root).

This is the error:
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_SOCKET_FAIL (0xC1F30200) - IPC daemon socket error (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

I have searched the net for solutions and tried all the fixes I can find, from removing the config, to checking permissions on /tmp to re-installing.

It is not creating the ipc folder in /tmp. Only creates it for root.

Permissions is correct:
# ls -ld /tmp
drwxrwxrwt 1 root root 167712 Feb 22 15:37 /tmp

Any idea what could be wrong?

Thanks
Andre

[scottgus1]

I'm no Linux guru, but I wonder if the updates to the host changed the Linux kernel headers that are a prerequisite for official Virtualbox on the host.

Or you're running the fork: run this in the terminal:

vboxmanage -version
If the output looks like this:

6.1.32r149290

where the numbers are your installed version, then you're running official Virtualbox. Uninstall Virtualbox. There may be leftover Virtualbox files, purge all files related to the Virtualbox install (not the VMs or Virtualbox.XML, though; these files can stay) - web-search how to do this. Then run the prerequisites, then install from https://www.virtualbox.org/wiki/Linux_Downloads

If the output looks like this:

6.1.32_Linuxr149290

where _Linux is the flavor of Linux of your host OS, then you're running the fork of Virtualbox which the Linux distro makes and is responsible for support through their support channels. You could uninstall it and install official prerequisites and Virtualbox, or ask the Linux distro for help to fix this.

[paulson]

VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_SOCKET_FAIL (0xC1F30200) - IPC daemon socket error (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

It is not creating the ipc folder in /tmp. Only creates it for root.

Permissions is correct:
# ls -ld /tmp
drwxrwxrwt 1 root root 167712 Feb 22 15:37 /tmp

Is there already a directory named /tmp/.vbox-$USER-ipc and if so what are its permissions?

[AndreTr]

Hallo, apologies for taking so long to respond.

To answer the first message from scottgus1:

I do not have a command vboxmanage as part of the installation.

VirtualBox runs fine as the root user, so it works, it is just that when I run it as a normal user, it complains.

To answer the second message (paulson):

There is no /tmp/.vbox-andre-ipc folder. There used to be one, but I deleted it on suggestions from other posts.
Now it does not even want to create a new folder. It just pops the error without even trying it seems

Andre

[AndreTr]

I uninstalled the SUSE version of Virtualbox and downloaded the packages from the Virtualbox site and installed that and now I have the vboxmanage command.

Output is : 6.1.32r149290

But the problem still exists. I can run as root, but not as normal user.

I checked the permissions of /tmp. I can create the folder /tmp/.vbox-ander-ipc/ manually and after I tried to run VirtualBox, it deletes the folder, so it does have permission.

I attach a screenshot of the error I get when I try to run VirtualBox

Screenshot_2022-04-07_07-17-44.png (25.71 KiB) Viewed 5988 times

[denk]

I have exactly the same issue on Arch Linux, even with an official dev-build downloaded from the virtualbox download page.
Permissions of /tmp: drwxrwxrwt 33 root root 1060 22. Apr 16:48 tmp
Mount options of /tmp: tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=12179404k,nr_inodes=1048576,inode64)

The thing is, that the mentioned permissions and mount options work with 6.1.30 but not with 6.1.32 and 6.1.34 and 6.1.97-150532. And I've never changed those permissions or mount options.
Even if I start Virtualbox as root, I get the same error message.

i really have no clue, why this happens. Whenever I update my running 6.1.30 to anything newer, the error occurs. If I then downgrade to 6.1.30 everything works again. With our without reboot in between, doesn't matter.
I would be really thankful for help!

Thanks

[fth0]

Please verify that /usr, /usr/lib and /usr/lib/virtualbox are owned by user root and group root. If this is the case, execute strace -tt -f -o strace.txt VBoxManage list vms and provide the (zipped) strace.txt file.

[denk]

Thank you very much for looking into this!

Permissions:
/usr drwxr-xr-x 11 root root 4096 23. Apr 18:48 usr
/usr/lib drwxr-xr-x 316 root root 348160 23. Apr 18:45 lib
/usr/lib/virtualbox drwxr-xr-x 5 root root 4096 23. Apr 18:45 virtualbox

Please find attached the strace.txt file from VirtualBox 6.1.34.

[fth0]

It looks like VBoxManage removes the /tmp/.vbox-<username>-ipc folder but /usr/lib/virtualbox/VBoxXPCOMIPCD is still running, which is an unexpected combination.

Please uninstall all VirtualBox packages (the VMs will be kept), reboot the host, remove all /tmp/.vbox-<username>-ipc folders, install the VirtualBox 6.1.34 package and reboot the host to ensure that no VirtualBox component is running. Then execute strace -tt -f -o strace.txt VBoxManage list vms and provide the (zipped) strace.txt file.

[denk]

Done as described, still the same error.
Please find attached the new strace file.

[fth0]

Ok, the new strace log looks like the previous one. This means that something prevents VBoxManage from starting /usr/lib/virtualbox/VBoxXPCOMIPCD as a detached process.

Please show a detailed directory listing of /usr/lib/virtualbox (e.g. ls -hal /usr/lib/virtualbox). Check if a VBoxXPCOMIPCD process is already running after rebooting the host and after trying the VBoxManage command (e.g. ps -elfH | grep -i box).

[denk]

Output of

Code: Select all

ls -hal /usr/lib/virtualbox

:

Code: Select all

insgesamt 133M
drwxr-xr-x   5 root root 4,0K 25. Apr 08:31 .
drwxr-xr-x 316 root root 340K 25. Apr 08:31 ..
drwxr-xr-x   2 root root 4,0K 25. Apr 08:31 additions
drwxr-xr-x   2 root root 4,0K 25. Apr 08:31 components
-rwxr-xr-x   1 root root 442K 21. Apr 22:04 DbgPlugInDiggers.so
drwxr-xr-x   2 root root 4,0K 21. Apr 22:04 ExtensionPacks
-rwxr-xr-x   1 root root 131K 21. Apr 22:04 libvboxjxpcom.so
-rwxr-xr-x   1 root root  36M 21. Apr 22:04 UICommon.so
-rwxr-xr-x   1 root root  38K 21. Apr 22:04 VBoxAuthSimple.so
-rwxr-xr-x   1 root root  14K 21. Apr 22:04 VBoxAuth.so
-rwxr-xr-x   1 root root 175K 21. Apr 22:04 VBoxBalloonCtrl
-rwxr-xr-x   1 root root 184K 21. Apr 22:04 VBoxDbg.so
-rwxr-xr-x   1 root root 8,4M 21. Apr 22:04 VBoxDD2.so
-rw-r--r--   1 root root 239K 21. Apr 22:04 VBoxDDR0.r0
-rwxr-xr-x   1 root root 2,2M 21. Apr 22:04 VBoxDD.so
-rwxr-xr-x   1 root root 435K 21. Apr 22:04 VBoxDDU.so
-rwxr-xr-x   1 root root  38K 21. Apr 22:04 VBoxDragAndDropSvc.so
-rw-r--r--   1 root root 4,0M 21. Apr 22:04 VBoxEFI32.fd
-rw-r--r--   1 root root 4,0M 21. Apr 22:04 VBoxEFI64.fd
-rwxr-xr-x   1 root root  63K 21. Apr 22:04 VBoxExtPackHelperApp
-rwxr-xr-x   1 root root  34K 21. Apr 22:04 VBoxGuestControlSvc.so
-rwxr-xr-x   1 root root  42K 21. Apr 22:04 VBoxGuestPropSvc.so
-rwsr-xr-x   1 root root 163K 21. Apr 22:04 VBoxHeadless
-rwxr-xr-x   1 root root 118K 21. Apr 22:04 VBoxHeadless.so
-rwxr-xr-x   1 root root  18K 21. Apr 22:04 VBoxHostChannel.so
-rwxr-xr-x   1 root root  77K 21. Apr 22:04 VBoxKeyboard.so
-rwxr-xr-x   1 root root 1,4M 21. Apr 22:04 VBoxManage
-rwsr-xr-x   1 root root  31K 21. Apr 22:04 VBoxNetAdpCtl
-rwsr-xr-x   1 root root 163K 21. Apr 22:04 VBoxNetDHCP
-rwxr-xr-x   1 root root 258K 21. Apr 22:04 VBoxNetDHCP.so
-rwsr-xr-x   1 root root 163K 21. Apr 22:04 VBoxNetNAT
-rwxr-xr-x   1 root root 307K 21. Apr 22:04 VBoxNetNAT.so
-rwxr-xr-x   1 root root 209K 21. Apr 22:04 VBoxPython3_10.so
-rwxr-xr-x   1 root root 209K 21. Apr 22:04 VBoxPython.so
-rwxr-xr-x   1 root root 3,4M 21. Apr 22:04 VBoxRT.so
-rwsr-xr-x   1 root root 163K 21. Apr 22:04 VBoxSDL
-rwxr-xr-x   1 root root 186K 21. Apr 22:04 VBoxSDL.so
-rwxr-xr-x   1 root root  62K 21. Apr 22:04 VBoxSharedClipboard.so
-rwxr-xr-x   1 root root  66K 21. Apr 22:04 VBoxSharedFolders.so
-rwxr-xr-x   1 root root 7,6M 21. Apr 22:04 VBoxSVC
-rwxr-xr-x   1 root root 243K 21. Apr 22:04 VBoxSVGA3D.so
-rwxr-xr-x   1 root root  63K 21. Apr 22:04 VBoxTestOGL
-rwxr-xr-x   1 root root  14K 21. Apr 22:04 VBoxVMMPreload.so
-rwxr-xr-x   1 root root 4,1M 21. Apr 22:04 VBoxVMM.so
-rwxr-xr-x   1 root root  29M 21. Apr 22:04 vboxwebsrv
-rwxr-xr-x   1 root root  50K 21. Apr 22:04 VBoxXPCOMC.so
-rwxr-xr-x   1 root root  31K 21. Apr 22:04 VBoxXPCOMIPCD
-rwxr-xr-x   1 root root 1,1M 21. Apr 22:04 VBoxXPCOM.so
-rwxr-xr-x   1 root root 2,5M 21. Apr 22:04 VirtualBox
-rwsr-xr-x   1 root root 163K 21. Apr 22:04 VirtualBoxVM
-rwxr-xr-x   1 root root 1,8M 21. Apr 22:04 VirtualBoxVM.so
-rw-r--r--   1 root root 1,9M 21. Apr 22:04 VMMR0.r0
-rwxr-xr-x   1 root root  23M 21. Apr 22:04 webtest

Output of

Code: Select all

ps -elfH | grep -i box

after running

Code: Select all

VBoxManage list vms

:

Code: Select all

0 S root       17612    1992  0  80   0 -  1833 pipe_r 08:34 pts/1    00:00:00                   grep -i box
0 S dkadiog+    1200    1058  0  80   0 - 317333 do_sys 08:20 ?       00:00:00     /usr/bin/akonadi_unifiedmailbox_agent --identifier akonadi_unifiedmailbox_agent

[fth0]

Ok, your latest checks didn't exhibit anything unexpected to me. IMHO the key is to find something preventing VBoxManage from starting /usr/lib/virtualbox/VBoxXPCOMIPCD as a detached process.

I took a look at the VirtualBox source code changes between 6.1.30 and 6.1.32 in the area of process creation, and there were several topics involved: UTF8, locales, environment variables, and PAM. Since only you and another user have reported this issue, I think it's fair to assume that your hosts must have something configured differently than for the majority of VirtualBox users. Does something ring a bell perhaps?

[denk]

Hmm, that's something I have to think about - spontaneously nothing comes to my mind.

However, I just found out, that if I manually start /usr/lib/virtualbox/VBoxXPCOMIPCD and afterwards /usr/lib/virtualbox/VBoxSVC, I can successfully run VBoxManage list vms, without errors. VBox GUI works also. However, I didn't try to start a VM, as I am unsure, if it would be safe with manually starting those two services.
Does that info help maybe to narrow it down a bit?

I know, that in the end it might be something with my system and that's why i'm even more grateful for your troubleshooting support!

[fth0]

It's ok to do that as a workaround. Can you please try if only starting /usr/lib/virtualbox/VBoxSVC manually after a host reboot suffices? Can you also provide an strace log from a working VBoxManage run?

PS: I triggered the VirtualBox development to also have a look, but I cannot promise any timeframe.