VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
19 Replies Last post: May 5, 2009 8:16 AM by c_shanklin   1 2 Previous Next

RuntimeFault: Database temporarily unavailable or has network problems. posted: Sep 29, 2008 10:40 PM

Click to view c0l2e's profile Lurker 1 posts since
Sep 29, 2008

RuntimeFault: Database temporarily unavailable or has network problems.

I always received that message when creating new Administrator from local users in Linux or

adding user permission on a specific Virtual Machine.

how can I fix this??

http://communities.vmware.com/servlet/JiveServlet/downloadImage/3955/snapshot23.png

Click to view Constan's profile Lurker 2 posts since
Aug 11, 2008
I have the same problem. I hope it am soon repaired.
Click to view JWDenecamp's profile Lurker 2 posts since
Oct 7, 2008
It would be great if someone at VMWare would reply to this and tell the public if there is a fix coming or not.
Click to view drossgatech's profile Lurker 1 posts since
Oct 7, 2008
I dont know what the offical patch will be but here is a workaround I found translating a German document I found.

/etc/init.d/vmware-mgmt stop


vi /etc/vmware/hostd/authorization.xml


edit the line that talks about


<NextAceId>11</NextAceId>


incrament it past the current "root" or administrator account you have.

so it now reads

<NextAceId>12</NextAceId>

I also deleted


<NextRoleId>11</NextRoleId>


doesnt seem to be used anywhere


I then


/etc/init.d/vmware-mgmt start


and relogged in.


I was then able to add users. Looks like the initial script doesnt incrament well and keeps trying to add you to an existing userid. I dunno why they didnt just use the userid for the users in /etc/password or ldap.


hope that helps

Click to view Constan's profile Lurker 2 posts since
Aug 11, 2008
I already found that, however the server falls then with me.
Click to view JWDenecamp's profile Lurker 2 posts since
Oct 7, 2008
This worked great! Thanks for the help. I used a different Admin so I had to specify the UID for the user I created to be the admin. Very easy fix.
Click to view jfoo's profile Lurker 1 posts since
Oct 8, 2008
Same problem here. Same fix. Thanks.
Click to view mattrich's profile Expert 510 posts since
Nov 29, 2006
Shouldn't this be in the Server 2.0 discussion, and not the VIX API discussion?
Click to view barnys's profile Enthusiast 108 posts since
Oct 29, 2006

what difference does it make where it is being posted as long as it provides a viable solution?

FYI folks - I tried this out and it worked on my setup. Thanks for sharing.

Click to view ctgrubbs's profile Lurker 1 posts since
Oct 11, 2008
My thanks as well...worked perfectly
Click to view gervaisb's profile Lurker 4 posts since
Sep 19, 2008
I have got the same problem. VUt this was just a missing access right to the vmware files.
Click to view MaskedMarauder's profile Lurker 1 posts since
Dec 4, 2007
Worked perfectly. THANK YOU!
Click to view slabadmin's profile Lurker 1 posts since
Nov 13, 2008

The posted fix that seems to have helped everyone else did not work for me. What worked for me was the following:

My setup is CentOS 5.2, VMware Server 2.0.

On initial config using vmware-config.pl, I specified a user other than root as the administrative user. That user was then unable to add permissions. I ran vmware-config.pl again and specified a different uesr as teh administrative user to no avail. That user could not add permissions. I then ran vmware-config.pl again and specified root as the administrative user. I was then able to login as root through the Web UI and add permissions. It was an unfortunate fix, as I would prefer not to have the root account directly accessible from any remote interface. As such, I then logged in as one of the newly added administrators and removed root's permissions, which prevented root from logging in.

Keep your heels low and center your gravity.

Click to view rokla's profile Lurker 1 posts since
Nov 19, 2008

In linux systems the problem is, that vmware-config create the folder /etc/vmware/hostd for user and group root. if you chose another user as administrator for your vmware-enviroment, you won't be able to write into this file, but you need to do, if you want to change and/or add permissions for virtual machines. so the workaround, which works for me and which is still secure, is to give the files in /etc/vmware/hostd group-rights to your administrator-user and allow write-right to the group, e.g. if your administrator-user is "admin" then you should have a group called "admin" (in debian-system this is standard), which one and only member is the user "admin"and change permissions as follows

chgrp admin /etc/vmware/hostd/*

chmod g+w /etc/vmware/hostd/*

Actually you dont need to change permissions for all files, but I'm to lazy to find out, which files will be affected and I want to prevent future permission problems, so I change permissions for the whole directory.

Click to view StuartRothrock's profile Novice 18 posts since
Dec 20, 2004

Both entries are used in my authorization.xml

I don't think I will ever approach 100 Roles (AceId) so this is what I used.

<NextAceId>12</NextAceId>
<NextRoleId>111</NextRoleId>

As roles are added, they have low numbers and as members are added, they get the high numbers.
I think their terms are not applied correctly.

Cheers!

Developer Social Media

Communities