Ubuntu
eucalyptus package

otherwise live instance goes deaf connection refused

Asked by Walt Corey

I had an instance up and running for hours, quite successfully. I left it alone for awhile and when I went back to that cmd session the window was dead, as when you shell into another machine and drop the vpn. In that case the entire window is unresponsive.

I tried opening another session and logging in from there. no good.
I tried rebooting the instance and then logging back in. no good. I do not believe the instance rebooted at all.
I did a describe-instances and it showed as running.
I did a terminate-instance and it shutdown.
I restarted it and still can not get in. To my knowledge nothing happened at the cluster.

No matter what I do I receive, after a suitable delay....

ssh: connect to host 192.168.3.100 port 22: Connection refused

I tried the private ip address with the same results.

I suspect that isn't enough for anyone to diagnose what happened, unless it is a known bug.

Where should I look for the answer, and better yet, what would prevent that in the future. It had been running fine. I had a mysql as well as tomcat 6 tasksel up and running on it. I had copied over a complete over 2M row database and was accessing it through the instance, until it went silent.

Thanks,

Walt

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu eucalyptus Edit question
Assignee:
No assignee Edit question
Solved by:
Walt Corey
Solved:
Last query:
Last reply:
Revision history for this message
Torsten Spindler (tspindler) said : 		#1

A good command to gather more debugging output is often
'euca-get-console-output'. In your case I would have checked also what
the output of 'euca-describe-instances' writes, especially if the
network configuration looks good.

I assume you ssh'ed from the same machine? Otherwise probably the ssh
port was not enabled with 'euca-authorize'.

Revision history for this message
Walt Corey (waltc) said : 		#2

Thanks for the quick reply.

The describe-instances looked identical to when I was able to connect, really, no difference. It should the same public ip as well as the same private ip and had a status of running.

I started literally in the same terminal session to the instance, which was dead. I see the same behavior if I vpn, for instance, to my work machine and disconnect the vpn session prior to ending the terminal session. The terminal session goes dead.

The instance is responsive, or so it appears as on a terminate request the state, via describe-instances, goes from running, to shutting down to terminated to, eventually, not displaying at all.

I will try, tonight, to view the console log and report back. Am I safe in assuming there are no known problems in this area?

Thanks,
Walt

Revision history for this message
Walt Corey (waltc) said : 		#3

As a followup:

On the cluster controller (or cloud controller) there is a dhcpd which manages both the private ip addresses as well as the public ip addresses, correct? This is why you want to give the installation of the cluster a range of addresses not in use already. Correct me if I am wrong, but I suspect that description should more properly be a subnet not currently in use, independent of a range not in use. This is why I had to reinstall (refer to my cloud store question) as I initially gave a range at the high end of subnet controlled by my router and there were massive unanticipated problems as a result. Placing the range in the 192.168.3 subnet solved all the unanticipated issues.

Is there a document, or might you elaborate, on the functioning of the public/private ip addesses given to an activating instance as well as lease duration and life cycle.

Thanks,

Walt

Revision history for this message
Torsten Spindler (tspindler) said : 		#4

...
> I will try, tonight, to view the console log and report back. Am I safe
> in assuming there are no known problems in this area?

I haven't seen the problem that an instance became unreachable without
loss of public IP address. What I've seen before is that an instance
becomes reachable if it picks up an IP address by DHCP from a renegade
DHCP server and not from the Eucalyptus CC.

Revision history for this message
Torsten Spindler (tspindler) said : 		#5

On Tue, 2010-05-25 at 14:35 +0000, waltc wrote:
...
> Is there a document, or might you elaborate, on the functioning of the
> public/private ip addesses given to an activating instance as well as
> lease duration and life cycle.

The public IP address list should not be served by your DHCP server. For
example in my test cloud I have set up the DHCP server to not serve IPs
between 192.168.1.1 and 192.168.1.99. Instead these are served by the CC
of the cloud to instances.

On documentation for the networking functions, you best look at the
upstream wiki at http://open.eucalyptus.com. In the UEC training by
Canonical (the company I work for) we do cover the network modes, though
not at the level of detail as lease length.

Revision history for this message
Walt Corey (waltc) said : 		#6

Yes, I acknowledge that. My default dhcp server is my router and it handles 192.168.01->192.168.0.255.

Originally when the prompt asked me for the range to use for public ips I gave it 192.168.0.200->192.168.0.250.

That wrecked havoc on my NFS mounts so I purged and reinstalled and answered 192.168.3.100->192.168.3.150

That cured my issue with nfs mounts.

Doesn't the dhcp server get installed as a function of installing the cloud cluster, as it serves up the private ip addresses as well as the public cloud ips?

Again, the describe instances shows the public ip as 192.168.3.100 and the private on something like 172.2.1.3. In the later case I know of no conflict with that address space between my wireless router and the dhcp server. So after I lost the 192.168.3.100 I did try the private address and it did not work either. Could the lease have expired and or could the host thought the lease had expired and failed to renew it, perhaps because the dhcp showed it as being in use? How would I tell, console log?

Revision history for this message
Torsten Spindler (tspindler) said : 		#7

...
> Doesn't the dhcp server get installed as a function of installing the
> cloud cluster, as it serves up the private ip addresses as well as the
> public cloud ips?

Yes, the dhcp server gets installed on the Cluster Controller (CC) to
serve the public and private IPs in the default networking mode
MANAGED-NOVLAN.

> Again, the describe instances shows the public ip as 192.168.3.100 and
> the private on something like 172.2.1.3. In the later case I know of no
> conflict with that address space between my wireless router and the dhcp
> server. So after I lost the 192.168.3.100 I did try the private address
> and it did not work either. Could the lease have expired and or could
> the host thought the lease had expired and failed to renew it, perhaps
> because the dhcp showed it as being in use? How would I tell, console
> log?

Sorry to come back with more questions: Can you ping the private IP from
your CC? Can you post the console output of the instance in question
that cannot be reached via ssh anymore? Can you check the 'iptable -t
nat -n -L' output on the CC and confirm that NATing is setup for
192.168.3.X network? All of this could go wrong, albeit I've never seen
it before.

Revision history for this message
Walt Corey (waltc) said : 		#8

Here is the iproutes command output

Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DNAT tcp -- 172.19.0.0/16 169.254.169.254 tcp dpt:80 to:169.254.169.254:8773

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE all -- !127.0.0.0/8 !172.19.0.0/16

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

This is very weird....this was the first output. As you can see no 192.168.3.100
I issued a euca-run again then issued the iproutes cmd, notice the difference.

Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DNAT tcp -- 172.19.0.0/16 169.254.169.254 tcp dpt:80 to:169.254.169.254:8773
DNAT all -- 0.0.0.0/0 192.168.3.100 to:172.19.1.2

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
SNAT all -- 172.19.1.2 !172.19.0.0/16 to:192.168.3.100
MASQUERADE all -- !127.0.0.0/8 !172.19.0.0/16

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
DNAT all -- 0.0.0.0/0 192.168.3.100 to:172.19.1.2

WHile the binding is present I still can not connect to either ip address

I can successfully ping both addresses.

Revision history for this message
Walt Corey (waltc) said : 		#9

I am using mangednvlan.

Here is the console output...note: this is a Ubuntu image:

