Am new to openstack and as of now I have got my openstack setup done in one of Ubuntu:14.04 VM. Creating network and launching a new instance all is going well and on track. But the problem is am not able start any of the instances.
Whenever I try to start an instance an error pops up saying
ERROR:YOU ARE NOT ALLOWED TO START THE INSTANCE
Make sure that you are logged in as the user that has admin role in that project.
As a start login with your admin user and select the admin project from the dropdown menu in the top panel. Try creating an instance from the Compute tab.
Related
for a project on which I work, we would like an admin user to be added to the database at the start of the first deployment automatically because for the moment it is done manually. if you have tips please share them with me
just installed the newest version 2.1.17 of Realm Object Server. Got it running on the IP I want it, got Realm Studio working and running, but no matter what config I set on the server, the default admin 'realm-admin' user always comes back after deleting it (this is after I restart my pm2 instance).
Also, can't seem to figure out how to give it a new password if deleting the user permanently is not an option. Because right now it's just open to the world. I don't want those values to go back to default when pm2 is restarted or the box is rebooted. Any help out there with this issue would be greatly appreciated. Thanks
You would need to keep the realm-admin user (or some other user with admin privilege) if you want to administer your Realm Object Server.
Changing password should fairly straight forward:
1. Connect to ROS
2. Go to the "Users" tab
3. Select the "realm-admin" user
4. Click the "Change password" button.
I'm pretty new to using amazon web services. I created a new launch instance using WordPress powered by Bitnami and made sure to create a key pair. The key pair I made shows up under the "Key Pair" category however it is not linked to my launch instance. How do I fix this without losing any of the content that's on my current Wordpress site? I want to access the instance through my terminal, however I need the key pair for authentication. Thank you!
It appears that your situation is:
Your EC2 instance with WordPress is operating fine
You did not associate a Keypair with the instance when it was first launched
Therefore you cannot login to the instance
To fix this, you will need to copy a keypair onto the boot volume. This can be done by accessing it via another computer (where you can login).
The basic steps are:
Launch another EC2 instance ("Debug instance")
Stop your WordPress instance
Detach the boot volume of the WordPress instance ("WordPress volume")
Attach the WordPress volume to the Debug instance
Login to the Debug instance, access the WordPress volume and copy a new keypair to /home/ec2-user/.ssh/authorized_keys (If you're not sure what to copy, copy the file from the same location in the Debug instance.)
Unmount and detach the WordPress volume from the Debug instance
Attach the WordPress volume to the WordPress Instance (as /dev/xvda)
Boot the WordPress volume and try to login
Terminate the Debug instance
A similar concept is documented here:
How to Recover an Unreachable Linux Instance
Lost my key with linux authorized_Keys. Now unable to login into the linux
We recently have an issue when importing users through the user import wizard.
As soon as we active the tab where you can specifiy the domain, we receive an error stating that the axaptaUserManager object is null.
On the form, this is the line where the userManager is instantiated but the result is null.
mgr = new AxaptaUserManager();
I could already point out that it is probably something with the machine itself, because it only happens on the sharepoint machine where the portal should be installed. Also the portal installer log shows the same error.
Anyone who has any idea?
Try to do this with a user with administrative rights in the Active Directory Domain you work in.
I have usually got problems with user creation (specifically, activating them) when I try to do so with a user with no administrative rights in Domain.
PurchReqApproval workflow stopped working, that is all the workflow's messages are in pending state. There were no modifications made to objects related to that workflow (maybe except EDTs).
I am thinking this issue might be consequence of changing server admin password. Any hints how and where can I check/fix outdated password in IIS/AX/Services?
Go to your IIS manager and then click on application pools. Find the relevant one and right click on it and do advanced settings, then look at its identity (username) and click the ellipse .... Try setting the password again and recycling the app pool and/or doing an iisreset.