![ERROR root@test03:~# dmesg | tail
root@test03:~# sudo mount build:/nfs/vm-share /mnt/vm-share
[ 59.870014] br1: no IPv6 routers present
[ 117.912115] virbr0: starting userspace STP failed, starting kernel STP
mount: wrong fs type, bad option, bad superblock on build:/nfs/vm-share,
[ 118.431061] ip_tables: (C) 2000-2006 Netfilter Core Team
missing codepage or helper program, or other error
[ 118.722212] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
(for several filesystems (e.g. nfs, cifs) you might
[ 118.722488] CONFIG_NF_CT_ACCT is deprecated and will be removed
need a /sbin/mount.<type> helper program) soon.
In some cases useful info is found in syslog - try
[ 118.722491] nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack
dmesg | tail or so
[ 118.722493] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 128.760016] virbr0: no IPv6 routers present
[ 1887.185865] RPC: Registered udp transport module.
[ 1887.185869] RPC: Registered tcp transport module.
SOLUTION
sudo apt-get install nfs-common
sudo mount build:/nfs/vm-share /mnt/vm-share
test02@test02:~$ sudo mount build:/nfs/vm-share /mnt/vm-share
mount.nfs: mount point /mnt/vm-share does not exist
martes 17 de agosto de 2010](https://image.slidesharecdn.com/troubleshootingvmspresen-100817075143-phpapp01/85/Troubleshooting-vm-s-presen-2-320.jpg)
![ERROR
•./run.sh
The system halt the jboss automatically
09:52:47,232 INFO [Server] Runtime shutdown hook called, forceHalt: true
09:52:47,233 INFO [Server] JBoss SHUTDOWN: Undeploying all packages
09:52:47,251 INFO [Server] Shutdown complete
Shutdown complete
Halting VM
SOLUTION:
check the following:
So I tried a somewhat hack-ish solution : the /etc/hosts file. It's been a while since I
edit one of these. Anyway the hack was to add the name of the identity which JBoss
If the permission of boot.log in /server/default/log are for test, you can
said it can't refer to, meaning if JBoss' log says the following :
see the permission with the command ls -al, if the permission are for
root change this with sudo chown test:test log
sudo vi /etc/hosts
edit the file and save:
If the problems continuing, make the same but for all the files of jboss:
127.0.0.1 localhost jboss_ctrl localhost.localdomain localhost4 localhost4.lo$
sudo chown -R test:test jboss-4.2.3
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
Try if this work....
martes 17 de agosto de 2010](https://image.slidesharecdn.com/troubleshootingvmspresen-100817075143-phpapp01/85/Troubleshooting-vm-s-presen-4-320.jpg)
Troubleshooting vm's presen
- 1. Troubleshooting vm’s How to resolve some problems during the installation of virtual machines martes 17 de agosto de 2010
- 2. ERROR root@test03:~# dmesg | tail root@test03:~# sudo mount build:/nfs/vm-share /mnt/vm-share [ 59.870014] br1: no IPv6 routers present [ 117.912115] virbr0: starting userspace STP failed, starting kernel STP mount: wrong fs type, bad option, bad superblock on build:/nfs/vm-share, [ 118.431061] ip_tables: (C) 2000-2006 Netfilter Core Team missing codepage or helper program, or other error [ 118.722212] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) (for several filesystems (e.g. nfs, cifs) you might [ 118.722488] CONFIG_NF_CT_ACCT is deprecated and will be removed need a /sbin/mount.<type> helper program) soon. In some cases useful info is found in syslog - try [ 118.722491] nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack dmesg | tail or so [ 118.722493] sysctl net.netfilter.nf_conntrack_acct=1 to enable it. [ 128.760016] virbr0: no IPv6 routers present [ 1887.185865] RPC: Registered udp transport module. [ 1887.185869] RPC: Registered tcp transport module. SOLUTION sudo apt-get install nfs-common sudo mount build:/nfs/vm-share /mnt/vm-share test02@test02:~$ sudo mount build:/nfs/vm-share /mnt/vm-share mount.nfs: mount point /mnt/vm-share does not exist martes 17 de agosto de 2010
- 3. ERROR virsh start jboss_ctrl02 Connecting to uri: qemu:///system error: Failed to start domain jboss_ctrl error: internal error unable to start guest: qemu: could not open disk image /dev/test03/jboss_boot SOLUTION: Change the name the file, jboss_ctrl----->jboss_ctrl02, the name the file should be different that the name of the boot controller. martes 17 de agosto de 2010
- 4. ERROR •./run.sh The system halt the jboss automatically 09:52:47,232 INFO [Server] Runtime shutdown hook called, forceHalt: true 09:52:47,233 INFO [Server] JBoss SHUTDOWN: Undeploying all packages 09:52:47,251 INFO [Server] Shutdown complete Shutdown complete Halting VM SOLUTION: check the following: So I tried a somewhat hack-ish solution : the /etc/hosts file. It's been a while since I edit one of these. Anyway the hack was to add the name of the identity which JBoss If the permission of boot.log in /server/default/log are for test, you can said it can't refer to, meaning if JBoss' log says the following : see the permission with the command ls -al, if the permission are for root change this with sudo chown test:test log sudo vi /etc/hosts edit the file and save: If the problems continuing, make the same but for all the files of jboss: 127.0.0.1 localhost jboss_ctrl localhost.localdomain localhost4 localhost4.lo$ sudo chown -R test:test jboss-4.2.3 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 Try if this work.... martes 17 de agosto de 2010
- 5. ERROR: •The ip for the three nodes are the same. This is because the mac address are the same...because you copy the file from the same *.xml file, then you edit the file....and define....you should be to do the changes and the definition one to one. SOLUTION: test02@test02:~$ sudo virsh list --all check the following: Connecting to uri: qemu:///system Go to each file to check if the mac are the same for the three nodes, in the Id Name State label <interface type='network'>: ---------------------------------- 1 jboss_ctrl02 running test02@test02:~$ sudo virsh edit jboss_ctrl02 2 jboss_node1 running test02@test02:~$ sudo virsh edit jboss_node1 - jboss_node2 shut off test02@test02:~$ sudo virsh edit jboss_node2 - jboss_node3 shut off test02@test02:~$ sudo virsh edit jboss_node3 where you delete de ip, and start again. If the mac is the same, delete this label, <interface type='network'>, shutdown the nodes: test02@test02:~$ sudo virsh start jboss_node3 test02@test02:~$ sudo virsh shutdown jboss_node2 Connecting to uri: qemu:///system Connecting to uri: qemu:///system Domain jboss_node3 started Domain jboss_node2 is being shutdown test02@test02:~$ sudo virsh start jboss_node2 test02@test02:~$ sudo virsh shutdown jboss_node3 Connecting to uri: qemu:///system Connecting to uri: qemu:///system Domain jboss_node2 started Domain jboss_node3 is being shutdown martes 17 de agosto de 2010
- 6. ERROR Jboss don't start properly, have a error in the starting of the webserver SOLUTION sudo vim /etc/hosts and insert this line in the file 127.0.0.1 localhost.localdomain localhost test02 jboss_ctrl Running jboss in cluster mode on node = ./run.sh -c all -b ip adress of node ./run.sh -c all -b 192.168.122.104 martes 17 de agosto de 2010
- 7. ERROR error: Failed to start network network_4 error: internal error network is already active SOLUTION: This occur because we don't copy the file in autostart, or not restart the library. martes 17 de agosto de 2010
- 8. ERROR •When you go check in the navigator the loop with the nodes http://10.2.0.62/testservlet/test the looping no is correct the web give you a error and the screen report you a error with the server. The problem is that one of the files don't have permissions to read for one of the nodes. SOLUTION Give permissions to this files; in the nodes check the files a do the following: •To see the version of java that we have java -version •To check the permissions of the files cd jboss-4.2.3.GA ls -al •Change the permissions to the files inside the directory of Jboss chown -R test:test * Then run again the jboss in the nodos, and check if the looping run well. martes 17 de agosto de 2010
- 9. •ERROR •When I try connect the navigator to the http://10.2.0.62 (the public ip of the controller) to see the looping of the nodes, give me a error, “service temporally unavailable” SOLUTION: To see if the file is inside, go to the console for the node and use to swich off the firewall, make in a off state permanently sudo /etc/init.d/iptables stop To check the configuration of the firewall: sudo /etc/init.d/iptables status martes 17 de agosto de 2010
- 10. ERROR •When I try connect the navigator to the http://10.2.0.62 (the public ip of the controller) and don't connect to the main page of jboss SOLUTION: We need restart apache, because is possible we make some changes, for example in workerspropeties. sudo /etc/init.d/httpd restar To check the configuration of apache: sudo /etc/init.d/httpd status martes 17 de agosto de 2010