i-385A076C
2010-05-25T21:14:15.844Z
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.31-14-generic-pae (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 15:22:42 UTC 2009 (Ubuntu 2.6.31-14.48-generic-pae)
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
[ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000000fffb000 (usable)
[ 0.000000] BIOS-e820: 000000000fffb000 - 0000000010000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fffbc000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.4 present.
[ 0.000000] last_pfn = 0xfffb max_arch_pfn = 0x1000000
[ 0.000000] PAT not supported by CPU.
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000002000 (usable)
[ 0.000000] modified: 0000000000002000 - 0000000000006000 (reserved)
[ 0.000000] modified: 0000000000006000 - 000000000009f000 (usable)
[ 0.000000] modified: 000000000009f000 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 000000000fffb000 (usable)
[ 0.000000] modified: 000000000fffb000 - 0000000010000000 (reserved)
[ 0.000000] modified: 00000000fffbc000 - 0000000100000000 (reserved)
[ 0.000000] init_memory_mapping: 0000000000000000-000000000fffb000
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] RAMDISK: 0fd51000 - 0ffeffcc
[ 0.000000] ACPI: RSDP 000f8940 00014 (v00 BOCHS )
[ 0.000000] ACPI: RSDT 0fffde30 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001)
[ 0.000000] ACPI: FACP 0ffffe70 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001)
[ 0.000000] ACPI: DSDT 0fffdfd0 01E22 (v01 BXPC BXDSDT 00000001 INTL 20090123)
[ 0.000000] ACPI: FACS 0ffffe00 00040
[ 0.000000] ACPI: SSDT 0fffdf90 00037 (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001)
[ 0.000000] ACPI: APIC 0fffdeb0 00072 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001)
[ 0.000000] ACPI: HPET 0fffde70 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001)
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 255MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 0fffb000
[ 0.000000] low ram: 0 - 0fffb000
[ 0.000000] node 0 low ram: 00000000 - 0fffb000
[ 0.000000] node 0 bootmap 00009000 - 0000b000
[ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 000fffb000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
[ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
[ 0.000000] #3 [0000100000 - 00008ad9a0] TEXT DATA BSS ==> [0000100000 - 00008ad9a0]
[ 0.000000] #4 [000fd51000 - 000ffeffcc] RAMDISK ==> [000fd51000 - 000ffeffcc]
[ 0.000000] #5 [000009f000 - 0000100000] BIOS reserved ==> [000009f000 - 0000100000]
[ 0.000000] #6 [00008ae000 - 00008b4071] BRK ==> [00008ae000 - 00008b4071]
[ 0.000000] #7 [0000007000 - 0000009000] PGTABLE ==> [0000007000 - 0000009000]
[ 0.000000] #8 [0000009000 - 000000b000] BOOTMAP ==> [0000009000 - 000000b000]
[ 0.000000] found SMP MP-table at [c00f8990] f8990
[ 0.000000] kvm-clock: cpu 0, msr 0:81c581, boot clock
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000000 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x0000fffb
[ 0.000000] HighMem 0x0000fffb -> 0x0000fffb
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[3] active PFN ranges
[ 0.000000] 0: 0x00000000 -> 0x00000002
[ 0.000000] 0: 0x00000006 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x0000fffb
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0xb008
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: 0000000000002000 - 0000000000006000
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at 10000000 (gap: 10000000:effbc000)
[ 0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages at c1202000, static data 35612 bytes
[ 0.000000] kvm-clock: cpu 0, msr 0:120a581, primary cpu clock
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64918
[ 0.000000] Kernel command line: root=/dev/sda1 console=ttyS0
[ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] allocated 1310620 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Initializing HighMem for node 0 (00000000:00000000)
[ 0.000000] Memory: 247280k/262124k available (4588k kernel code, 14204k reserved, 2148k data, 544k init, 0k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xfff1d000 - 0xfffff000 ( 904 kB)
[ 0.000000] pkmap : 0xffa00000 - 0xffc00000 (2048 kB)
[ 0.000000] vmalloc : 0xd07fb000 - 0xff9fe000 ( 754 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xcfffb000 ( 255 MB)
[ 0.000000] .init : 0xc0795000 - 0xc081d000 ( 544 kB)
[ 0.000000] .data : 0xc057b314 - 0xc07946e8 (2148 kB)
[ 0.000000] .text : 0xc0100000 - 0xc057b314 (4588 kB)
[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[ 0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:2304 nr_irqs:256
[ 0.000000] Detected 2660.560 MHz processor.
[ 0.004000] Console: colour VGA+ 80x25
[ 0.004000] console [ttyS0] enabled
[ 0.004000] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[ 0.008004] Calibrating delay loop (skipped) preset value.. 5321.12 BogoMIPS (lpj=10642240)
[ 0.008667] Security Framework initialized
[ 0.009040] AppArmor: AppArmor initialized
[ 0.009390] Mount-cache hash table entries: 512
[ 0.009884] Initializing cgroup subsys ns
[ 0.010233] Initializing cgroup subsys cpuacct
[ 0.010579] Initializing cgroup subsys memory
[ 0.010943] Initializing cgroup subsys freezer
[ 0.011346] Initializing cgroup subsys net_cls
[ 0.012032] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.012658] CPU: L2 cache: 4096K
[ 0.012912] mce: CPU supports 10 MCE banks
[ 0.013386] Performance Counters: unsupported p6 CPU model 2 no PMU driver, software counters only.
[ 0.016004] SMP alternatives: switching to UP code
[ 0.032006] Freeing SMP alternatives: 19k freed
[ 0.032408] ACPI: Core revision 20090521
[ 0.036727] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.037296] CPU0: Intel QEMU Virtual CPU version 0.12.3 stepping 03
[ 0.040001] Brought up 1 CPUs
[ 0.040001] Total of 1 processors activated (5321.12 BogoMIPS).
[ 0.040001] Booting paravirtualized kernel on KVM
[ 0.040001] regulator: core version 0.5
[ 0.040001] Time: 21:06:13 Date: 05/25/10
[ 0.040001] NET: Registered protocol family 16
[ 0.040001] EISA bus registered
[ 0.040001] ACPI: bus type pci registered
[ 0.040256] PCI: PCI BIOS revision 2.10 entry at 0xffe77, last bus=0
[ 0.040846] PCI: Using configuration type 1 for base access
[ 0.041920] bio: create slab <bio-0> at 0
[ 0.043810] ACPI: Interpreter enabled
[ 0.044004] ACPI: (supports S0 S3 S4 S5)
[ 0.044442] ACPI: Using IOAPIC for interrupt routing
[ 0.046327] ACPI: No dock devices found.
[ 0.046687] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.048365] pci 0000:00:01.3: quirk: region b000-b03f claimed by PIIX4 ACPI
[ 0.049070] pci 0000:00:01.3: quirk: region b100-b10f claimed by PIIX4 SMB
[ 0.054418] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[ 0.055061] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[ 0.055678] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[ 0.056204] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[ 0.057299] SCSI subsystem initialized
[ 0.057875] usbcore: registered new interface driver usbfs
[ 0.058468] usbcore: registered new interface driver hub
[ 0.058968] usbcore: registered new device driver usb
[ 0.059662] ACPI: WMI: Mapper loaded
[ 0.060006] PCI: Using ACPI for IRQ routing
[ 0.060613] Bluetooth: Core ver 2.15
[ 0.060968] NET: Registered protocol family 31
[ 0.061360] Bluetooth: HCI device and connection manager initialized
[ 0.061990] Bluetooth: HCI socket layer initialized
[ 0.062414] NetLabel: Initializing
[ 0.062744] NetLabel: domain hash size = 128
[ 0.063144] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.063609] NetLabel: unlabeled traffic allowed by default
[ 0.064063] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.064584] hpet0: 3 comparators, 64-bit 100.000000 MHz counter
[ 0.069723] pnp: PnP ACPI init
[ 0.070046] ACPI: bus type pnp registered
[ 0.070982] pnp: PnP ACPI: found 7 devices
[ 0.071373] ACPI: ACPI bus type pnp unregistered
[ 0.071819] PnPBIOS: Disabled
[ 0.106667] AppArmor: AppArmor Filesystem Enabled
[ 0.107195] NET: Registered protocol family 2
[ 0.107639] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.108518] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.109257] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.109876] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.110563] TCP reno registered
[ 0.110884] NET: Registered protocol family 1
[ 0.111365] Trying to unpack rootfs image as initramfs...
[ 0.162481] Freeing initrd memory: 2683k freed
[ 0.163297] cpufreq-nforce2: No nForce2 chipset.
[ 0.163749] Scanning for low memory corruption every 60 seconds
[ 0.164442] audit: initializing netlink socket (disabled)
[ 0.164959] type=2000 audit(1274821574.164:1): initialized
[ 0.172351] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.173746] VFS: Disk quotas dquot_6.5.2
[ 0.174169] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.175138] fuse init (API version 7.12)
[ 0.175599] msgmni has been set to 488
[ 0.176185] alg: No test for stdrng (krng)
[ 0.176658] io scheduler noop registered
[ 0.177011] io scheduler anticipatory registered
[ 0.177473] io scheduler deadline registered
[ 0.177915] io scheduler cfq registered (default)
[ 0.178340] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
[ 0.178941] pci 0000:00:01.0: PIIX3: Enabling Passive Release
[ 0.179496] pci 0000:00:01.0: Activating ISA DMA hang workarounds
[ 0.180155] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.180691] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.181366] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[ 0.182002] ACPI: Power Button [PWRF]
[ 0.182587] processor LNXCPU:00: registered as cooling_device0
[ 0.183548] isapnp: Scanning for PnP cards...
[ 0.538679] isapnp: No Plug & Play device found
[ 0.539784] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.540489] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.541258] 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.542375] brd: module loaded
[ 0.542940] loop: module loaded
[ 0.543268] input: Macintosh mouse button emulation as /devices/virtual/input/input1
[ 0.544219] scsi0 : ata_piix
[ 0.544534] scsi1 : ata_piix
[ 0.544818] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14
[ 0.545399] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15
[ 0.546590] Fixed MDIO Bus: probed
[ 0.546914] PPP generic driver version 2.4.2
[ 0.547341] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.547918] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.548470] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.549131] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
[ 0.549640] uhci_hcd 0000:00:01.2: PCI INT D -> Link[LNKD] -> GSI 11 (level, high) -> IRQ 11
[ 0.550371] uhci_hcd 0000:00:01.2: UHCI Host Controller
[ 0.550860] uhci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
[ 0.551553] uhci_hcd 0000:00:01.2: irq 11, io base 0x0000c020
[ 0.552304] usb usb1: configuration #1 chosen from 1 choice
[ 0.552873] hub 1-0:1.0: USB hub found
[ 0.553337] hub 1-0:1.0: 2 ports detected
[ 0.553868] PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[ 0.555022] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.555563] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.556087] mice: PS/2 mouse device common for all mice
[ 0.556751] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
[ 0.557572] rtc0: alarms up to one day, 114 bytes nvram, hpet irqs
[ 0.558262] device-mapper: uevent: version 1.0.3
[ 0.559073] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
[ 0.560163] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: <email address hidden>
[ 0.560998] device-mapper: multipath: version 1.1.0 loaded
[ 0.561473] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 0.562201] EISA: Probing bus 0 at eisa.0
[ 0.562611] EISA: Detected 0 cards.
[ 0.563010] cpuidle: using governor ladder
[ 0.563370] cpuidle: using governor menu
[ 0.564047] TCP cubic registered
[ 0.564440] NET: Registered protocol family 10
[ 0.565177] lo: Disabled Privacy Extensions
[ 0.565733] NET: Registered protocol family 17
[ 0.566393] Bluetooth: L2CAP ver 2.13
[ 0.566735] Bluetooth: L2CAP socket layer initialized
[ 0.567285] Bluetooth: SCO (Voice Link) ver 0.6
[ 0.567701] Bluetooth: SCO socket layer initialized
[ 0.568243] Bluetooth: RFCOMM TTY layer initialized
[ 0.568698] Bluetooth: RFCOMM socket layer initialized
[ 0.569170] Bluetooth: RFCOMM ver 1.11
[ 0.569557] Using IPI No-Shortcut mode
[ 0.569943] registered taskstats version 1
[ 0.570373] Magic number: 10:166:147
[ 0.570737] acpi device:18: hash matches
[ 0.571115] rtc_cmos 00:01: setting system clock to 2010-05-25 21:06:13 UTC (1274821573)
[ 0.571880] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 0.572477] EDD information not available.
[ 0.708618] ata2.00: ATAPI: QEMU DVD-ROM, 0.12.3, max UDMA/100
[ 0.709752] ata2.00: configured for MWDMA2
[ 0.710943] scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM 0.12 PQ: 0 ANSI: 5
[ 0.713906] sr0: scsi3-mmc drive: 4x/4x xa/form2 tray
[ 0.714740] Uniform CD-ROM driver Revision: 3.20
[ 0.715608] sr 1:0:0:0: Attached scsi generic sg0 type 5
[ 0.716513] Freeing unused kernel memory: 544k freed
[ 0.717738] Write protecting the kernel text: 4592k
[ 0.718612] Write protecting the kernel read-only data: 1836k
Loading, please wait...
Couldn't get a file descriptor referring to the console
Begin: Loading essential drivers... ...
[ 0.988015] sym53c8xx 0000:00:04.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, high) -> IRQ 11
[ 0.989940] sym0: <895a> rev 0x0 at pci 0000:00:04.0 irq 11
[ 0.992578] sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
[ 0.996019] sym0: SCSI BUS has been reset.
[ 1.003455] scsi2 : sym-2.2.3
[ 1.005905] Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
[ 1.006498] Copyright (c) 1999-2006 Intel Corporation.
Done.
Begin: Running /scripts/init-premount ...
[ 1.032926] FDC 0 is a S82078B
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
[ 1.065941] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
[ 1.066592] e1000 0000:00:03.0: PCI INT A -> Link[LNKC] -> GSI 10 (level, high) -> IRQ 10
[ 1.343996] e1000: 0000:00:03.0: e1000_probe: (PCI:33MHz:32-bit) d0:0d:38:5a:07:6c
[ 1.383651] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 4.012285] scsi 2:0:0:0: Direct-Access QEMU QEMU HARDDISK 0.12 PQ: 0 ANSI: 3
[ 4.013586] scsi target2:0:0: tagged command queuing enabled, command queue depth 16.
[ 4.014810] scsi target2:0:0: Beginning Domain Validation
[ 4.016084] scsi target2:0:0: Domain Validation skipping write tests
[ 4.017012] scsi target2:0:0: Ending Domain Validation
[ 4.020731] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 4.021742] sd 2:0:0:0: [sda] 10579968 512-byte logical blocks: (5.41 GB/5.04 GiB)
[ 4.022920] sd 2:0:0:0: [sda] Write Protect is off
[ 4.023765] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4.025500] sda: sda1 sda2 sda3
[ 4.028007] sd 2:0:0:0: [sda] Attached SCSI disk
Done.
Begin: Running /scripts/local-premount ...
Done.
[ 4.081824] kjournald starting. Commit interval 5 seconds
[ 4.082314] EXT3-fs: mounted filesystem with writeback data mode.
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Begin: Starting AppArmor profiles ...
[ 4.219371] type=1505 audit(1274821577.144:2): operation="profile_load" pid=348 name=/sbin/dhclient3
[ 4.220232] type=1505 audit(1274821577.149:3): operation="profile_load" pid=348 name=/usr/lib/NetworkManager/nm-dhcp-client.action
[ 4.221272] type=1505 audit(1274821577.149:4): operation="profile_load" pid=348 name=/usr/lib/connman/scripts/dhclient-script
[ 4.268662] type=1505 audit(1274821577.196:5): operation="profile_load" pid=349 name=/usr/sbin/tcpdump
Done.
Done.
[ 4.330062] EXT3-fs warning: checktime reached, running e2fsck is recommended
[ 4.383740] EXT3 FS on sda1, internal journal
[ 4.411352] ext3: No journal on filesystem on sda2
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

