Re: [one-users] VMs not deploying because of datastore error
Hi Ruben, Thank you for your reply. Here it is what I found out: 1- I had a cluster defined but I deleted it, so right now I don't have any. 2- The only host I have at the moment is correctly monitored. And the output of monitor_ds.sh is correctly showing info about the datastore (I cannot run anything else from the script because I don't have root privileges): DS_LOCATION_USED_MB=34417 DS_LOCATION_TOTAL_MB=32802826 DS_LOCATION_FREE_MB=18826318 However OpenNebula is not monitoring datastore 0 as it does with the others. 3- I haven't set DATASTORE_LOCATION. I have a self-contained installation and it should default to $ONE_LOCATION/var/datastores, which resides in a network shared partition. And yes, the datastore is mounted. Regards, Javier On 17/01/14 18:39, Ruben S. Montero wrote: Hi Javier, A couple of ideas: 1.- System DS needs to be associated to a cluster. Sometimes this may cause problems if a host is in a cluster but the cluster hasn't got any system DS. (This seems not to be your problem, but just double checking) 2.- System DS information is gathered through the motorization process. You need to check: 1.- hosts are being monitored, 2.- the monitor message includes information about the DS. You can debug this by executing monitor_ds.sh script at the hosts. Monitor DS is a bash script, at the top you can find out the arguments you need to pass to it 3.- Did you set DATASTORE_LOCATION? Maybe the monitor script is not looking at the right place. (Also could you double check that the datastore is actually mounted?) Hope it helps Ruben On Fri, Jan 17, 2014 at 5:42 PM, Javier javier.alva...@bsc.es mailto:javier.alva...@bsc.es wrote: Hello, After a reboot my VMs started getting stuck in PENDING state. Watching at the log files I noticed that the problem was that the system datastore was not being correctly monitored: onedatastore list ID NAMESIZE AVAIL CLUSTER IMAGES TYPE DS TM 0 system0M - - 0 sys - shared 1 default31.3T 57% -12 img fs shared 2 files 31.3T 57% - 2 fil fs ssh And I was getting the following error: Fri Jan 17 17:32:02 2014 [SCHED][D]: VM 2794: Local Datastore 0 in Host 8 filtered out. Not enough capacity. Now, if I create a new system datastore, it happens the same as with datastore 0. However, creating an image datastore and then changing its type to SYSTEM_DS makes it work fine and VMs start being deployed again using that alternative system datastore. My question is if this is a bug or if I am making some mistake. Thank you, Javier WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer ___ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.OpenNebula.org | rsmont...@opennebula.org mailto:rsmont...@opennebula.org | @OpenNebula WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] VMs not deploying because of datastore error
Have you upgraded to 4.4 from an older version? In previous versions system datastores are not monitored and old probes do not get that information. In this case execute: $ onehost sync It should copy the new ones to the hosts. On Mon, Jan 20, 2014 at 12:09 PM, Javier javier.alva...@bsc.es wrote: Hi Ruben, Thank you for your reply. Here it is what I found out: 1- I had a cluster defined but I deleted it, so right now I don't have any. 2- The only host I have at the moment is correctly monitored. And the output of monitor_ds.sh is correctly showing info about the datastore (I cannot run anything else from the script because I don't have root privileges): DS_LOCATION_USED_MB=34417 DS_LOCATION_TOTAL_MB=32802826 DS_LOCATION_FREE_MB=18826318 However OpenNebula is not monitoring datastore 0 as it does with the others. 3- I haven't set DATASTORE_LOCATION. I have a self-contained installation and it should default to $ONE_LOCATION/var/datastores, which resides in a network shared partition. And yes, the datastore is mounted. Regards, Javier On 17/01/14 18:39, Ruben S. Montero wrote: Hi Javier, A couple of ideas: 1.- System DS needs to be associated to a cluster. Sometimes this may cause problems if a host is in a cluster but the cluster hasn't got any system DS. (This seems not to be your problem, but just double checking) 2.- System DS information is gathered through the motorization process. You need to check: 1.- hosts are being monitored, 2.- the monitor message includes information about the DS. You can debug this by executing monitor_ds.sh script at the hosts. Monitor DS is a bash script, at the top you can find out the arguments you need to pass to it 3.- Did you set DATASTORE_LOCATION? Maybe the monitor script is not looking at the right place. (Also could you double check that the datastore is actually mounted?) Hope it helps Ruben On Fri, Jan 17, 2014 at 5:42 PM, Javier javier.alva...@bsc.es wrote: Hello, After a reboot my VMs started getting stuck in PENDING state. Watching at the log files I noticed that the problem was that the system datastore was not being correctly monitored: onedatastore list ID NAMESIZE AVAIL CLUSTER IMAGES TYPE DS TM 0 system0M - - 0 sys - shared 1 default31.3T 57% -12 img fs shared 2 files 31.3T 57% - 2 fil fs ssh And I was getting the following error: Fri Jan 17 17:32:02 2014 [SCHED][D]: VM 2794: Local Datastore 0 in Host 8 filtered out. Not enough capacity. Now, if I create a new system datastore, it happens the same as with datastore 0. However, creating an image datastore and then changing its type to SYSTEM_DS makes it work fine and VMs start being deployed again using that alternative system datastore. My question is if this is a bug or if I am making some mistake. Thank you, Javier WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Developer OpenNebula - The Open Source Toolkit for Data Center Virtualization www.OpenNebula.org | @OpenNebula | github.com/jfontan ___ Users mailing list
Re: [one-users] VMs not deploying because of datastore error
Hi Javier, Even though I updated to 4.4 after the problem appeared, it looks like 'onehost sync' has solved the issue. Thank you, Javier On 20/01/14 12:25, Javier Fontan wrote: Have you upgraded to 4.4 from an older version? In previous versions system datastores are not monitored and old probes do not get that information. In this case execute: $ onehost sync It should copy the new ones to the hosts. On Mon, Jan 20, 2014 at 12:09 PM, Javier javier.alva...@bsc.es wrote: Hi Ruben, Thank you for your reply. Here it is what I found out: 1- I had a cluster defined but I deleted it, so right now I don't have any. 2- The only host I have at the moment is correctly monitored. And the output of monitor_ds.sh is correctly showing info about the datastore (I cannot run anything else from the script because I don't have root privileges): DS_LOCATION_USED_MB=34417 DS_LOCATION_TOTAL_MB=32802826 DS_LOCATION_FREE_MB=18826318 However OpenNebula is not monitoring datastore 0 as it does with the others. 3- I haven't set DATASTORE_LOCATION. I have a self-contained installation and it should default to $ONE_LOCATION/var/datastores, which resides in a network shared partition. And yes, the datastore is mounted. Regards, Javier On 17/01/14 18:39, Ruben S. Montero wrote: Hi Javier, A couple of ideas: 1.- System DS needs to be associated to a cluster. Sometimes this may cause problems if a host is in a cluster but the cluster hasn't got any system DS. (This seems not to be your problem, but just double checking) 2.- System DS information is gathered through the motorization process. You need to check: 1.- hosts are being monitored, 2.- the monitor message includes information about the DS. You can debug this by executing monitor_ds.sh script at the hosts. Monitor DS is a bash script, at the top you can find out the arguments you need to pass to it 3.- Did you set DATASTORE_LOCATION? Maybe the monitor script is not looking at the right place. (Also could you double check that the datastore is actually mounted?) Hope it helps Ruben On Fri, Jan 17, 2014 at 5:42 PM, Javier javier.alva...@bsc.es wrote: Hello, After a reboot my VMs started getting stuck in PENDING state. Watching at the log files I noticed that the problem was that the system datastore was not being correctly monitored: onedatastore list ID NAMESIZE AVAIL CLUSTER IMAGES TYPE DS TM 0 system0M - - 0 sys - shared 1 default31.3T 57% -12 img fs shared 2 files 31.3T 57% - 2 fil fs ssh And I was getting the following error: Fri Jan 17 17:32:02 2014 [SCHED][D]: VM 2794: Local Datastore 0 in Host 8 filtered out. Not enough capacity. Now, if I create a new system datastore, it happens the same as with datastore 0. However, creating an image datastore and then changing its type to SYSTEM_DS makes it work fine and VMs start being deployed again using that alternative system datastore. My question is if this is a bug or if I am making some mistake. Thank you, Javier WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed
[one-users] VMs not deploying because of datastore error
Hello, After a reboot my VMs started getting stuck in PENDING state. Watching at the log files I noticed that the problem was that the system datastore was not being correctly monitored: onedatastore list ID NAMESIZE AVAIL CLUSTER IMAGES TYPE DS TM 0 system0M - - 0 sys -shared 1 default31.3T 57% -12 img fs shared 2 files 31.3T 57% - 2 fil fs ssh And I was getting the following error: Fri Jan 17 17:32:02 2014 [SCHED][D]: VM 2794: Local Datastore 0 in Host 8 filtered out. Not enough capacity. Now, if I create a new system datastore, it happens the same as with datastore 0. However, creating an image datastore and then changing its type to SYSTEM_DS makes it work fine and VMs start being deployed again using that alternative system datastore. My question is if this is a bug or if I am making some mistake. Thank you, Javier WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] VMs not deploying because of datastore error
Hi Javier, A couple of ideas: 1.- System DS needs to be associated to a cluster. Sometimes this may cause problems if a host is in a cluster but the cluster hasn't got any system DS. (This seems not to be your problem, but just double checking) 2.- System DS information is gathered through the motorization process. You need to check: 1.- hosts are being monitored, 2.- the monitor message includes information about the DS. You can debug this by executing monitor_ds.sh script at the hosts. Monitor DS is a bash script, at the top you can find out the arguments you need to pass to it 3.- Did you set DATASTORE_LOCATION? Maybe the monitor script is not looking at the right place. (Also could you double check that the datastore is actually mounted?) Hope it helps Ruben On Fri, Jan 17, 2014 at 5:42 PM, Javier javier.alva...@bsc.es wrote: Hello, After a reboot my VMs started getting stuck in PENDING state. Watching at the log files I noticed that the problem was that the system datastore was not being correctly monitored: onedatastore list ID NAMESIZE AVAIL CLUSTER IMAGES TYPE DS TM 0 system0M - - 0 sys -shared 1 default31.3T 57% -12 img fs shared 2 files 31.3T 57% - 2 fil fs ssh And I was getting the following error: Fri Jan 17 17:32:02 2014 [SCHED][D]: VM 2794: Local Datastore 0 in Host 8 filtered out. Not enough capacity. Now, if I create a new system datastore, it happens the same as with datastore 0. However, creating an image datastore and then changing its type to SYSTEM_DS makes it work fine and VMs start being deployed again using that alternative system datastore. My question is if this is a bug or if I am making some mistake. Thank you, Javier WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
