List of Errors
Here you will find a list of typical error messages and faults that could appear while you're trying to install or tu use VNUML.
If you notice an error message that is not listed below, please send me an e-mail message: avolk@uni-koblenz.de
Some error messages were already described in the following document.
Message Text:
main::configure_virtual_bridged_networks (775): module tun can not be initialized: Datei oder Verzeichnis nicht gefunden
Time of appearance :
Start of vnumlparser.pl
Possible cause:
Recent Kernel-Update, e.g. with Yast Online Update
The path to "modules.dep" is no longer correct.
Work-Around:
- Login as root with "su".
- Type "cd /lib/modules"
- Type "ls"
- Supposedly the directory "2.6.13-15.8-default" (or similar) exists.
- Create a symbolic link to this directory with the name of the expected directory in the error message:
"ln -s existent_directory direcory_in_errormessage"
e.g.: "ln -s 2.6.13-15.8-default 2.6.13-15-default"
Message Text :
524 (/root/.ssh/identity.pub is not a valid file (perhaps does not exist)
Time of appearance :
Start of vnumlparser.pl
Solution:
"ssh-keygen -t rsa1"
Enter file in which to save the key (/root/.ssh/identity): [Enter]
Enter passphrase... [Enter]
Problem:
SSH prompts for a password while logging into a virtual machine.
Time of Appearance :
The VNUML scenario is started correctly. During the login via SSH, yo're prompted for a password.
Cause:
SSH uses different modes for the authentiation.
Solution1:
Password for the Filesystem (usually): xxxx
Solution2:
Start SSH in Authentication Mode 1:
"ssh -1 name-of-virtual-machine"
Problem:
The VNUML scenario started correctly,
you can log into the virtual machines via SSH,
but you can't ping any other virtual machine from there.
Cause:
The Linux firewall (especially when you're using SuSE) blocks all connections between the virtual machines.
Solution1:
Deactivate the Linux Firewall (in SuSE Linux under YAST!) - but be sure to enable it after your work with VNUML!
Solution2:
Insert the parameter mode=’uml switch’ in the <net> -tags of the XML scenario file.
(resp. change an eventually existing parameter mode=’virtual bridge’
to mode=’uml switch’ )
