Authentication Token Manipulation Error

if u are running shadowed passwords it might be theres no entry for this user. make a backup of /etc/shadow, delete /etc/shadow and convert /etc/passwd using pwconvert.same goes for /etc/groups.

via Authentication Token Manipulation Error.

I got this error when logging in as root into a system that I think was badly installed (by me).  Anyway, this fixed that problem.  I found it interesting that this came up #1 on the google search and it’s an entry dated May 2001.

Note: The linux command pwconv replaced pwconvert sometime during these last ten years.

Note2:  Here’s a more modern (3 years old) explanation tmhat I found useful.

Note3: I still had to do a complete reinstall since a lot of things went haywire.  I probably shouldn’t have been playing with hot swapping while the install was in progress.

Update:I don’t think the kernel likes this motherboard.  Second install failed.  Have to resort to compiling a kernel by hand.  What started out as a simple hour long task will now take all night.

ERROR 1130 (HY000): Host ‘hostname’ is not allowed to connect to this MySQL server

After a bit of research, the fix in my case was to “GRANT” user root to connect to MySQL on any hosts. By default, user “root” was only allowed to connect to localhost and 127.0.0.1 hosts of MySQL.

#GRANT ALL PRIVILEGES ON *.* TO ‘root’@’%’ IDENTIFIED BY ‘<roots-password>’ WITH GRANT OPTION;

via ERROR 1130 (HY000): Host ‘hostname’ is not allowed to connect to this MySQL server – kuber’s posterous.

How to clone virtual machines in VMware ESXi

This is the tricky step. Unlike VMware Server, the Infrastructure Client does not have the File > Open option, allowing you to browse for existing .vmx configuration files and registering them. So it seems you might be stuck.

The answer lies in the datastore. In the destination folder, where you have just created your clone, right-click on the .vmx configuration file. Select Add to Inventory.

via How to clone virtual machines in VMware ESXi.

Update:  This indeed worked.  The problem occurs in that if a .vmx file is copied directly from Workstation, it can contain erroneous info that can cause problems.  In my case eth0 would not pass traffic.  I noticed something wrong by examining the virtual machines on Configuration -> Networking when the esxi box is selected.  I noticed the vm I was having problems with wasn’t listed so I thought to examine the .vmx file.

The copied over .vmx file had ethernet0.vnet=”/dev/vmnet0″ which is a Workstation reference that doesn’t apply to esxi.  By eliminating this and adding ethernet0.networkName = “VM Network” networking worked.

 

VMware KB: VMware VirtualCenter Server service does not start automatically after reboot

This issue may occur if the VirtualCenter Server service starts before one of the services it depends on is started. The VirtualCenter Server service is dependent on the following services: SQL Services ADAM Services when using linked mode in vCenter Server 4.x To resolve this issue, add a dependency to the VirtualCenter service so that it starts only after the necessary services have started.

via VMware KB: VMware VirtualCenter Server service does not start automatically after reboot.

Yikes!  You need to edit the registry to get this to work.

Device eth0 does not seem to be present error after cloning a linux machine

After some searching, i found out that there is a device manager for the Linux kernel named “udev” which remembers the settings from the NIC of the virtual machine before it was cloned. To fix the issue simply delete the the following file and it will be regenerated properly on reboot.

/etc/udev/rules.d/70-persistent-net.rules

via Random IT Stuff » ‘Device eth0 does not seem to be present’ error after cloning a linux machine.

This worked for me with a VirtualBox clone that was giving me problems.  Google is simply an amazing resource!  And kudos to the linked site for coming up first with a no nonsense answer.

How To Mount a Linux LVM Partition in a XenServer Host

This article describes how to mount a Linux Logical Volume Manager (LVM) partition located inside a virtual disk (VDI) in a XenServer Host.

via CTX117791 – How To Mount a Linux LVM Partition in a XenServer Host – Citrix Knowledge Center.

Finally!!!!

I have never been a fan of logical volume management which seems to be a Red Hat thing.  It completely complicates matters when mounting drives.  XenServer, which is based off centos (I think) is littered with LVMs as the result of performing the above procedure will attest.  I hope Citrix had a good reason for doing this.