On Fri, Oct 26, 2012 at 8:06 AM, Curtis C. <[email protected]> wrote: > On Fri, Oct 26, 2012 at 7:48 AM, Dmitri Chebotarov <[email protected]> wrote: >> Curtis >> >> Do you have an option to connect to the reservation via a console? >> Does the computer have networking after reservation fail? > > Yes I can connect to the console, and the computer's network is no > longer working, I'm guessing because dhcp fails due to something the > VCL commands are doing. > > However, if I run a ipconfig /renew on the computer it can get it's > dhcp address back and things continue on as usual. If I don't run a > renew command the computer does not get an IP again on it's own. The > computers in this case, with an openstack backend, get their IP from > dhcp, which I believe have a one minute lease time. (I'm going to > increase that this morning as a workaround.)
FYI, the workaround of increasing openstack's dhcp lease time to 8 hours is working. By default it's 120 seconds. Something vcl is doing kills the initial dhcp address. Thanks, Curtis. > > Thanks, > Curtis. > >> >> On Oct 26, 2012, at 9:33 , Aaron Peeler <[email protected]> wrote: >> >>> I'm not very good at windows 7/2008 kms activation process. But could >>> it be related to this. I see in your log one of the last warnings is a >>> message about not being able to activate. Is somehow in the process >>> the networking getting disabled or diminished? >>> >>> Aaron >>> >>> On Thu, Oct 25, 2012 at 8:59 PM, Curtis C. <[email protected]> wrote: >>>> Still trying to troubleshoot this issue. >>>> >>>> For some reason the networking stops on my windows 7 and server 2008 >>>> instances just before we hit "waiting for user acknowledgement." >>>> >>>> Here's another log file: >>>> >>>> http://pastebin.com/raw.php?i=91a4GnhQ >>>> >>>> Though I've been doing some "print" debugging so there might be a few >>>> unusual things in that log file. >>>> >>>> Eventually I'll find it, but sure would be nice to do so sooner than >>>> later, before I go blind from eye strain. :) >>>> >>>> Thanks, >>>> Curtis. >>>> >>>> On Mon, Oct 22, 2012 at 4:03 PM, Curtis C. <[email protected]> wrote: >>>>> So it turns out that the OpenStack bug probably wasn't affecting this >>>>> issue. >>>>> >>>>> Here is another log of a failed reservation: >>>>> >>>>> http://pastebin.com/raw.php?i=K6RPMK8A >>>>> >>>>> These are the last SSH commands that are executed on the instance: >>>>> >>>>> 2012-10-22 >>>>> 15:37:12|1739|56:56|new|utils.pm:run_ssh_command(4936)|executing >>>>> SSH command on vm1: >>>>> |1739|56:56|new| /usr/bin/ssh -i /etc/vcl/vcl.key -o >>>>> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o >>>>> ConnectionAttempts=1 -o ConnectTimeout=3 -l root -p 22 -x vm1 >>>>> 'C:/Windows/Sysnative/net.exe user "admin"' 2>&1 >>>>> 2012-10-22 15:37:13|1739|56:56|new|Windows.pm:user_exists(1672)|user >>>>> admin does not exist on vm1 >>>>> 2012-10-22 15:37:13|1739|56:56|new|Windows.pm:create_user(1744)|attempting >>>>> to add user admin to vm1 (XWekEk) >>>>> 2012-10-22 15:37:13|1739|56:56|new|Windows.pm:create_user(1755)|user >>>>> will be added to the Administrators group >>>>> 2012-10-22 >>>>> 15:37:13|1739|56:56|new|utils.pm:run_ssh_command(4936)|executing >>>>> SSH command on vm1: >>>>> |1739|56:56|new| /usr/bin/ssh -i /etc/vcl/vcl.key -o >>>>> StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o >>>>> ConnectionAttempts=1 -o ConnectTimeout=3 -l root -p 22 -x vm1 >>>>> 'C:/Windows/Sysnative/net.exe user "admin" "XWekEk" /ADD >>>>> /EXPIRES:NEVER /COMMENT:"Account created by VCL" && >>>>> C:/Windows/Sysnative/net.exe localgroup "Remote Desktop Users" "admin" >>>>> /ADD && C:/Windows/Sysnative/net.exe localgroup "Administrators" >>>>> "admin" /ADD' 2>&1 >>>>> >>>>> == >>>>> >>>>> At which point the networking fails on the instance and no further SSH >>>>> commands can run. >>>>> >>>>> Any ideas around that? Perhaps something missing from the "capture" >>>>> process? >>>>> >>>>> Thanks, >>>>> Curtis. >>>>> >>>>> On Mon, Oct 22, 2012 at 1:43 PM, Curtis C. <[email protected]> wrote: >>>>>> On Mon, Oct 22, 2012 at 12:09 PM, Aaron Peeler <[email protected]> >>>>>> wrote: >>>>>>> Hi Curtis, >>>>>>> >>>>>>> The process flow is not documented, but yes when a user hits the >>>>>>> connect button the OS firewall is modified. But looking at your log >>>>>>> output, it's not getting to that step. >>>>>> >>>>>> Ok, I think you are right. I think it was just coincidence that the >>>>>> networking failed when I clicked connect. I did a few more tests and >>>>>> waited longer and the networking for the instance is failing. I think >>>>>> I've hit a known OpenStack bug that is fixed in updates, so I will try >>>>>> that out. >>>>>> >>>>>> Thanks for your help, >>>>>> Curtis. >>>>>> >>>>>>> >>>>>>> It's not able to ssh into the vm1 to update anything. >>>>>>> >>>>>>> Can to tell if anything is happening to vm1 between the new state and >>>>>>> the reserved state? >>>>>>> Like the vm1 gets turned off or the vm gets a new IP from openstack >>>>>>> and is does not resolve to vm1 anymore? >>>>>>> >>>>>>> Aaron >>>>>>> >>>>>>> On Mon, Oct 22, 2012 at 12:50 PM, Curtis C. <[email protected]> >>>>>>> wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> I have a Windows server 2008 instance/slot/computer which is up until >>>>>>>> the user connects, then the networking on the instance stops, I assume >>>>>>>> because hitting the connect button sets off some kind of networking >>>>>>>> process on the instance, such as adding firewall rules. In this case >>>>>>>> the instances get their IP via DHCP because VCL is being backended by >>>>>>>> OpenStack. >>>>>>>> >>>>>>>> Is that connection/networking process documented anywhere? >>>>>>>> >>>>>>>> As I may be totally wrong, kinda new to VCL :), about what is going >>>>>>>> on, here are the logs for one of the reservations: >>>>>>>> >>>>>>>> http://pastebin.com/raw.php?i=L5G3qCmx >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Curtis. >>>>>>>> >>>>>>>> -- >>>>>>>> Twitter: @serverascode >>>>>>>> Blog: serverascode.com >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Aaron Peeler >>>>>>> Program Manager >>>>>>> Virtual Computing Lab >>>>>>> NC State University >>>>>>> >>>>>>> All electronic mail messages in connection with State business which >>>>>>> are sent to or received by this account are subject to the NC Public >>>>>>> Records Law and may be disclosed to third parties. >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Twitter: @serverascode >>>>>> Blog: serverascode.com >>>>> >>>>> >>>>> >>>>> -- >>>>> Twitter: @serverascode >>>>> Blog: serverascode.com >>>> >>>> >>>> >>>> -- >>>> Twitter: @serverascode >>>> Blog: serverascode.com >>> >>> >>> >>> -- >>> Aaron Peeler >>> Program Manager >>> Virtual Computing Lab >>> NC State University >>> >>> All electronic mail messages in connection with State business which >>> are sent to or received by this account are subject to the NC Public >>> Records Law and may be disclosed to third parties. >> >> >> >> -- >> Thank you, >> >> Dmitri Chebotarov >> Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging >> 223 Aquia Building, Ffx, MSN: 1B5 >> Phone: (703) 993-6175 >> Fax: (703) 993-3404 >> >> >> >> > > > > -- > Twitter: @serverascode > Blog: serverascode.com -- Twitter: @serverascode Blog: serverascode.com
