On Debian based systems like Ubuntu:
# dpkg --list | grep linux-image
To list / display current kernel
Type the following command:
# uname -r
# uname -mrs
On Debian based systems like Ubuntu:
# dpkg --list | grep linux-image
Type the following command:
# uname -r
# uname -mrs
With rpm based OSes
# rpm -qa kernel
This will list the available kernels.
Type the following command:
# uname -r
# uname -mrs
If an instance gets stuck in an intermediate state (e.g., “deleting”), you can manually reset the state of an instance using the nova reset-state command. This will reset it to an error state, which you can then delete. For example:
$ nova reset-state c6bbbf26-b40a-47e7-8d5c-eb17bf65c485
$ nova delete c6bbbf26-b40a-47e7-8d5c-eb17bf65c485
You can also use the --active to force the instance back into an active state instead of an error state, for example:
$ nova reset-state –active c6bbbf26-b40a-47e7-8d5c-eb17bf65c485
![]() |
Note |
|---|---|
The version of the nova client that ships with Essex on most distributions does not support the reset-statecommand. You can download a more recent version of the nova client from PyPI. The package name ispython-novaclient, which can be installed using a Python package tool such as pip. |
The Launchpad Answers site offers a place to ask and answer questions, and you can also mark questions as frequently asked questions.
Credential errors, 401, 403 forbidden errors
A 403 forbidden error is caused by missing credentials. Through current installation methods, there are basically two ways to get the novarc file. The manual method requires getting it from within a project zipfile, and the scripted method just generates novarc out of the project zip file and sources it for you. If you do the manual method through a zip file, then the following novarc alone, you end up losing the creds that are tied to the user you created with nova-manage in the steps before.
When you run nova-api the first time, it generates the certificate authority information, including openssl.cnf. If it gets started out of order, you may not be able to create your zip file. Once your CA information is available, you should be able to go back to nova-manage to create your zipfile.
You may also need to check your proxy settings to see if they are causing problems with the novarc creation.
Instance errors
Sometimes a particular instance shows “pending” or you cannot SSH to it. Sometimes the image itself is the problem. For example, when using flat manager networking, you do not have a dhcp server, and an ami-tiny image doesn’t support interface injection so you cannot connect to it. The fix for this type of problem is to use an Ubuntu image, which should obtain an IP address correctly with FlatManager network settings. To troubleshoot other possible problems with an instance, such as one that stays in a spawning state, first check your instances directory for i-ze0bnh1q dir to make sure it has the following files:
Check the file sizes to see if they are reasonable. If any are missing/zero/very small then nova-compute has somehow not completed download of the images from objectstore.
Also check nova-compute.log for exceptions. Sometimes they don’t show up in the console output.
Next, check the /var/log/libvirt/qemu/i-ze0bnh1q.log file to see if it exists and has any useful error messages in it.
Finally, from the instances/i-ze0bnh1q directory, try virsh create libvirt.xml and see if you get an error there.
LTS is an abbreviation for “Long Term Support”.
We produce a new Ubuntu Desktop and Ubuntu Server release every six months [diagram below]. That means you’ll always have the latest and greatest applications that the open source world has to offer. Ubuntu is designed with security in mind. You get free security updates for at least 18 months on the desktop and server.
A new LTS version is released every 2 years. In previous releases, a Long Term Support (LTS) version had 3 years support on Ubuntu (Desktop) and 5 years on Ubuntu Server. Starting with Ubuntu 12.04 LTS, both versions will receive 5 years support. There is no extra fee for the LTS version; we make our very best work available to everyone on the same free terms. Upgrades to new versions of Ubuntu are and always will be free of charge.
The LTS designation applies only to specific subsets of the Ubuntu archive. The LTS may not apply to all flavors and remixes of Ubuntu. For example, for 8.04 LTS, Kubuntu chose to move to KDE 4.0 and didn’t issue an LTS release. In 10.04, the Netbook Edition was not an LTS. The project will decide which flavors will be LTS and the support duration for each, early in the LTS development cycle.
Some of the latest support windows are illustrated below:
Furthermore, we define the LTS to be:
and clearly state that it is not:
To support our goal of ensuring stability, we plan to make a small number of changes to the release schedule:
Quoted from here.
The log files are located here :
/var/logs/nova
Logfiles are :
nova-api.log
nova-cert.log
nova-compute.log
nova-dhcpbridge.log
nova-manage.log
nova-network.log
nova-objectstore.log
nova-scheduler.log
nova-volume.log
nova-xvpvncproxy.log
The magic spell is :
$sudo apt-get update; sudo apt-get upgrade
kickstart postinstall, you can read how to do this on the internet.
wget http://foo/tools.tar.gz
tar xzvf *.tar.gz
cd directory-where-you-untarred
vmware-tools-install.pl -d
BINGO !
Giggidi Giggidi
While this is a Linux forum this came in REALLY handy so what the heck 🙂
Frustratingly hidden away, windows command for putting the machine into Hibernate and / or standby are hidden away in the api under the powrprof.dll library.
Shutdown %windir%\System32\shutdown.exe -s
Reboot %windir%\System32\shutdown.exe -r
Logoff %windir%\System32\shutdown.exe -l
Standby %windir%\System32\rundll32.exe powrprof.dll,SetSuspendState Standby
Hibernate %windir%\System32\shutdown.exe -h OR
%windir%\System32\rundll32.exe powrprof.dll,SetSuspendState Hibernate
Also if you Windows 7 wakes up and you don’t know why check:
powercfg lastwake
Hope this helps.
Let’s say you have a subnet 192.168.1.0 / 24 and you want to scan all ip’s to see if any hosts are up:
Type the following command, enter:
$ for ip in $(seq 1 254); do ping -c 1 192.168.1.$ip>/dev/null; [ $? -eq 0 ] && echo “192.168.1.$ip UP” || : ; done
Output:
192.168.1.65 UP
192.168.1.66 UP
192.168.1.70 UP
192.168.1.76 UP
192.168.1.253 UP
192.168.1.254 UP