mountall: mount /mnt [389] terminated with status 32
mountall: Filesystem could not be mounted: /mnt
[ 4.423651] ext3: No journal on filesystem on sda2
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

mountall: mount /mnt [393] terminated with status 32
mountall: Filesystem could not be mounted: /mnt
[ 4.429894] ext3: No journal on filesystem on sda2
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

mountall: mount /mnt [399] terminated with status 32
mountall: Filesystem could not be mounted: /mnt
 * Setting preliminary keymap... * Setting up console font and keymap... * Waiting for EC2 meta-data service [ 7.901606] ext3: No journal on filesystem on sda2
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

mountall: mount /mnt [883] terminated with status 32
mountall: Filesystem could not be mounted: /mnt

Revision history for this message
Walt Corey (waltc) said : 		#10

This may be related:

I had to reboot the cluster controller after purging the python-cloud-store (112156) and after reboot the image that was running before still shows as running but has neither a public nor private IP Address listed. I trust I am the only one surprised by this.

I wanted to check the system log to see if there was anything interesting from the dhcp server running on this server. I paste below. I am confused by this regarding the repeated requests for the 172 address. Also the DHCPDISCOVER no free leases for euca. This is from yesterday

May 24 00:00:33 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 00:00:33 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:00:35 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 00:00:35 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:00:35 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 00:00:35 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:18:12 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 00:18:12 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:18:14 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 00:18:14 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:18:14 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 00:18:14 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:35:44 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 00:35:44 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:35:46 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 00:35:46 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:35:46 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 00:35:46 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:53:19 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 00:53:19 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:53:20 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 00:53:20 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 00:53:20 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 00:53:20 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 01:11:03 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 01:11:03 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 01:11:04 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 01:11:04 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 01:11:04 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 01:11:04 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 01:28:39 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 01:28:39 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 01:28:40 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 01:28:40 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 01:28:40 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 01:28:40 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 01:46:28 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 01:46:28 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 01:46:29 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 01:46:29 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 01:46:29 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 01:46:29 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:04:08 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 02:04:08 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:04:09 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 02:04:09 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:04:09 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 02:04:09 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:21:50 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 02:21:50 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:21:51 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 02:21:51 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:21:51 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 02:21:51 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:23:07 cor720 dhcpd: DHCPREQUEST for 192.168.0.8 from 00:0c:29:4b:38:02 via eth0: unknown lease 192.168.0.8.
May 24 02:23:07 cor720 dhcpd: DHCPREQUEST for 192.168.0.8 from 00:0c:29:4b:38:02 via eth0: unknown lease 192.168.0.8.
May 24 02:39:30 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 02:39:30 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:39:31 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 02:39:31 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:39:31 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 02:39:31 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:57:18 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 02:57:18 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:57:19 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 02:57:19 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 02:57:19 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 02:57:19 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 03:14:52 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 03:14:52 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 03:14:53 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 03:14:53 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 03:14:53 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 03:14:53 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 03:23:50 cor720 dhcpd: DHCPDISCOVER from 00:11:d9:17:cd:0f via eth0: network euca: no free leases
May 24 03:23:50 cor720 dhcpd: DHCPDISCOVER from 00:11:d9:01:9b:49 via eth0: network euca: no free leases
May 24 03:23:52 cor720 dhcpd: DHCPREQUEST for 192.168.0.4 (192.168.0.1) from 00:11:d9:17:cd:0f via eth0: ignored (not authoritative).
May 24 03:23:52 cor720 dhcpd: DHCPREQUEST for 192.168.0.5 (192.168.0.1) from 00:11:d9:01:9b:49 via eth0: ignored (not authoritative).
May 24 03:32:31 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 03:32:31 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 03:32:32 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 03:32:32 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 03:32:32 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 03:32:32 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 03:50:07 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 03:50:07 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 03:50:08 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 03:50:08 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 03:50:08 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 03:50:08 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 04:07:47 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 04:07:47 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 04:07:48 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 04:07:48 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 04:07:48 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 04:07:48 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 04:25:33 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 04:25:33 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 04:25:34 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 04:25:34 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 04:25:34 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 04:25:34 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 04:35:52 cor720 dhcpd: DHCPDISCOVER from 00:0d:a2:01:38:7b via eth0: network euca: no free leases
May 24 04:35:52 cor720 dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.1) from 00:0d:a2:01:38:7b via eth0: ignored (not authoritative).
May 24 04:43:07 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 04:43:07 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 04:43:08 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 04:43:08 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 04:43:08 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 04:43:08 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:00:42 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 05:00:42 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:00:43 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 05:00:43 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:00:43 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 05:00:43 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:18:19 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 05:18:19 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:18:20 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 05:18:20 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:18:20 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 05:18:20 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:36:04 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 05:36:04 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:36:05 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 05:36:05 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:36:05 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 05:36:05 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:53:44 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 05:53:44 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:53:45 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 05:53:45 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 05:53:45 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 05:53:45 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 06:11:22 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 06:11:22 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 06:11:23 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 06:11:23 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 06:11:23 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 06:11:23 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 06:13:19 cor720 dhcpd: DHCPDISCOVER from 60:fb:42:e0:73:10 via eth0: network euca: no free leases
May 24 06:13:20 cor720 dhcpd: DHCPDISCOVER from 60:fb:42:e0:73:10 via eth0: network euca: no free leases
May 24 06:13:21 cor720 dhcpd: DHCPREQUEST for 192.168.0.11 (192.168.0.1) from 60:fb:42:e0:73:10 via eth0: ignored (not authoritative).
May 24 06:13:24 cor720 avahi-daemon[1212]: Invalid query packet.
May 24 06:14:36 cor720 avahi-daemon[1212]: last message repeated 2 times
May 24 06:28:58 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 06:28:58 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 06:28:59 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 06:28:59 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 06:28:59 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 06:28:59 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 06:46:30 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 06:46:30 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 06:46:31 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 06:46:31 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 06:46:31 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 06:46:31 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:04:18 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 07:04:18 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:04:19 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 07:04:19 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:04:19 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 07:04:19 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:22:06 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 07:22:06 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:22:07 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 07:22:07 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:22:07 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 07:22:07 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:35:18 cor720 dhclient: DHCPREQUEST of 192.168.0.6 on eth0 to 192.168.0.1 port 67
May 24 07:35:18 cor720 dhclient: DHCPNAK from 192.168.0.1
May 24 07:35:18 cor720 NetworkManager: <info> DHCP: device eth0 state changed bound -> expire
May 24 07:35:18 cor720 NetworkManager: <info> DHCP: device eth0 state changed expire -> preinit
May 24 07:35:18 cor720 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
May 24 07:35:18 cor720 dhcpd: DHCPDISCOVER from 00:1e:4f:b4:e2:b5 via eth0: network euca: no free leases
May 24 07:35:18 cor720 dhclient: DHCPOFFER of 192.168.0.6 from 192.168.0.1
May 24 07:35:18 cor720 dhclient: DHCPREQUEST of 192.168.0.6 on eth0 to 255.255.255.255 port 67
May 24 07:35:18 cor720 dhcpd: DHCPREQUEST for 192.168.0.6 (192.168.0.1) from 00:1e:4f:b4:e2:b5 via eth0: ignored (not authoritative).
May 24 07:35:18 cor720 dhclient: DHCPACK of 192.168.0.6 from 192.168.0.1
May 24 07:35:18 cor720 dhclient: bound to 192.168.0.6 -- renewal in 40533 seconds.
May 24 07:35:18 cor720 NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound
May 24 07:35:18 cor720 NetworkManager: <info> address 192.168.0.6
May 24 07:35:18 cor720 NetworkManager: <info> prefix 16 (255.255.0.0)
May 24 07:35:18 cor720 NetworkManager: <info> gateway 192.168.0.1
May 24 07:35:18 cor720 NetworkManager: <info> nameserver '192.168.0.1'
May 24 07:39:44 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 07:39:44 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:39:45 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 07:39:45 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:39:45 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 07:39:45 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:57:30 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 07:57:30 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:57:31 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 07:57:31 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 07:57:31 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 07:57:31 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 08:15:03 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 08:15:03 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 08:15:04 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 08:15:04 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 08:15:04 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 08:15:04 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 08:32:35 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 08:32:35 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 08:32:36 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 08:32:36 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 08:32:36 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 08:32:36 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 08:50:19 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 08:50:19 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 08:50:20 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 08:50:20 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 08:50:20 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 08:50:20 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 09:07:56 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 09:07:56 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 09:07:57 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 09:07:57 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 09:07:57 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 09:07:57 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 09:17:46 cor720 dhcpd: DHCPDISCOVER from a4:ba:db:f9:3d:aa via eth0: network euca: no free leases
May 24 09:17:46 cor720 dhcpd: DHCPREQUEST for 192.168.0.12 (192.168.0.1) from a4:ba:db:f9:3d:aa via eth0: ignored (not authoritative).
May 24 09:25:28 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 09:25:28 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 09:25:29 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 09:25:29 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 09:25:29 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 09:25:29 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 09:38:37 cor720 dhcpd: DHCPINFORM from 192.168.0.3 via eth0: unknown subnet for client address 192.168.0.3
May 24 09:43:10 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 09:43:10 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 09:43:11 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 09:43:11 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 09:43:11 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 09:43:11 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:00:52 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 10:00:52 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:00:53 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 10:00:53 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:00:53 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 10:00:53 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:18:29 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 10:18:29 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:18:30 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 10:18:30 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:18:30 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 10:18:30 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:36:02 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 10:36:02 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:36:03 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 10:36:03 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:36:03 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 10:36:03 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:53:45 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 10:53:45 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:53:46 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 10:53:46 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 10:53:46 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 10:53:46 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 11:11:03 cor720 dhcpd: DHCPINFORM from 192.168.0.8 via eth0: unknown subnet for client address 192.168.0.8
May 24 11:11:03 cor720 dhcpd: DHCPINFORM from 192.168.0.8 via eth0: unknown subnet for client address 192.168.0.8
May 24 11:11:32 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 11:11:32 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 11:11:33 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 11:11:33 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 11:11:33 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 11:11:33 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 11:29:18 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 11:29:18 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 11:29:19 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 11:29:19 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 11:29:19 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 11:29:19 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 11:47:02 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 11:47:02 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 11:47:03 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 11:47:03 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 11:47:03 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 11:47:03 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:04:43 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 12:04:43 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:04:44 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 12:04:44 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:04:44 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 12:04:44 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:22:15 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 12:22:15 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:22:16 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 12:22:16 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:22:16 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 12:22:16 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:39:48 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 12:39:48 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:39:49 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 12:39:49 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:39:49 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 12:39:49 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:57:26 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 12:57:26 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:57:27 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 12:57:27 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 12:57:27 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 12:57:27 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 13:05:14 cor720 dhcpd: DHCPINFORM from 192.168.0.8 via eth0: unknown subnet for client address 192.168.0.8
May 24 13:05:14 cor720 dhcpd: DHCPINFORM from 192.168.0.8 via eth0: unknown subnet for client address 192.168.0.8
May 24 13:15:05 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 13:15:05 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 13:15:06 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 13:15:06 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 13:15:06 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 13:15:06 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 13:32:37 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 13:32:37 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 13:32:38 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 13:32:38 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 13:32:38 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 13:32:38 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 13:50:18 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 13:50:18 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 13:50:19 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 13:50:19 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 13:50:19 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 13:50:19 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 14:07:58 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 14:07:58 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 14:07:59 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 14:07:59 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 14:07:59 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 14:07:59 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 14:23:06 cor720 dhcpd: DHCPREQUEST for 192.168.0.8 from 00:0c:29:4b:38:02 via eth0: unknown lease 192.168.0.8.
May 24 14:23:06 cor720 dhcpd: DHCPREQUEST for 192.168.0.8 from 00:0c:29:4b:38:02 via eth0: unknown lease 192.168.0.8.
May 24 14:25:30 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 14:25:30 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 14:25:31 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 14:25:31 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 14:25:31 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 14:25:31 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 14:43:03 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 14:43:03 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 14:43:04 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 14:43:04 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 14:43:04 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 14:43:04 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:00:39 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 15:00:39 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:00:40 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 15:00:40 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:00:40 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 15:00:40 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:18:23 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 15:18:23 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:18:24 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 15:18:24 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:18:24 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 15:18:24 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:23:51 cor720 dhcpd: DHCPDISCOVER from 00:11:d9:17:cd:0f via eth0: network euca: no free leases
May 24 15:23:52 cor720 dhcpd: DHCPDISCOVER from 00:11:d9:01:9b:49 via eth0: network euca: no free leases
May 24 15:23:54 cor720 dhcpd: DHCPREQUEST for 192.168.0.4 (192.168.0.1) from 00:11:d9:17:cd:0f via eth0: ignored (not authoritative).
May 24 15:23:54 cor720 dhcpd: DHCPREQUEST for 192.168.0.5 (192.168.0.1) from 00:11:d9:01:9b:49 via eth0: ignored (not authoritative).
May 24 15:36:14 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 15:36:14 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:36:15 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 15:36:15 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:36:15 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 15:36:15 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:53:57 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 15:53:57 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:53:58 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 15:53:58 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 15:53:58 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 15:53:58 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 16:08:08 cor720 dhcpd: DHCPINFORM from 192.168.0.3 via eth0: unknown subnet for client address 192.168.0.3
May 24 16:11:32 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 16:11:32 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 16:11:33 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 16:11:33 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 16:11:33 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 16:11:33 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 16:29:15 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 16:29:15 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 16:29:16 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 16:29:16 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 16:29:16 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 16:29:16 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 16:35:56 cor720 dhcpd: DHCPDISCOVER from 00:0d:a2:01:38:7b via eth0: network euca: no free leases
May 24 16:35:56 cor720 dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.1) from 00:0d:a2:01:38:7b via eth0: ignored (not authoritative).
May 24 16:38:54 cor720 dhcpd: DHCPREQUEST for 192.168.0.11 from 60:fb:42:e0:73:10 via eth0: ignored (not authoritative).
May 24 16:38:55 cor720 avahi-daemon[1212]: Invalid query packet.
May 24 16:39:59 cor720 avahi-daemon[1212]: last message repeated 2 times
May 24 16:46:47 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:47:c9:08:7f via eth0
May 24 16:46:47 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 16:46:48 cor720 dhcpd: DHCPDISCOVER from d0:0d:47:c9:08:7f via eth0
May 24 16:46:48 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 16:46:48 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:47:c9:08:7f via eth0
May 24 16:46:48 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:47:c9:08:7f via eth0
May 24 16:48:26 cor720 avahi-daemon[1212]: Registering new address record for 172.19.1.1 on eth0.IPv4.
May 24 16:48:27 cor720 dhcpd: Internet Systems Consortium DHCP Server V3.1.3
May 24 16:48:27 cor720 dhcpd: Copyright 2004-2009 Internet Systems Consortium.
May 24 16:48:27 cor720 dhcpd: All rights reserved.
May 24 16:48:27 cor720 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
May 24 16:48:27 cor720 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
May 24 16:48:27 cor720 dhcpd: Wrote 0 deleted host decls to leases file.
May 24 16:48:27 cor720 dhcpd: Wrote 0 new dynamic host decls to leases file.
May 24 16:48:27 cor720 dhcpd: Wrote 0 leases to leases file.
May 24 16:48:27 cor720 dhcpd: Listening on LPF/eth0/00:1e:4f:b4:e2:b5/euca
May 24 16:48:27 cor720 dhcpd: Sending on LPF/eth0/00:1e:4f:b4:e2:b5/euca
May 24 16:48:27 cor720 dhcpd: Sending on Socket/fallback/fallback-net
May 24 16:48:27 cor720 avahi-daemon[1212]: Registering new address record for 192.168.3.100 on eth0.IPv4.
May 24 16:48:45 cor720 dhcpd: DHCPDISCOVER from d0:0d:57:64:09:5b via eth0
May 24 16:48:45 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 16:48:45 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (192.168.0.6) from d0:0d:57:64:09:5b via eth0
May 24 16:48:45 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 16:58:04 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 16:58:04 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 17:05:37 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 17:05:37 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 17:13:52 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 17:13:52 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 17:22:59 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 17:22:59 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 17:31:47 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 17:31:47 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 17:40:33 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 17:40:33 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 17:48:26 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 17:48:26 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 17:57:54 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 17:57:54 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 18:07:26 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 18:07:26 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 18:15:18 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 18:15:18 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 18:23:24 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 18:23:24 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 18:31:42 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 18:31:42 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 18:40:55 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 18:40:55 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 18:50:22 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 18:50:22 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 18:50:51 cor720 dhclient: DHCPREQUEST of 192.168.0.6 on eth0 to 192.168.0.1 port 67
May 24 18:50:51 cor720 dhclient: DHCPNAK from 192.168.0.1
May 24 18:50:51 cor720 NetworkManager: <info> DHCP: device eth0 state changed bound -> expire
May 24 18:50:51 cor720 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
May 24 18:50:51 cor720 NetworkManager: <info> DHCP: device eth0 state changed expire -> preinit
May 24 18:50:51 cor720 dhcpd: DHCPDISCOVER from 00:1e:4f:b4:e2:b5 via eth0: network euca: no free leases
May 24 18:50:51 cor720 dhclient: DHCPOFFER of 192.168.0.6 from 192.168.0.1
May 24 18:50:51 cor720 dhclient: DHCPREQUEST of 192.168.0.6 on eth0 to 255.255.255.255 port 67
May 24 18:50:51 cor720 dhcpd: DHCPREQUEST for 192.168.0.6 (192.168.0.1) from 00:1e:4f:b4:e2:b5 via eth0: ignored (not authoritative).
May 24 18:50:51 cor720 dhclient: DHCPACK of 192.168.0.6 from 192.168.0.1
May 24 18:50:51 cor720 dhclient: bound to 192.168.0.6 -- renewal in 32652 seconds.
May 24 18:50:51 cor720 NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound
May 24 18:50:51 cor720 NetworkManager: <info> address 192.168.0.6
May 24 18:50:51 cor720 NetworkManager: <info> prefix 16 (255.255.0.0)
May 24 18:50:51 cor720 NetworkManager: <info> gateway 192.168.0.1
May 24 18:50:51 cor720 NetworkManager: <info> nameserver '192.168.0.1'
May 24 18:58:55 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 18:58:55 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 19:08:51 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 19:08:51 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 19:18:19 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 19:18:19 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 19:28:17 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 19:28:17 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 19:33:13 cor720 dhcpd: DHCPDISCOVER from a4:ba:db:f9:3d:aa via eth0: network euca: no free leases
May 24 19:33:13 cor720 dhcpd: DHCPREQUEST for 192.168.0.12 (192.168.0.1) from a4:ba:db:f9:3d:aa via eth0: ignored (not authoritative).
May 24 19:37:01 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 19:37:01 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 19:46:58 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 19:46:58 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 19:55:19 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 19:55:19 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 20:03:40 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 20:03:40 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 20:12:53 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 20:12:53 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 20:21:00 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 20:21:00 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 20:28:32 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 20:28:32 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 20:36:11 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 20:36:11 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 20:44:28 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 20:44:28 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 20:54:25 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 20:54:25 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 21:03:28 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 21:03:28 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 21:11:18 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 21:11:18 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 21:21:15 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 21:21:15 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 21:28:54 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 21:28:54 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 21:38:33 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 21:38:33 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 21:47:35 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 21:47:35 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 21:55:55 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 21:55:55 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 22:03:44 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 22:03:44 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 22:13:20 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 22:13:20 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 22:21:09 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 22:21:09 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 22:29:32 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 22:29:32 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 22:39:01 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 22:39:01 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 22:47:50 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 22:47:50 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 22:56:16 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 22:56:16 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 23:03:59 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 23:03:59 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 23:13:30 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 23:13:30 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 23:23:28 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 23:23:28 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 23:32:30 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 23:32:30 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 23:41:45 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 23:41:45 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 23:50:45 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 23:50:45 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 23:59:11 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 23:59:11 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0

