I am working on Ubuntu 12.04 .Recently I downloaded Hadoop 2.0.3 and made a user named Hduser which I added and give privileged rights. Now I want to delete the user.
I used
sudo deluser hduser
But it's giving me the following error:
Warning: group hadoop' has no more members. userdel: user hduser is
currently logged in /usr/sbin/deluser:/usr/sbin/userdel hduser'
returned error code 8. Exiting
Try logging in as root or any other user before executing the above. And make sure HDFS is down.
i had these errors too on Ubuntu 12.04 but I tried it on WEBMIN and successfully deleted the user.
Related
I'm a student working on a test cluster, consisting of around 25 hosts. We installed using Ambari and have FreeIpa running on a host as a dns and ldap server. The rest are typical Hadoop
infrastructure. Hive was failing and I wondered whether the db connection parameters used during the Ambari installation were incorrect and I tried to find a way to re-run the db connection process. I didn't get anywhere and it was late so I left it, ambari interface working.
Next morning, ambari webUI seems to be down. I thought that maybe the webserver needed restarted so I tried the following:
[akidd#dw ~]$ sudo ambari-server start
Using python /usr/bin/python
Starting ambari-server
ERROR: Exiting with exit code 1.
REASON: Unable to detect a system user for Ambari Server.
- If this is a new setup, then run the "ambari-server setup" command to create the user
- If this is an upgrade of an existing setup, run the "ambari-server upgrade" command.
Refer to the Ambari documentation for more information on setup and upgrade.
Can anyone help me to understand what could have happened?
If I run ambari-server setup will the existing cluster be ok assuming I create everything like for like with how it was originally?
Thanks for your help!
#user3535074 You should try to start it with the user that installed it.
If you do run ambari-server setup as current user, remember to choose No the following options:
Customize user account for ambari-server daemon [y/n] (n)? n
Do you want to change Oracle JDK [y/n] (n)? n
Enter advanced database configuration [y/n] (n)? n
More info on the following post, including how to backup ambari database before running setup again:
https://community.cloudera.com/t5/Support-Questions/Ambari-server-failed-to-start-after-system-reboot-Below-is/td-p/203806
I'm using vagrant for many projects.
The web-service and php-service is running with the user vagrant(uid:1000). I'm using OS X with nfs to sync my shared-folder with vagrant. At the guest-system all files get my OS X user-id as owner.
So I want to update the vagrant user to the uid 501. But if I use usermod -u 501 vagrant I get an error because the user is used by a process.
I hope that someone can help me.
I get the error during cloudera 5 installation on my ec2 redhat 7 system cluster ...
during the installation of cloudera the installation is interrupted and I get the message
Cluster Installation
Installation failed on all hosts.
0 of 1 host(s) completed successfully.
Uninstalled on 1 host(s) after installation failure.
Retry | Details
Installation failed. Failed to copy installation files.
Failed to copy installation files. (Current Step)
Please login as the user "ec2-user" rather than the user "root".
I have got no idea how to fix it and I can not find information on the web on this issue...
What a stupid mistake. When I chose the options in the beginning, it asked what user to choose for installation. I mistakenly chose the default "root". As soon as you change the user to "ec2-user" the installation works fine.
I'm new in Windows. I use Windows 10. While I run vagrant on my machine, there are some issues with UID. Please look at the picture for more information.
While I run vagrant up, I get some warning :
The VirtualBox VM was created with a user that doesn't match the
current user running Vagrant. VirtualBox requires that the same user
be used to manage the VM that as created. Please re-run Vagrant with
that user. This is not a Vagrant issue.
The UID used to create the VM was: 1000
Your UID is: 0
Looks like you are logged in as sudo, hence the UID is different. Log-out of sudo and try vagrant up as normal user.
If the above doesn't work then update the below file
vi .vagrant/machines/default/virtualbox/creator_uid
to add 0 in it
Let me know if this helps.
Find this path and change to 0.
.vagrant/machines/default/virtualbox/creator_uid
In the Windows folder. Vagrant is in the same folder as the Vagrantfile.
As default won't be available, so you may have to edit in every vm but the path is the same: vagrant/machines/(name of the vm)/virtualbox/creator_uid
Remove .vagrant dir in the current working dir and re-run vagrant up command.
Error, because of copy / backup of Vagranfile /s from one system to another system. user id's mismath to the Vagrant to bring up the environment..
hope it helps cheers..!! :))
This happened to me (on subsequent runs) when I used vagrant up with elevated privileges for the first time (administrator).
I'm having trouble installing Chef Sever (12.0.3) on my Centos 6.4 virtual machine. Whenever I install Chef Server and reconfigure with these commands, the /etc/chef-server does not get created:
rpm -ivh chef-server-core-12.0.1-1.x86_64.rpm
chef-server-ctl reconfigure
This is a problem because all of the .pem files for authentication do not get created as well. Has anyone ran into this issue? I've searched, but I haven't found anyone with this same issue so far. Any help is appreciated.
Jotun,
I think you may be needing the *.pem files and hence searching for chef-server directory.
Chef 12 does not create the chef-server directory and that is because there is no default user (admin incase of chef 11) in chef 12. So you have to exclusively create the user using the below command:
chef-server-ctl user-create any_user_name your_first_name your_last_name email password --filename FILE_NAME
this will create a user with admin rights and the FILENAME should be the path where the admin.pem will be created.
In the same way for org creation,
chef-server-ctl org-create org_short_name org_full_name --association_user admin --filename FILENAME
this will create a organization associated with the admin user and the FILENAME should be the path where the chef-validator.pem will be created.
You can proceed with the steps that you used in chef 11 and configure the workstation.
I couldn't find the reason this error was happening, but I just destroyed my VM and created a new one. Sorry if you are looking at this in the future and still want to know what was causing this problem.