Revision history for this message
Walt Corey (waltc) said : 		#11

I restarted an instance of the same image and displayed syslog and I have the following:

May 25 17:49:08 cor720 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
May 25 17:49:08 cor720 dhcpd: Wrote 0 deleted host decls to leases file.
May 25 17:49:08 cor720 dhcpd: Wrote 0 new dynamic host decls to leases file.
May 25 17:49:08 cor720 dhcpd: Wrote 0 leases to leases file.
May 25 17:49:08 cor720 dhcpd: Listening on LPF/eth0/00:1e:4f:b4:e2:b5/euca
May 25 17:49:08 cor720 dhcpd: Sending on LPF/eth0/00:1e:4f:b4:e2:b5/euca
May 25 17:49:08 cor720 dhcpd: Sending on Socket/fallback/fallback-net
May 25 17:49:08 cor720 avahi-daemon[1196]: Registering new address record for 192.168.3.100 on eth0.IPv4.
May 25 17:49:26 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 25 17:49:26 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 25 17:49:26 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 25 17:49:26 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0

I do not know what that initial warning means but I thought the first 5-6 lines might be revealing.

Revision history for this message
Walt Corey (waltc) said : 		#12

After having rebooted the cluster I can now log into the instance perfectly. Of course I lost all the data that first instances created for me but that will be the subject of another question. I will keep track of when I lose connectivity with this instance and send in the logs of what happened.

Torsten, I appreciate all your assistance on this.

Revision history for this message
Torsten Spindler (tspindler) said : 		#13

> Waiting for EC2 meta-data service

I suspect this is the problem you encountered. SSH was never started on
the instance as it is waiting for the EC2 meta-data service. I'm
surprised you could ever ssh to it, because the sshd was never brought
up.

Revision history for this message
Walt Corey (waltc) said : 		#14

But that was in the context of some error mounting the other virtual drive, which I think is kind of scary but is the subject of another question (shouldn't the /mnt mounted drive be formatted?). The other interesting thing is after I launched that last instance I had to reboot and the instance reappeared with both ip addresses in the describe-instances output. I saw only a single reference for 192.168.3.100 in the line:

May 24 16:48:27 cor720 avahi-daemon[1212]: Registering new address record for 192.168.3.100 on eth0.IPv4.

From that point forward it appeared all references to it were actually to the private address. So my concern is the statements in the log (no free leases available) in addition to the following:

May 24 18:40:55 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 18:40:55 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 18:50:22 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:57:64:09:5b via eth0
May 24 18:50:22 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:57:64:09:5b via eth0
May 24 18:50:51 cor720 dhclient: DHCPREQUEST of 192.168.0.6 on eth0 to 192.168.0.1 port 67
May 24 18:50:51 cor720 dhclient: DHCPNAK from 192.168.0.1
May 24 18:50:51 cor720 NetworkManager: <info> DHCP: device eth0 state changed bound -> expire
May 24 18:50:51 cor720 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
May 24 18:50:51 cor720 NetworkManager: <info> DHCP: device eth0 state changed expire -> preinit
May 24 18:50:51 cor720 dhcpd: DHCPDISCOVER from 00:1e:4f:b4:e2:b5 via eth0: network euca: no free leases

Does this tell you anything? Is the issue that the installed dhcp service to handle the cluster trying also to handle the 192.168.0.6 request. At one level I don't believe so as 192.168.0.1 is the wireless router but immediately following that is the event network euca: no free leases. So is this the point where the public address gets lost?

Revision history for this message
Walt Corey (waltc) said : 		#15

Note: 21:36:57 - I don't know why the public IP was dropped but here it is clearly dropped.
I noticed the subnet for euca is only 5-6 bits wide (I've forgotten exactly) but enough for 50 addresses as I recall I added.
The subnet mast for the router is 255.255.0.0, would this present a problem?

May 26 19:06:36 cor720 dhcpd: DHCPINFORM from 192.168.0.8 via eth0: unknown subnet for client address 192.168.0.8
May 26 19:06:36 cor720 dhcpd: DHCPINFORM from 192.168.0.8 via eth0: unknown subnet for client address 192.168.0.8
May 26 19:13:40 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 19:13:40 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 19:17:02 cor720 CRON[11100]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 26 19:21:37 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 19:21:37 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 19:30:24 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 19:30:24 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 19:39:27 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 19:39:27 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 19:48:17 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 19:48:17 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 19:48:17 cor720 dhclient: 7 bad udp checksums in 13 packets
May 26 19:57:20 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 19:57:20 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 20:04:57 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 20:04:57 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 20:14:55 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 20:14:55 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 20:17:01 cor720 CRON[17036]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 26 20:24:36 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 20:24:36 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 20:34:03 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 20:34:03 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 20:34:03 cor720 dhclient: 5 bad udp checksums in 5 packets
May 26 20:42:34 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 20:42:34 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 20:52:07 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 20:52:07 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 21:00:13 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 21:00:13 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 21:09:38 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 21:09:38 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 21:17:01 cor720 CRON[23041]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 26 21:17:31 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 21:17:31 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 21:17:31 cor720 dhclient: 5 bad udp checksums in 5 packets
May 26 21:23:41 cor720 kernel: [88837.880033] usb 1-6: new high speed USB device using ehci_hcd and address 7
May 26 21:23:41 cor720 kernel: [88838.020678] usb 1-6: configuration #1 chosen from 1 choice
May 26 21:23:41 cor720 kernel: [88838.020858] hub 1-6:1.0: USB hub found
May 26 21:23:41 cor720 kernel: [88838.020929] hub 1-6:1.0: 4 ports detected
May 26 21:26:16 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 21:26:16 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 21:33:57 cor720 dhcpd: Internet Systems Consortium DHCP Server V3.1.3
May 26 21:33:57 cor720 dhcpd: Copyright 2004-2009 Internet Systems Consortium.
May 26 21:33:57 cor720 dhcpd: All rights reserved.
May 26 21:33:57 cor720 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
May 26 21:33:57 cor720 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
May 26 21:33:57 cor720 dhcpd: Wrote 0 deleted host decls to leases file.
May 26 21:33:57 cor720 dhcpd: Wrote 0 new dynamic host decls to leases file.
May 26 21:33:57 cor720 dhcpd: Wrote 0 leases to leases file.
May 26 21:33:57 cor720 dhcpd: Listening on LPF/eth0/00:1e:4f:b4:e2:b5/euca
May 26 21:33:57 cor720 dhcpd: Sending on LPF/eth0/00:1e:4f:b4:e2:b5/euca
May 26 21:33:57 cor720 dhcpd: Sending on Socket/fallback/fallback-net
May 26 21:34:07 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 21:34:07 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 21:34:53 cor720 dhcpd: DHCPDISCOVER from d0:0d:4f:03:09:69 via eth0
May 26 21:34:53 cor720 dhcpd: DHCPOFFER on 172.19.1.3 to d0:0d:4f:03:09:69 via eth0
May 26 21:34:53 cor720 dhcpd: DHCPREQUEST for 172.19.1.3 (169.254.169.254) from d0:0d:4f:03:09:69 via eth0
May 26 21:34:53 cor720 dhcpd: DHCPACK on 172.19.1.3 to d0:0d:4f:03:09:69 via eth0
May 26 21:36:57 cor720 avahi-daemon[1175]: Withdrawing address record for 192.168.3.100 on eth0.
May 26 21:36:57 cor720 avahi-daemon[1175]: Withdrawing address record for 172.19.1.1 on eth0.
May 26 21:37:17 cor720 avahi-daemon[1175]: Registering new address record for 172.19.1.1 on eth0.IPv4.
May 26 21:37:17 cor720 dhcpd: Internet Systems Consortium DHCP Server V3.1.3
May 26 21:37:17 cor720 dhcpd: Copyright 2004-2009 Internet Systems Consortium.
May 26 21:37:17 cor720 dhcpd: All rights reserved.
May 26 21:37:17 cor720 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
May 26 21:37:17 cor720 dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in.
May 26 21:37:17 cor720 dhcpd: Wrote 0 deleted host decls to leases file.
May 26 21:37:17 cor720 dhcpd: Wrote 0 new dynamic host decls to leases file.
May 26 21:37:17 cor720 dhcpd: Wrote 0 leases to leases file.
May 26 21:37:17 cor720 dhcpd: Listening on LPF/eth0/00:1e:4f:b4:e2:b5/euca
May 26 21:37:17 cor720 dhcpd: Sending on LPF/eth0/00:1e:4f:b4:e2:b5/euca
May 26 21:37:17 cor720 dhcpd: Sending on Socket/fallback/fallback-net
May 26 21:37:17 cor720 avahi-daemon[1175]: Registering new address record for 192.168.3.100 on eth0.IPv4.
May 26 21:37:37 cor720 dhcpd: DHCPDISCOVER from d0:0d:45:b3:08:35 via eth0
May 26 21:37:37 cor720 dhcpd: DHCPOFFER on 172.19.1.3 to d0:0d:45:b3:08:35 via eth0
May 26 21:37:37 cor720 dhcpd: DHCPREQUEST for 172.19.1.3 (169.254.169.254) from d0:0d:45:b3:08:35 via eth0
May 26 21:37:37 cor720 dhcpd: DHCPACK on 172.19.1.3 to d0:0d:45:b3:08:35 via eth0
May 26 21:39:38 cor720 avahi-daemon[1175]: Withdrawing address record for 192.168.3.100 on eth0.
May 26 21:39:38 cor720 avahi-daemon[1175]: Withdrawing address record for 172.19.1.1 on eth0.
May 26 21:40:50 cor720 kernel: [89867.675957] usb 1-6: USB disconnect, address 7
May 26 21:40:52 cor720 kernel: [89869.237858] usb 1-8: USB disconnect, address 6
May 26 21:42:22 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 21:42:22 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 21:51:42 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 21:51:42 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 21:51:43 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 26 21:51:43 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 21:51:43 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 26 21:51:43 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 22:09:16 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 22:09:16 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 22:09:17 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 26 22:09:17 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 22:09:17 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 26 22:09:17 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 22:17:01 cor720 CRON[30007]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 26 22:26:56 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 22:26:56 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 22:26:57 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 26 22:26:57 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 22:26:57 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 26 22:26:57 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 22:44:30 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 22:44:30 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 22:44:31 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 26 22:44:31 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 22:44:31 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 26 22:44:31 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:02:02 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 23:02:02 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:02:03 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 26 23:02:03 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:02:03 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 26 23:02:03 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:17:01 cor720 CRON[3797]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 26 23:19:38 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 23:19:38 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:19:39 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 26 23:19:39 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:19:39 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 26 23:19:39 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:37:21 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 23:37:21 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:37:22 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 26 23:37:22 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:37:22 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 26 23:37:22 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:54:55 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 26 23:54:55 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:54:56 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 26 23:54:56 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 26 23:54:56 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 26 23:54:56 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 00:12:31 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 00:12:31 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 00:12:32 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 00:12:32 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 00:12:32 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 00:12:32 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 00:17:01 cor720 CRON[9848]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 27 00:30:08 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 00:30:08 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 00:30:09 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 00:30:09 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 00:30:09 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 00:30:09 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 00:47:40 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 00:47:40 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 00:47:41 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 00:47:41 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 00:47:41 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 00:47:41 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:05:21 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 01:05:21 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:05:23 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 01:05:23 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:05:23 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 01:05:23 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:17:01 cor720 CRON[15881]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 27 01:22:57 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 01:22:57 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:22:59 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 01:22:59 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:22:59 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 01:22:59 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:40:43 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 01:40:43 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:40:44 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 01:40:44 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:40:44 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 01:40:44 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:58:15 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 01:58:15 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:58:16 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 01:58:16 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 01:58:16 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 01:58:16 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 02:16:04 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 02:16:04 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 02:16:05 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 02:16:05 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 02:16:05 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 02:16:05 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 02:17:01 cor720 CRON[21804]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 27 02:33:36 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 02:33:36 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 02:33:37 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 02:33:37 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 02:33:37 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 02:33:37 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 02:51:24 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 02:51:24 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 02:51:25 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 02:51:25 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 02:51:25 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 02:51:25 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 03:08:57 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 03:08:57 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 03:08:58 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 03:08:58 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 03:08:58 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 03:08:58 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 03:17:01 cor720 CRON[27754]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 27 03:22:48 cor720 dhcpd: DHCPDISCOVER from a4:ba:db:f9:3d:aa via eth0: network euca: no free leases
May 27 03:22:48 cor720 dhcpd: DHCPREQUEST for 192.168.0.12 (192.168.0.1) from a4:ba:db:f9:3d:aa via eth0: ignored (not authoritative).
May 27 03:24:03 cor720 dhcpd: DHCPDISCOVER from 00:11:d9:01:9b:49 via eth0: network euca: no free leases
May 27 03:24:03 cor720 dhcpd: DHCPDISCOVER from 00:11:d9:17:cd:0f via eth0: network euca: no free leases
May 27 03:24:05 cor720 dhcpd: DHCPREQUEST for 192.168.0.5 (192.168.0.1) from 00:11:d9:01:9b:49 via eth0: ignored (not authoritative).
May 27 03:24:05 cor720 dhcpd: DHCPREQUEST for 192.168.0.4 (192.168.0.1) from 00:11:d9:17:cd:0f via eth0: ignored (not authoritative).
May 27 03:26:34 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 03:26:34 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 03:26:35 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 03:26:35 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 03:26:35 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 03:26:35 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 03:44:09 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 03:44:09 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 03:44:10 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 03:44:10 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 03:44:10 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 03:44:10 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 03:51:35 cor720 dhclient: DHCPREQUEST of 192.168.0.6 on eth0 to 192.168.0.1 port 67
May 27 03:51:35 cor720 dhclient: DHCPNAK from 192.168.0.1
May 27 03:51:35 cor720 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
May 27 03:51:35 cor720 dhcpd: DHCPDISCOVER from 00:1e:4f:b4:e2:b5 via eth0: network euca: no free leases
May 27 03:51:35 cor720 dhclient: DHCPOFFER of 192.168.0.6 from 192.168.0.1
May 27 03:51:35 cor720 dhclient: DHCPREQUEST of 192.168.0.6 on eth0 to 255.255.255.255 port 67
May 27 03:51:35 cor720 dhcpd: DHCPREQUEST for 192.168.0.6 (192.168.0.1) from 00:1e:4f:b4:e2:b5 via eth0: ignored (not authoritative).
May 27 03:51:35 cor720 dhclient: DHCPACK of 192.168.0.6 from 192.168.0.1
May 27 03:51:35 cor720 NetworkManager: <info> DHCP: device eth0 state changed bound -> expire
May 27 03:51:35 cor720 NetworkManager: <info> DHCP: device eth0 state changed expire -> preinit
May 27 03:51:35 cor720 NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound
May 27 03:51:35 cor720 dhclient: bound to 192.168.0.6 -- renewal in 34687 seconds.
May 27 03:51:35 cor720 NetworkManager: <info> address 192.168.0.6
May 27 03:51:35 cor720 NetworkManager: <info> prefix 16 (255.255.0.0)
May 27 03:51:35 cor720 NetworkManager: <info> gateway 192.168.0.1
May 27 03:51:35 cor720 NetworkManager: <info> nameserver '192.168.0.1'
May 27 04:01:46 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 04:01:46 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:01:47 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 04:01:47 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:01:47 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 04:01:47 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:17:01 cor720 CRON[1326]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 27 04:19:20 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 04:19:20 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:19:21 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 04:19:21 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:19:21 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 04:19:21 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:36:11 cor720 dhcpd: DHCPDISCOVER from 00:0d:a2:01:38:7b via eth0: network euca: no free leases
May 27 04:36:11 cor720 dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.1) from 00:0d:a2:01:38:7b via eth0: ignored (not authoritative).
May 27 04:37:09 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 04:37:09 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:37:10 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 04:37:10 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:37:10 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 04:37:10 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:54:48 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 04:54:48 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:54:49 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 04:54:49 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 04:54:49 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 04:54:49 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 05:12:25 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 05:12:25 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 05:12:26 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 05:12:26 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 05:12:26 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 05:12:26 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 05:17:01 cor720 CRON[7740]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 27 05:30:05 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 05:30:05 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 05:30:06 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 05:30:06 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 05:30:06 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 05:30:06 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 05:47:42 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 05:47:42 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 05:47:43 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 05:47:43 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 05:47:43 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 05:47:43 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:05:21 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 06:05:21 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:05:22 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 06:05:22 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:05:22 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 06:05:22 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:07:23 cor720 dhcpd: DHCPREQUEST for 192.168.0.11 from 60:fb:42:e0:73:10 via eth0: ignored (not authoritative).
May 27 06:07:25 cor720 avahi-daemon[1175]: Invalid query packet.
May 27 06:08:54 cor720 avahi-daemon[1175]: last message repeated 2 times
May 27 06:17:01 cor720 CRON[13642]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 27 06:22:59 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 06:22:59 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:23:00 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 06:23:00 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:23:00 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 06:23:00 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:25:01 cor720 CRON[14322]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
May 27 06:40:43 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 06:40:43 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:40:44 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 06:40:44 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:40:44 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 06:40:44 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:58:15 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 06:58:15 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:58:16 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 06:58:16 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:58:16 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 06:58:16 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 06:59:14 cor720 dhcpd: DHCPREQUEST for 192.168.0.8 from 00:0c:29:4b:38:02 via eth0: unknown lease 192.168.0.8.
May 27 06:59:14 cor720 dhcpd: DHCPREQUEST for 192.168.0.8 from 00:0c:29:4b:38:02 via eth0: unknown lease 192.168.0.8.
May 27 07:15:47 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 07:15:47 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 07:15:48 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 07:15:48 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 07:15:48 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 07:15:48 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 07:17:01 cor720 CRON[19565]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 27 07:30:01 cor720 CRON[20854]: (root) CMD (start -q anacron || :)
May 27 07:30:01 cor720 anacron[20857]: Anacron 2.3 started on 2010-05-27
May 27 07:30:01 cor720 anacron[20857]: Will run job `cron.daily' in 5 min.
May 27 07:30:01 cor720 anacron[20857]: Jobs will be executed sequentially
May 27 07:33:22 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 07:33:22 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 07:33:23 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 07:33:23 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 07:33:23 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 07:33:23 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 07:35:01 cor720 anacron[20857]: Job `cron.daily' started
May 27 07:35:01 cor720 anacron[21287]: Updated timestamp for job `cron.daily' to 2010-05-27
May 27 07:51:02 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:4b:fe:08:c6 via eth0
May 27 07:51:02 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 07:51:03 cor720 dhcpd: DHCPDISCOVER from d0:0d:4b:fe:08:c6 via eth0
May 27 07:51:03 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0
May 27 07:51:03 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:4b:fe:08:c6 via eth0
May 27 07:51:03 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:4b:fe:08:c6 via eth0

Revision history for this message
Walt Corey (waltc) said : 		#16

More information...consider this:
May 28 18:26:19 cor720 NetworkManager: <info> Maximum Segment Size (MSS): 0
May 28 18:26:19 cor720 NetworkManager: <info> Static Route: 10.0.0.0/8 Next Hop: 10.0.0.0
May 28 18:26:19 cor720 NetworkManager: <info> Static Route: 192.168.251.0/24 Next Hop: 192.168.251.0
May 28 18:26:19 cor720 NetworkManager: <info> Static Route: 192.168.22.0/24 Next Hop: 192.168.22.0
May 28 18:26:19 cor720 NetworkManager: <info> Static Route: 192.168.23.0/24 Next Hop: 192.168.23.0
May 28 18:26:19 cor720 NetworkManager: <info> Static Route: 192.168.24.0/24 Next Hop: 192.168.24.0
May 28 18:26:19 cor720 NetworkManager: <info> Static Route: 63.131.134.0/24 Next Hop: 63.131.134.0
May 28 18:26:19 cor720 NetworkManager: <info> Static Route: 208.111.81.157/32 Next Hop: 208.111.81.157
May 28 18:26:19 cor720 NetworkManager: <info> Static Route: 208.111.81.159/32 Next Hop: 208.111.81.159
May 28 18:26:19 cor720 NetworkManager: <info> Static Route: 72.20.25.16/32 Next Hop: 72.20.25.16
May 28 18:26:19 cor720 NetworkManager: <info> Static Route: 209.249.222.54/32 Next Hop: 209.249.222.54
May 28 18:26:19 cor720 NetworkManager: <info> Internal IP4 DNS: 10.50.33.21
May 28 18:26:19 cor720 NetworkManager: <info> Internal IP4 DNS: 10.5.4.1
May 28 18:26:19 cor720 NetworkManager: <info> DNS Domain: 'na.global.ad'
May 28 18:26:19 cor720 NetworkManager: <info> Login Banner:
May 28 18:26:19 cor720 NetworkManager: <info> -----------------------------------------
May 28 18:26:19 cor720 NetworkManager: <info> All data on the Monster Worldwide VPN Service is privileged and confidential. It is a criminal offense to obtain access to data (or damage, delete, alter or insert data) without authorization. #015#012#015#012Your PC is now connected to the Monster Worldwide WAN through the Maynard Concentrator and is subject to the usage policy
May 28 18:26:19 cor720 NetworkManager: <info> -----------------------------------------
May 28 18:26:19 cor720 vpnc[3537]: can't open pidfile /var/run/vpnc/pid for writing
May 28 18:26:20 cor720 NetworkManager: <info> VPN connection 'Monster (Maynard)' (IP Config Get) complete.
May 28 18:26:20 cor720 NetworkManager: <info> Policy set 'Monster (Maynard)' (tun0) as default for routing and DNS.
May 28 18:26:20 cor720 vmnetBridge: RTM_NEWROUTE: index:5
May 28 18:26:20 cor720 NetworkManager: <info> VPN plugin state changed: 4
May 28 18:26:20 cor720 nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.
May 28 18:27:36 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:30:cf:06:f7 via eth0
May 28 18:27:36 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:30:cf:06:f7 via eth0
May 28 18:28:26 cor720 vpnc[3537]: select: Interrupted system call
May 28 18:28:26 cor720 vpnc[3537]: terminated by signal: 15
May 28 18:28:26 cor720 avahi-daemon[1175]: Withdrawing address record for 172.19.1.1 on eth0.
May 28 18:28:26 cor720 avahi-daemon[1175]: Withdrawing address record for 192.168.3.100 on eth0.
May 28 18:28:27 cor720 NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
May 28 18:28:27 cor720 vmnetBridge: RTM_NEWROUTE: index:2

There was a, likely, corresponding loss of signal to the open connection to the instance:
When I say it I tried to log on again.
I tried restarting eucalyptus on the cluster as well as the eucalyptus-cc
ubuntu@ip-172-19-1-2:~$ Write failed: Broken pipe
walt@cor720:~$ ssh -i .euca/mykey.priv ubuntu@192.168.3.100
ssh: connect to host 192.168.3.100 port 22: Connection timed out
walt@cor720:~$ ssh -i .euca/mykey.priv ubuntu@192.168.3.100
ssh: connect to host 192.168.3.100 port 22: Connection timed out
walt@cor720:~$

I looked at the tail end of the console log and found this:
I also tried rebooting the instance:

Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
cloud-init running: Sat, 29 May 2010 01:29:42 +0000. up 9.06 seconds

waiting for metadata service at http://169.254.169.254/2009-04-04/meta-data/instance-id
  01:29:44 [ 1/100]: url error [timed out]
  01:29:47 [ 2/100]: url error [timed out]
  01:29:50 [ 3/100]: url error [timed out]
  01:29:51 [ 4/100]: url error [[Errno 113] No route to host]
  01:29:54 [ 5/100]: url error [timed out]
  01:29:57 [ 6/100]: url error [timed out]
  01:30:01 [ 7/100]: url error [timed out]
  01:30:05 [ 8/100]: url error [timed out]
  01:30:09 [ 9/100]: url error [timed out]
  01:30:13 [10/100]: url error [timed out]
  01:30:17 [11/100]: url error [timed out]
  01:30:22 [12/100]: url error [timed out]
  01:30:27 [13/100]: url error [timed out]
  01:30:32 [14/100]: url error [timed out]
  01:30:37 [15/100]: url error [timed out]
  01:30:42 [16/100]: url error [timed out]
  01:30:48 [17/100]: url error [timed out]
  01:30:54 [18/100]: url error [timed out]
  01:31:00 [19/100]: url error [[Errno 113] No route to host]
  01:31:06 [20/100]: url error [timed out]
  01:31:12 [21/100]: url error [timed out]
  01:31:19 [22/100]: url error [timed out]

The system log on the cc shows:
May 28 21:23:47 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:30:cf:06:f7 via eth0
May 28 21:23:47 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:30:cf:06:f7 via eth0
May 28 21:23:47 cor720 dhcpd: DHCPDISCOVER from d0:0d:30:cf:06:f7 via eth0
May 28 21:23:47 cor720 dhcpd: DHCPOFFER on 172.19.1.2 to d0:0d:30:cf:06:f7 via eth0
May 28 21:23:47 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 (169.254.169.254) from d0:0d:30:cf:06:f7 via eth0
May 28 21:23:47 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:30:cf:06:f7 via eth0
May 28 21:24:16 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:30:cf:06:f7 via eth0
May 28 21:24:16 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:30:cf:06:f7 via eth0
May 28 21:27:47 cor720 init: uec-component-listener main process (3949) killed by TERM signal
May 28 21:28:47 cor720 init: uec-component-listener main process (22579) killed by TERM signal
May 28 21:29:45 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:30:cf:06:f7 via eth0
May 28 21:29:45 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:30:cf:06:f7 via eth0

The instance, while continuing to show a running state, never shows a reestablished IP address pair
RESERVATION r-4481087B admin default
INSTANCE i-30CF06F7 emi-DEF41072 0.0.0.0 0.0.0.0 running mykey 0 m1.large 1970-01-01T00:00:00.65Z cluster1 eki-F52010F2 eri-0960114A

Revision history for this message
Walt Corey (waltc) said : 		#17

Where the system log showed component listener stopped I restart it.

Why where the instance shows running, and it looks like the 182.19.1.2 address is re-acquired does it not resynchronize?

Is this a bug. It seems awfully frail.

Revision history for this message
Torsten Spindler (tspindler) said : 		#18

Is it so that your CC runs NetworkManager on the device that serves your cloud? I'm pretty sure this would be a completely untested scenario.

Revision history for this message
Walt Corey (waltc) said : 		#19

This goes to a question I initially asked that nobody bothered to answer, what is the reason the cluster configuration, all components but node controller, need to be on a separate physical server? It seems to me the physical requirements are such that there would be an awful lot of wasted resources if it demanded a standalone dedicated server.

I believe the only requirements specified (aside from the unexplained use case of UES) is a segment of IP addresses nothing else is using. This is did. In fact, I discovered it is not simply a case of a range of addresses nothing else is using but, rather, a separate subnet, i.e. not 192.168.0.xxx but 192.168.3.xxx).

As in that last set of information where I discovered what prompted the problem, I started a vpn session to, as it happened, my office. Certainly when I do that existing sessions stop, like whatever is in my browser, my email program etc, for the duration of the vpn session. Once that session is disconnected, my browser works as well as the uninterrupted instance of my mail program.

So I am not too disappointed, surprised perhaps, that while a vpn session is active I loss connectivity to my node controller, as I do to my email provider etc, but once the vpn connection is disconnected the connection to the running instances is hopelessly lost. This is functionally no different than a transient loss of the cc.

If a transient loss of contact between a cc and a node controller causes all running instances to become hopelessly detached, it is a bug. It should be treated as a bug and filed as a bug.

You know the Eucalyptus software way better than I do. What do you think? If you do not feel it is a bug, would you explain why it's not a bug. If you feel it is a bug would you interface with Eucalyptus or whoever on the UEC side of things. Now I have a better idea of what is causing this I would be happy to provide whatever documentation is necessary.

Thanks,
Walt

Revision history for this message
Torsten Spindler (tspindler) said : 		#20

> This goes to a question I initially asked that nobody bothered to
> answer, what is the reason the cluster configuration, all components but
> node controller, need to be on a separate physical server? It seems to
> me the physical requirements are such that there would be an awful lot
> of wasted resources if it demanded a standalone dedicated server.

The original reason for this requirement seems to be that the EBS
volumes can only be attached from the SC to the instances if they are on
different systems. This is a limitation of the ATA over Ethernet
protocol used for this.

> I believe the only requirements specified (aside from the unexplained
> use case of UES) is a segment of IP addresses nothing else is using.
> This is did. In fact, I discovered it is not simply a case of a range of
> addresses nothing else is using but, rather, a separate subnet, i.e. not
> 192.168.0.xxx but 192.168.3.xxx).

I have several clouds seen where the public IP is merely a range, not a
subnet and it worked fine. But care must be taken that the public IP
addresses are not offered by a DHCP server.

...
> If a transient loss of contact between a cc and a node controller causes
> all running instances to become hopelessly detached, it is a bug. It
> should be treated as a bug and filed as a bug.

Sure, I see you filed a bug on this and I'm interested in seeing the
developers thought on this scenario as well.

> You know the Eucalyptus software way better than I do. What do you think?

I believe that the use of NetworkManager in combination with vpn on the
front end (if I got this right) is not tested at all.

> If you do not feel it is a bug, would you explain why it's not a bug. If
> you feel it is a bug would you interface with Eucalyptus or whoever on the
> UEC side of things. Now I have a better idea of what is causing this I would
> be happy to provide whatever documentation is necessary.

No need for me to interfere with the developers look at your bug. Good
luck with getting it resolved!

Revision history for this message
Walt Corey (waltc) said : 		#21

Thanks for your response Torsten,

Isn't it true that some have come up with a single server environment but in that mode only System networking, as opposed to Managed or ManagedNVlan would be supported....no matter. I was totally good with a dedicated server for the node. It has 50% more memory and the appearance of double the CPU.

This is where I will appear ignorant. Isn't Network Manager merely the vehicle to configure and manage the ports? Granted, on the Desktop images there are icons and panel apps but don't the same functions need to be performed on a server configuration?

I did consider waiting/hoping you would determine the behavior of my cc, for whatever reason, was inappropriate, and convert this to a bug thinking it was more likely to get taken seriously that way. Then I thought perhaps it was unreasonable for me to expect you to file it so I went ahead and did it. Certainly it might be very logical reasons why that functionality can not coexist in a desktop or otherwise shared environment. I just haven't seen or heard of a good reason yet.

I hope the conclusion is there really is no reason why a desktop, or other shared environment, couldn't handle the functions of everything but node controller. I would hope this is merely a resiliency issue and is opened and fixed before 10.10.

Revision history for this message
Walt Corey (waltc) said : 		#22

Hi, I have a related question that we never actually addressed.
I have another instance that had been running for days that just went 'deaf'. My question is, where it appears the instance is actually still running, how can I re-establish a route to it and reconnect?

Thanks,
Walt

Revision history for this message
Walt Corey (waltc) said : 		#23

What I discovered, which means there are several paths to this problem, is the private address, in this case, remained valid. I can connect via the private address.

I tried to connect then release with the intent of connect the original ip address of 192.168.3.100 but in both cases got the error "Address: Permission denied while trying to release address: 192.168.3.100"

The same error occurred when prefixed by sudo.

Revision history for this message
Dimitri (deathwash) said : 		#24

Hi WaltC

I have had a similar issue trying to release a public IP from an instance.
did you ever get it solved?

now i'm trying to add more public IP's to my cloud, but after adding VNET_PUBLICIPS "xxxx" to the config file, it is not picked up by eucalyptus ... they suggest CC clean=1 restart, but i'm afraid all my running (in production) VM's will lose connection and be gone forever :-(

any tips would be welcome :-)

Revision history for this message
Walt Corey (waltc) said : 		#25

Hi DImitri,
   I hate to say this because I am sure there is an unpublished or published but not advertised quick method of doing this, i.e. euca-config (or maybe it's euca-conf) but I just went to UEC 2.0 and even though both machines (this time I added a separate cc machine rather than using my desktop, once I reinstalled the NC (for a separate reason) the CC no longer could talk to it. I ended up reinstalling both, in the following order because I believe order is important, the CC machine and, next, the node controller. That worked. Screwing around with trying to find a quick way wasn't quick and didn't work.

I hope that helps.

Revision history for this message
Walt Corey (waltc) said : 		#26

I am going to close this as 'solved' even though it never was.

Strictly speaking it does say to, in a 2 machine environment, to install the CC/SC/Cloud Controller on one instance of UServer and a NC on another. I did not see a good reason why I needed 3 machines, my desktop, a CC/SC/Cloud controller, and the node controller so I installed the CC/SC etc packages on my desktop. It worked, in a fashion, but I did have the aforementioned bugs.

For UEC 2.0 I have 3 machines.