Can not ssh into containers from Win

Steps to reproduce:

Create x-peer env with one peer on Win (7,8,10) and another on Linux
Try to ssh into containers from Linux - it works
Try to check env connectivity (telemetry) - it works
Try to ssh into containers from Win using ez-ssh or tray -  it fails with  "Container is not ready" or "Connection timed out" in opened shell.

Seems this problem is specific to Win p2p client.
P2P version tested: p2p Cloud project 4.0.0-RC14-56-g35f19b6. Packet version: 5 up to version 58

Retested with P2P: 4.0.0-RC14-58-g6274c9e. Packet version: 5
Same problem - can not ssh into container from Win7
SSH terminal windows opened and failed with Connection timed out error

@Dilshat can you try to ping RH from host (win7) machine?

After I restarted VM it started to work on Win7

@crioto RH is accessible from Win7 b/c I open SS UI by RH IP

Seems this problem is reproduced on any Win version: 7, 8, 10

Still can not ssh from Win7 to containers
Also now can not ssh into Win7 container from outside

p2p.txt

Win 8

The error reproduces on Win10, can not ssh into its containers. Can not ssh from it to remote containers

[INFO] 2016/07/14 05:39:43 Starting RPC Listener on 52523 port
[INFO] 2016/07/14 05:50:16 Generate MAC for TAP device: 06:f0:94:f5:6f:0e
[INFO] 2016/07/14 05:50:16 Looking for available network interfaces
[INFO] 2016/07/14 05:50:16 Interface Ethernet0: fe80::c104:1c6d:4b5d:e058/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet0: <IP_ADDRESS>/24. Type: Global Unicast. Saving
[INFO] 2016/07/14 05:50:16 Interface VirtualBox Host-Only Network: fe80::a962:539:f385:a049/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface VirtualBox Host-Only Network: <IP_ADDRESS>/24. Type: Global Unicast. Saving
[INFO] 2016/07/14 05:50:16 Interface Ethernet: fe80::d5a8:f785:587b:6a9b/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet: <IP_ADDRESS>/16. Type: Link Local Unicast. Ignoring
[INFO] 2016/07/14 05:50:16 Interface Ethernet 2: fe80::e013:3947:cc62:d09a/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet 2: <IP_ADDRESS>/16. Type: Link Local Unicast. Ignoring
[INFO] 2016/07/14 05:50:16 Interface Ethernet 3: fe80::8973:3fb:3c41:d97c/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet 3: <IP_ADDRESS>/16. Type: Link Local Unicast. Ignoring
[INFO] 2016/07/14 05:50:16 Interface Ethernet 4: fe80::396b:fa9c:625:593a/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet 4: <IP_ADDRESS>/16. Type: Link Local Unicast. Ignoring
[INFO] 2016/07/14 05:50:16 Interface Ethernet 5: fe80::287c:664d:da98:ebc8/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet 5: <IP_ADDRESS>/16. Type: Link Local Unicast. Ignoring
[INFO] 2016/07/14 05:50:16 Interface Ethernet 6: fe80::89e2:2429:8371:7f78/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet 6: <IP_ADDRESS>/16. Type: Link Local Unicast. Ignoring
[INFO] 2016/07/14 05:50:16 Interface Ethernet 7: fe80::941a:5009:be14:998a/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet 7: <IP_ADDRESS>/16. Type: Link Local Unicast. Ignoring
[INFO] 2016/07/14 05:50:16 Interface Ethernet 8: fe80::740e:4a2a:6d81:e632/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet 8: <IP_ADDRESS>/16. Type: Link Local Unicast. Ignoring
[INFO] 2016/07/14 05:50:16 Interface Ethernet 9: fe80::c03c:6bc4:2890:e7a/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet 9: <IP_ADDRESS>/16. Type: Link Local Unicast. Ignoring
[INFO] 2016/07/14 05:50:16 Interface Ethernet 10: fe80::64af:8b41:8802:492a/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Ethernet 10: <IP_ADDRESS>/16. Type: Link Local Unicast. Ignoring
[INFO] 2016/07/14 05:50:16 Interface Loopback Pseudo-Interface 1: ::1/128. Type: Loopback. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Loopback Pseudo-Interface 1: <IP_ADDRESS>/8. Type: Loopback. Ignoring
[INFO] 2016/07/14 05:50:16 Interface isatap.localdomain: fe80::5efe:c0a8:4181/128. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Local Area Connection* 3: 2001:0:9d38:6abd:3cd5:3f0e:614a:7d8c/64. Type: Global Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface Local Area Connection* 3: fe80::3cd5:3f0e:614a:7d8c/64. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 Interface isatap.{B9441BD9-F431-427F-A531-A21BD00E7196}: fe80::5efe:c0a8:3801/128. Type: Link Local Unicast. No IPv4
[INFO] 2016/07/14 05:50:16 2 interfaces were saved
[ERROR] 2016/07/14 05:50:16 Failed to parse TTL. Falling back to default value of 1 hour
[ERROR] 2016/07/14 05:50:16 Failed to parse provided TTL value: strconv.ParseInt: parsing "default": invalid syntax
[INFO] 2016/07/14 05:50:16 Traffic encryption is enabled. Key valid until 2016-07-14 06:50:16.8759833 -0700 PDT
[INFO] 2016/07/14 05:50:16 Started UDP Listener at port 55583
[INFO] 2016/07/14 05:50:16 DHT operating in CLIENT mode
[INFO] 2016/07/14 05:50:16 Connecting to a router dht1.subut.ai:6881
[INFO] 2016/07/14 05:50:17 Ready to peer discovery via dht1.subut.ai:6881 [<IP_ADDRESS>:6881]
[INFO] 2016/07/14 05:50:17 Handshaked. Starting listener
[INFO] 2016/07/14 05:50:17 Bootstraping via <IP_ADDRESS>:6881
[INFO] 2016/07/14 05:50:17 Received connection confirmation from router <IP_ADDRESS>:6881
[INFO] 2016/07/14 05:50:17 Received personal ID for this session: 743ee25c-49c1-11e6-865f-022d0fae0f03
[INFO] 2016/07/14 05:50:17 ID assigned. Continue
[INFO] 2016/07/14 05:50:17 Requesting IP
[INFO] 2016/07/14 05:50:17 Sending DHCP request
[INFO] 2016/07/14 05:50:17 Received DHCP Information
[INFO] 2016/07/14 05:50:17 Saving IP/Net data: <IP_ADDRESS>
[WARNING] 2016/07/14 05:50:18 Failed to load config: open C:/p2p/config.yaml: The system cannot find the path specified.
[INFO] 2016/07/14 05:50:18 Acquired control over TAP interface: Ethernet 10
[INFO] 2016/07/14 05:50:18 Local Area Network1 TAP Device created
[INFO] 2016/07/14 05:50:18 MAC: 00:ff:8:cd:91:8b
[INFO] 2016/07/14 05:50:18 Configuring Ethernet 10. IP: <IP_ADDRESS> Mask: <IP_ADDRESS>
[INFO] 2016/07/14 05:50:18 Executing: netsh interface ip set address "Ethernet 10" static <IP_ADDRESS> <IP_ADDRESS>
[INFO] 2016/07/14 05:50:18 Initializing new peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:50:18 Initializing new peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:50:18 Initializing new peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:50:19 Waiting network addresses for peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:50:19 Waiting network addresses for peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:50:19 Waiting network addresses for peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:50:19 Trying direct conection with peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:50:19 Trying direct conection with peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:50:19 Trying direct conection with peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:50:19 Setting endpoint for ff3de526-49c0-11e6-8fd0-022d0fae0f03 to <IP_ADDRESS>:48665
[INFO] 2016/07/14 05:50:19 Connected with ff3de526-49c0-11e6-8fd0-022d0fae0f03 over LAN
[INFO] 2016/07/14 05:50:19 Setting endpoint for 61165bad-49c1-11e6-805a-022d0fae0f03 to <IP_ADDRESS>:50598
[INFO] 2016/07/14 05:50:19 Connected with 61165bad-49c1-11e6-805a-022d0fae0f03 over LAN
[INFO] 2016/07/14 05:50:20 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:50:20 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:50:22 read udp4 <IP_ADDRESS>:54104-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:50:23 Connection with peer ff3de526-49c0-11e6-8fd0-022d0fae0f03 has been established
[INFO] 2016/07/14 05:50:23 Connection with peer 61165bad-49c1-11e6-805a-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:50:26 read udp4 <IP_ADDRESS>:58136-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:50:26 Direct connection with fde60727-49c0-11e6-8873-022d0fae0f03 failed
[INFO] 2016/07/14 05:50:26 Setting peer address as <IP_ADDRESS>:48806 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:50:26 Looking in a list of cached proxies
[INFO] 2016/07/14 05:50:26 Requesting proxy for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:50:26 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:50:27 Handshaking with proxy <IP_ADDRESS>:39823 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:50:27 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:50:27 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:50:28 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:50:34 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[INFO] 2016/07/14 05:50:35 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:50:36 Handshaking with proxy <IP_ADDRESS>:39823 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:50:36 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 38
[INFO] 2016/07/14 05:50:36 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:50:36 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:50:36 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:50:37 Handshaking with proxy <IP_ADDRESS>:39823 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:50:37 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 16
[INFO] 2016/07/14 05:50:37 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:50:38 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:50:48 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:50:48 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:50:49 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:50:49 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:50:49 Looking in a list of cached proxies
[INFO] 2016/07/14 05:50:49 Found cached forwarder
[INFO] 2016/07/14 05:50:50 Handshaking with proxy <IP_ADDRESS>:39823 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:50:50 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[ERROR] 2016/07/14 05:50:50 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:50:50 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:50:50 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 38
[INFO] 2016/07/14 05:50:50 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:50:50 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:50:50 61165bad-49c1-11e6-805a-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:50:50 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:50:51 Handshaking with proxy <IP_ADDRESS>:50160 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:50:51 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:50:51 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 38
[INFO] 2016/07/14 05:50:51 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:50:56 Peer fde60727-49c0-11e6-8873-022d0fae0f03: Peer fde60727-49c0-11e6-8873-022d0fae0f03 has been timed out
[INFO] 2016/07/14 05:50:56 Initializing new peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:50:57 Waiting network addresses for peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:50:57 Trying direct conection with peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:00 Received forwarder <IP_ADDRESS>:50160
[ERROR] 2016/07/14 05:51:00 read udp4 <IP_ADDRESS>:61135-><IP_ADDRESS>:48806: i/o timeout
[ERROR] 2016/07/14 05:51:02 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:02 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:03 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:51:03 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:51:03 ff3de526-49c0-11e6-8fd0-022d0fae0f03 already has <IP_ADDRESS>:39823 in a blacklist of proxies
[INFO] 2016/07/14 05:51:03 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:03 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:03 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:51:03 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:51:03 read udp4 <IP_ADDRESS>:61136-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:51:03 Direct connection with fde60727-49c0-11e6-8873-022d0fae0f03 failed
[INFO] 2016/07/14 05:51:03 Setting peer address as <IP_ADDRESS>:48806 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:04 Received forwarder <IP_ADDRESS>:50160
[ERROR] 2016/07/14 05:51:04 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:04 61165bad-49c1-11e6-805a-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:51:04 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:04 Found cached forwarder
[INFO] 2016/07/14 05:51:04 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:04 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:04 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 42
[INFO] 2016/07/14 05:51:04 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:04 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:04 Handshaking with proxy <IP_ADDRESS>:50160 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:04 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:05 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:51:05 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:05 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:05 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:51:09 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:10 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:10 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:51:15 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:15 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:15 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:51:17 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:17 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:17 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:17 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:51:18 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:18 Found cached forwarder
[INFO] 2016/07/14 05:51:18 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:18 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:18 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 42
[INFO] 2016/07/14 05:51:19 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:20 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:21 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:21 We've failed to receive any proxies within this period
[INFO] 2016/07/14 05:51:21 Initializing new peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:22 Waiting network addresses for peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:22 Trying direct conection with peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:51:25 read udp4 <IP_ADDRESS>:65252-><IP_ADDRESS>:50598: i/o timeout
[INFO] 2016/07/14 05:51:25 Direct connection with 61165bad-49c1-11e6-805a-022d0fae0f03 failed
[INFO] 2016/07/14 05:51:25 Setting peer address as <IP_ADDRESS>:50598 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:26 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:26 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:26 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:51:27 Handshaking with proxy <IP_ADDRESS>:39823 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:27 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[ERROR] 2016/07/14 05:51:27 Peer fde60727-49c0-11e6-8873-022d0fae0f03: Peer fde60727-49c0-11e6-8873-022d0fae0f03 has been timed out
[INFO] 2016/07/14 05:51:27 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 40
[INFO] 2016/07/14 05:51:27 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:27 Initializing new peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:28 Waiting network addresses for peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:28 Trying direct conection with peer: fde60727-49c0-11e6-8873-022d0fae0f03
[ERROR] 2016/07/14 05:51:31 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:31 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:31 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:31 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:51:31 ff3de526-49c0-11e6-8fd0-022d0fae0f03 already has <IP_ADDRESS>:50160 in a blacklist of proxies
[ERROR] 2016/07/14 05:51:31 read udp4 <IP_ADDRESS>:49521-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:51:32 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:32 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:35 read udp4 <IP_ADDRESS>:49522-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:51:35 Direct connection with fde60727-49c0-11e6-8873-022d0fae0f03 failed
[INFO] 2016/07/14 05:51:35 Setting peer address as <IP_ADDRESS>:48806 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:35 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:35 Requesting proxy for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:35 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:36 Handshaking with proxy <IP_ADDRESS>:50160 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:36 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:36 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:51:36 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:36 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:51:37 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: No proxy were received for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:37 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:37 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:39 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:51:39 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:51:40 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:51:40 61165bad-49c1-11e6-805a-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:51:40 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:40 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:41 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:41 Handshaking with proxy <IP_ADDRESS>:50160 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:41 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:41 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 17
[INFO] 2016/07/14 05:51:42 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:51:42 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: No proxy were received for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:43 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:43 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:51:48 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: No proxy were received for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:48 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:48 We've failed to receive any proxies within this period
[INFO] 2016/07/14 05:51:49 Initializing new peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:49 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:51:49 Waiting network addresses for peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:50 Trying direct conection with peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:50 Handshaking with proxy <IP_ADDRESS>:39823 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:50 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:51:51 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:51:51 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:51:51 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:51:53 read udp4 <IP_ADDRESS>:51910-><IP_ADDRESS>:48665: i/o timeout
[INFO] 2016/07/14 05:51:53 Direct connection with ff3de526-49c0-11e6-8fd0-022d0fae0f03 failed
[INFO] 2016/07/14 05:51:53 Setting peer address as <IP_ADDRESS>:48665 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:53 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:53 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:54 Received forwarder <IP_ADDRESS>:39823
[ERROR] 2016/07/14 05:51:54 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:51:54 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:54 Handshaking with proxy <IP_ADDRESS>:39823 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:54 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[ERROR] 2016/07/14 05:51:54 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:54 61165bad-49c1-11e6-805a-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:51:54 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 18
[INFO] 2016/07/14 05:51:55 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:51:55 Looking in a list of cached proxies
[INFO] 2016/07/14 05:51:55 Found cached forwarder
[INFO] 2016/07/14 05:51:55 Handshaking with proxy <IP_ADDRESS>:50160 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:51:55 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:51:55 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 17
[INFO] 2016/07/14 05:51:56 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:52:07 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:52:07 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:52:07 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:52:07 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:52:08 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:08 Found cached forwarder
[ERROR] 2016/07/14 05:52:08 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:52:08 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:08 Handshaking with proxy <IP_ADDRESS>:39823 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:08 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[ERROR] 2016/07/14 05:52:08 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:08 61165bad-49c1-11e6-805a-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:52:08 61165bad-49c1-11e6-805a-022d0fae0f03 already has <IP_ADDRESS>:50160 in a blacklist of proxies
[INFO] 2016/07/14 05:52:08 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 18
[INFO] 2016/07/14 05:52:09 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:09 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:09 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:52:13 Peer fde60727-49c0-11e6-8873-022d0fae0f03: Peer fde60727-49c0-11e6-8873-022d0fae0f03 has been timed out
[INFO] 2016/07/14 05:52:13 Initializing new peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:52:14 Waiting network addresses for peer: fde60727-49c0-11e6-8873-022d0fae0f03
[ERROR] 2016/07/14 05:52:14 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:14 Trying direct conection with peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:52:14 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:14 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:52:17 read udp4 <IP_ADDRESS>:55068-><IP_ADDRESS>:48806: i/o timeout
[ERROR] 2016/07/14 05:52:19 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:20 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:20 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:52:20 read udp4 <IP_ADDRESS>:55069-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:52:20 Direct connection with fde60727-49c0-11e6-8873-022d0fae0f03 failed
[INFO] 2016/07/14 05:52:20 Setting peer address as <IP_ADDRESS>:48806 for fde60727-49c0-11e6-8873-022d0fae0f03
[ERROR] 2016/07/14 05:52:21 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:52:21 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:21 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:21 Requesting proxy for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:52:21 Received forwarder <IP_ADDRESS>:39823
[ERROR] 2016/07/14 05:52:21 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:52:21 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:52:21 ff3de526-49c0-11e6-8fd0-022d0fae0f03 already has <IP_ADDRESS>:39823 in a blacklist of proxies
[INFO] 2016/07/14 05:52:21 Handshaking with proxy <IP_ADDRESS>:39823 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:52:21 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:52:22 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:52:22 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:22 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:22 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:52:22 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:22 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[INFO] 2016/07/14 05:52:23 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:23 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:23 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 37
[INFO] 2016/07/14 05:52:23 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:52:25 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:26 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:26 We've failed to receive any proxies within this period
[INFO] 2016/07/14 05:52:26 Initializing new peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:27 Waiting network addresses for peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:27 Trying direct conection with peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:52:30 read udp4 <IP_ADDRESS>:54178-><IP_ADDRESS>:50598: i/o timeout
[INFO] 2016/07/14 05:52:30 Direct connection with 61165bad-49c1-11e6-805a-022d0fae0f03 failed
[INFO] 2016/07/14 05:52:30 Setting peer address as <IP_ADDRESS>:50598 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:31 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:31 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:31 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:31 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:31 Handshaking with proxy <IP_ADDRESS>:50160 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:31 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:31 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 17
[INFO] 2016/07/14 05:52:32 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:32 Connection with peer 61165bad-49c1-11e6-805a-022d0fae0f03 has been established
[INFO] 2016/07/14 05:52:35 Received forwarder <IP_ADDRESS>:50160
[ERROR] 2016/07/14 05:52:35 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:52:35 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:52:36 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:36 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:52:36 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:36 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:36 Handshaking with proxy <IP_ADDRESS>:50160 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:52:36 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:36 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:52:37 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:52:37 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:52:41 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: No proxy were received for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:42 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:42 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:45 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:52:46 Handshaking with proxy <IP_ADDRESS>:39823 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:52:46 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:52:46 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 40
[INFO] 2016/07/14 05:52:47 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:52:47 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: No proxy were received for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:47 Connection with peer 61165bad-49c1-11e6-805a-022d0fae0f03 has been established
[INFO] 2016/07/14 05:52:47 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:47 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:52:52 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: No proxy were received for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:53 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:53 We've failed to receive any proxies within this period
[INFO] 2016/07/14 05:52:53 Initializing new peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:54 Waiting network addresses for peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:54 Trying direct conection with peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:52:57 read udp4 <IP_ADDRESS>:54181-><IP_ADDRESS>:48665: i/o timeout
[INFO] 2016/07/14 05:52:57 Direct connection with ff3de526-49c0-11e6-8fd0-022d0fae0f03 failed
[INFO] 2016/07/14 05:52:57 Setting peer address as <IP_ADDRESS>:48665 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:58 Looking in a list of cached proxies
[INFO] 2016/07/14 05:52:58 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:58 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:58 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:59 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:59 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:52:59 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 37
[ERROR] 2016/07/14 05:52:59 Peer fde60727-49c0-11e6-8873-022d0fae0f03: Peer fde60727-49c0-11e6-8873-022d0fae0f03 has been timed out
[INFO] 2016/07/14 05:52:59 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:52:59 Initializing new peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:52:59 Connection with peer ff3de526-49c0-11e6-8fd0-022d0fae0f03 has been established
[INFO] 2016/07/14 05:53:00 Waiting network addresses for peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:00 Trying direct conection with peer: fde60727-49c0-11e6-8873-022d0fae0f03
[ERROR] 2016/07/14 05:53:03 read udp4 <IP_ADDRESS>:54183-><IP_ADDRESS>:48806: i/o timeout
[ERROR] 2016/07/14 05:53:06 read udp4 <IP_ADDRESS>:55135-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:53:06 Direct connection with fde60727-49c0-11e6-8873-022d0fae0f03 failed
[INFO] 2016/07/14 05:53:06 Setting peer address as <IP_ADDRESS>:48806 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:07 Looking in a list of cached proxies
[INFO] 2016/07/14 05:53:07 Found cached forwarder
[INFO] 2016/07/14 05:53:07 Handshaking with proxy <IP_ADDRESS>:39823 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:07 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:53:08 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:53:08 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[ERROR] 2016/07/14 05:53:09 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Peer 61165bad-49c1-11e6-805a-022d0fae0f03 has been timed out
[INFO] 2016/07/14 05:53:09 Initializing new peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:53:10 Waiting network addresses for peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:53:10 Trying direct conection with peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:53:10 Setting endpoint for 61165bad-49c1-11e6-805a-022d0fae0f03 to <IP_ADDRESS>:50598
[INFO] 2016/07/14 05:53:10 Connected with 61165bad-49c1-11e6-805a-022d0fae0f03 over LAN
[INFO] 2016/07/14 05:53:11 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:53:11 Connection with peer 61165bad-49c1-11e6-805a-022d0fae0f03 has been established
[INFO] 2016/07/14 05:53:11 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:53:12 Handshaking with proxy <IP_ADDRESS>:39823 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:12 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:53:12 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:53:12 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:12 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[INFO] 2016/07/14 05:53:13 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:53:14 Handshaking with proxy <IP_ADDRESS>:39823 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:14 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:53:14 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 18
[INFO] 2016/07/14 05:53:14 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:21 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:53:22 Handshaking with proxy <IP_ADDRESS>:39823 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:53:22 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:53:22 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 16
[INFO] 2016/07/14 05:53:22 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:53:25 Received forwarder <IP_ADDRESS>:50160
[ERROR] 2016/07/14 05:53:26 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:53:26 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:27 Handshaking with proxy <IP_ADDRESS>:50160 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:27 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:53:27 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[ERROR] 2016/07/14 05:53:27 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:53:27 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:53:27 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:27 Looking in a list of cached proxies
[INFO] 2016/07/14 05:53:27 Found cached forwarder
[INFO] 2016/07/14 05:53:27 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[INFO] 2016/07/14 05:53:28 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:28 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:53:28 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 37
[INFO] 2016/07/14 05:53:28 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:28 Connection with peer ff3de526-49c0-11e6-8fd0-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:53:34 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:53:34 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:53:35 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:53:35 61165bad-49c1-11e6-805a-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:53:35 Looking in a list of cached proxies
[INFO] 2016/07/14 05:53:35 Found cached forwarder
[INFO] 2016/07/14 05:53:36 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:53:36 Handshaking with proxy <IP_ADDRESS>:50160 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:53:36 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:53:36 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 38
[INFO] 2016/07/14 05:53:36 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:53:49 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:53:49 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:53:49 Peer fde60727-49c0-11e6-8873-022d0fae0f03: Peer fde60727-49c0-11e6-8873-022d0fae0f03 has been timed out
[INFO] 2016/07/14 05:53:49 Received forwarder <IP_ADDRESS>:39823
[ERROR] 2016/07/14 05:53:49 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:53:49 61165bad-49c1-11e6-805a-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:53:49 Initializing new peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:50 Looking in a list of cached proxies
[INFO] 2016/07/14 05:53:50 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:53:50 Waiting network addresses for peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:50 Handshaking with proxy <IP_ADDRESS>:39823 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:50 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:53:50 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 18
[INFO] 2016/07/14 05:53:50 Trying direct conection with peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:51 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:51 Connection with peer ff3de526-49c0-11e6-8fd0-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:53:52 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03 has been timed out
[INFO] 2016/07/14 05:53:52 Initializing new peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:53 Waiting network addresses for peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:53 Trying direct conection with peer: ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:53 Setting endpoint for ff3de526-49c0-11e6-8fd0-022d0fae0f03 to <IP_ADDRESS>:48665
[INFO] 2016/07/14 05:53:53 Connected with ff3de526-49c0-11e6-8fd0-022d0fae0f03 over LAN
[ERROR] 2016/07/14 05:53:54 read udp4 <IP_ADDRESS>:60447-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:53:54 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:53:54 Connection with peer ff3de526-49c0-11e6-8fd0-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:53:55 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:53:55 Looking in a list of cached proxies
[INFO] 2016/07/14 05:53:55 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:53:57 read udp4 <IP_ADDRESS>:60449-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:53:57 Direct connection with fde60727-49c0-11e6-8873-022d0fae0f03 failed
[INFO] 2016/07/14 05:53:57 Setting peer address as <IP_ADDRESS>:48806 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:57 Looking in a list of cached proxies
[INFO] 2016/07/14 05:53:57 Found cached forwarder
[INFO] 2016/07/14 05:53:58 Handshaking with proxy <IP_ADDRESS>:50160 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:58 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:53:58 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:53:58 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:53:58 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:54:00 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:01 Looking in a list of cached proxies
[INFO] 2016/07/14 05:54:01 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:01 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:02 Handshaking with proxy <IP_ADDRESS>:50160 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:54:02 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:02 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:54:02 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:54:03 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[INFO] 2016/07/14 05:54:03 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:05 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:54:05 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:05 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 38
[INFO] 2016/07/14 05:54:05 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:54:06 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:06 Looking in a list of cached proxies
[INFO] 2016/07/14 05:54:06 We've failed to receive any proxies within this period
[INFO] 2016/07/14 05:54:07 Initializing new peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:07 Waiting network addresses for peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:08 Trying direct conection with peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:54:11 read udp4 <IP_ADDRESS>:58145-><IP_ADDRESS>:50598: i/o timeout
[INFO] 2016/07/14 05:54:11 Direct connection with 61165bad-49c1-11e6-805a-022d0fae0f03 failed
[INFO] 2016/07/14 05:54:11 Setting peer address as <IP_ADDRESS>:50598 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:11 Looking in a list of cached proxies
[INFO] 2016/07/14 05:54:11 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:11 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:11 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:12 Handshaking with proxy <IP_ADDRESS>:39823 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:12 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:12 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 40
[INFO] 2016/07/14 05:54:12 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:13 Connection with peer 61165bad-49c1-11e6-805a-022d0fae0f03 has been established
[INFO] 2016/07/14 05:54:16 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:17 Handshaking with proxy <IP_ADDRESS>:39823 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:54:17 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:17 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[ERROR] 2016/07/14 05:54:17 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:54:17 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:54:17 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:54:18 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:54:18 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:18 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:54:18 Looking in a list of cached proxies
[INFO] 2016/07/14 05:54:18 Found cached forwarder
[INFO] 2016/07/14 05:54:19 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:54:19 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:19 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 38
[INFO] 2016/07/14 05:54:19 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:54:26 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:27 Handshaking with proxy <IP_ADDRESS>:50160 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:27 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:27 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 17
[INFO] 2016/07/14 05:54:27 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:28 Connection with peer 61165bad-49c1-11e6-805a-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:54:31 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:54:31 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:54:32 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:32 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:54:32 ff3de526-49c0-11e6-8fd0-022d0fae0f03 already has <IP_ADDRESS>:50160 in a blacklist of proxies
[INFO] 2016/07/14 05:54:32 Looking in a list of cached proxies
[INFO] 2016/07/14 05:54:32 Found cached forwarder
[INFO] 2016/07/14 05:54:33 Handshaking with proxy <IP_ADDRESS>:39823 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:54:33 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:33 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 16
[INFO] 2016/07/14 05:54:33 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:54:39 Peer fde60727-49c0-11e6-8873-022d0fae0f03: Peer fde60727-49c0-11e6-8873-022d0fae0f03 has been timed out
[INFO] 2016/07/14 05:54:39 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:40 Initializing new peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:54:40 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:54:40 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:40 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 38
[INFO] 2016/07/14 05:54:40 Waiting network addresses for peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:54:40 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:54:41 Trying direct conection with peer: fde60727-49c0-11e6-8873-022d0fae0f03
[ERROR] 2016/07/14 05:54:44 read udp4 <IP_ADDRESS>:58147-><IP_ADDRESS>:48806: i/o timeout
[ERROR] 2016/07/14 05:54:47 read udp4 <IP_ADDRESS>:58150-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:54:47 Direct connection with fde60727-49c0-11e6-8873-022d0fae0f03 failed
[INFO] 2016/07/14 05:54:47 Setting peer address as <IP_ADDRESS>:48806 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:54:47 Looking in a list of cached proxies
[INFO] 2016/07/14 05:54:47 Found cached forwarder
[INFO] 2016/07/14 05:54:48 Handshaking with proxy <IP_ADDRESS>:39823 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:54:48 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:48 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:54:48 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:54:49 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:54:49 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Peer 61165bad-49c1-11e6-805a-022d0fae0f03 has been timed out
[INFO] 2016/07/14 05:54:50 Initializing new peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:50 Waiting network addresses for peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:51 Trying direct conection with peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:51 Setting endpoint for 61165bad-49c1-11e6-805a-022d0fae0f03 to <IP_ADDRESS>:50598
[INFO] 2016/07/14 05:54:51 Connected with 61165bad-49c1-11e6-805a-022d0fae0f03 over LAN
[INFO] 2016/07/14 05:54:51 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:54:51 Connection with peer 61165bad-49c1-11e6-805a-022d0fae0f03 has been established
[INFO] 2016/07/14 05:54:52 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:52 Handshaking with proxy <IP_ADDRESS>:39823 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:54:52 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:52 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[ERROR] 2016/07/14 05:54:53 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:54:53 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:54:53 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[ERROR] 2016/07/14 05:54:53 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:54:53 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:54:53 ff3de526-49c0-11e6-8fd0-022d0fae0f03 already has <IP_ADDRESS>:50160 in a blacklist of proxies
[INFO] 2016/07/14 05:54:53 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[INFO] 2016/07/14 05:54:54 Looking in a list of cached proxies
[INFO] 2016/07/14 05:54:54 Found cached forwarder
[INFO] 2016/07/14 05:54:54 Handshaking with proxy <IP_ADDRESS>:39823 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:54:54 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:54 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:54 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 16
[INFO] 2016/07/14 05:54:55 Handshaking with proxy <IP_ADDRESS>:39823 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:54:55 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:54:55 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 16
[INFO] 2016/07/14 05:54:55 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:54:56 Failed to parse introduction string: ¡8(¬Õ¡rÝ ¸ˆÚ7Z¦ëÙž[Àª¥1bÀâ»†÷eK2yBóé2NÒ½M{Ú¬Èeé¸0ÈúûÑa{ '}àpª
[INFO] 2016/07/14 05:55:02 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:03 Handshaking with proxy <IP_ADDRESS>:50160 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:03 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:03 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 38
[INFO] 2016/07/14 05:55:03 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:06 Received forwarder <IP_ADDRESS>:50160
[ERROR] 2016/07/14 05:55:07 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:55:07 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:55:07 Handshaking with proxy <IP_ADDRESS>:50160 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:55:07 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:07 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[ERROR] 2016/07/14 05:55:08 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:55:08 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:55:08 ff3de526-49c0-11e6-8fd0-022d0fae0f03 already has <IP_ADDRESS>:39823 in a blacklist of proxies
[INFO] 2016/07/14 05:55:08 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:55:08 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[INFO] 2016/07/14 05:55:08 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:08 Found cached forwarder
[INFO] 2016/07/14 05:55:09 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:55:09 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:09 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 39
[INFO] 2016/07/14 05:55:09 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:55:15 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:55:15 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:55:16 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:16 61165bad-49c1-11e6-805a-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:55:16 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:55:16 Handshaking with proxy <IP_ADDRESS>:39823 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:16 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:55:16 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 16
[INFO] 2016/07/14 05:55:17 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:55:21 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:55:21 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:55:22 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:22 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:55:22 ff3de526-49c0-11e6-8fd0-022d0fae0f03 already has <IP_ADDRESS>:50160 in a blacklist of proxies
[INFO] 2016/07/14 05:55:22 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:22 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:55:27 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: No proxy were received for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:55:28 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:28 Requesting proxy for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:55:29 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:55:29 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:55:29 Failed to handshake with 61165bad-49c1-11e6-805a-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:55:29 61165bad-49c1-11e6-805a-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:55:30 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:30 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:55:30 Peer fde60727-49c0-11e6-8873-022d0fae0f03: Peer fde60727-49c0-11e6-8873-022d0fae0f03 has been timed out
[INFO] 2016/07/14 05:55:30 Initializing new peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:55:30 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:31 Waiting network addresses for peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:55:31 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:55:31 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:31 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 38
[INFO] 2016/07/14 05:55:31 Trying direct conection with peer: fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:55:31 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:55:34 read udp4 <IP_ADDRESS>:53608-><IP_ADDRESS>:48806: i/o timeout
[ERROR] 2016/07/14 05:55:35 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:35 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:35 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:55:37 read udp4 <IP_ADDRESS>:53609-><IP_ADDRESS>:48806: i/o timeout
[INFO] 2016/07/14 05:55:37 Direct connection with fde60727-49c0-11e6-8873-022d0fae0f03 failed
[INFO] 2016/07/14 05:55:37 Setting peer address as <IP_ADDRESS>:48806 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:55:38 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:38 Found cached forwarder
[INFO] 2016/07/14 05:55:38 Handshaking with proxy <IP_ADDRESS>:39823 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:55:38 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:55:38 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:55:39 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[ERROR] 2016/07/14 05:55:40 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:41 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:41 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:42 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:55:42 Handshaking with proxy <IP_ADDRESS>:39823 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:55:42 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:55:43 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[INFO] 2016/07/14 05:55:43 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[ERROR] 2016/07/14 05:55:43 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:55:43 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:55:43 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[ERROR] 2016/07/14 05:55:44 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:44 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:50160 to a blacklist
[INFO] 2016/07/14 05:55:44 ff3de526-49c0-11e6-8fd0-022d0fae0f03 already has <IP_ADDRESS>:50160 in a blacklist of proxies
[INFO] 2016/07/14 05:55:44 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:44 Found cached forwarder
[INFO] 2016/07/14 05:55:45 Received forwarder <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:55:45 Handshaking with proxy <IP_ADDRESS>:39823 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:55:45 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:55:45 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 16
[INFO] 2016/07/14 05:55:45 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:55:46 Peer 61165bad-49c1-11e6-805a-022d0fae0f03: No proxy were received for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:46 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:46 We've failed to receive any proxies within this period
[INFO] 2016/07/14 05:55:47 Initializing new peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:47 Waiting network addresses for peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:48 Trying direct conection with peer: 61165bad-49c1-11e6-805a-022d0fae0f03
[ERROR] 2016/07/14 05:55:51 read udp4 <IP_ADDRESS>:53610-><IP_ADDRESS>:50598: i/o timeout
[INFO] 2016/07/14 05:55:51 Direct connection with 61165bad-49c1-11e6-805a-022d0fae0f03 failed
[INFO] 2016/07/14 05:55:51 Setting peer address as <IP_ADDRESS>:50598 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:51 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:51 Requesting proxy for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:52 Received forwarder <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:52 Handshaking with proxy <IP_ADDRESS>:50160 for 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:52 61165bad-49c1-11e6-805a-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:52 Proxy confirmation received from <IP_ADDRESS>:50598. Tunnel ID 17
[INFO] 2016/07/14 05:55:53 Sending handshake to 61165bad-49c1-11e6-805a-022d0fae0f03
[INFO] 2016/07/14 05:55:53 Connection with peer 61165bad-49c1-11e6-805a-022d0fae0f03 has been established
[INFO] 2016/07/14 05:55:56 Received forwarder <IP_ADDRESS>:50160
[ERROR] 2016/07/14 05:55:57 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[ERROR] 2016/07/14 05:55:57 Peer ff3de526-49c0-11e6-8fd0-022d0fae0f03: Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:55:57 Handshaking with proxy <IP_ADDRESS>:50160 for fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:55:57 fde60727-49c0-11e6-8873-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:58 Proxy confirmation received from <IP_ADDRESS>:48806. Tunnel ID 36
[ERROR] 2016/07/14 05:55:58 Failed to handshake with ff3de526-49c0-11e6-8fd0-022d0fae0f03 via proxy <IP_ADDRESS>:39823
[INFO] 2016/07/14 05:55:58 ff3de526-49c0-11e6-8fd0-022d0fae0f03 Adding forwarder <IP_ADDRESS>:39823 to a blacklist
[INFO] 2016/07/14 05:55:58 ff3de526-49c0-11e6-8fd0-022d0fae0f03 already has <IP_ADDRESS>:39823 in a blacklist of proxies
[INFO] 2016/07/14 05:55:58 Sending handshake to fde60727-49c0-11e6-8873-022d0fae0f03
[INFO] 2016/07/14 05:55:58 Looking in a list of cached proxies
[INFO] 2016/07/14 05:55:58 Found cached forwarder
[INFO] 2016/07/14 05:55:58 Connection with peer fde60727-49c0-11e6-8873-022d0fae0f03 has been established
[INFO] 2016/07/14 05:55:59 Handshaking with proxy <IP_ADDRESS>:50160 for ff3de526-49c0-11e6-8fd0-022d0fae0f03
[INFO] 2016/07/14 05:55:59 ff3de526-49c0-11e6-8fd0-022d0fae0f03 handshaked with proxy <IP_ADDRESS>:50160
[INFO] 2016/07/14 05:55:59 Proxy confirmation received from <IP_ADDRESS>:48665. Tunnel ID 38
[INFO] 2016/07/14 05:55:59 Sending handshake to ff3de526-49c0-11e6-8fd0-022d0fae0f03

C:\Users\d>ping <IP_ADDRESS>
Pinging <IP_ADDRESS> with 32 bytes of data:
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64
Ping statistics for <IP_ADDRESS>:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

ping ssh and scp works inside env

On Win10 ssh started working with Win client version p2p Cloud project 4.0.0-RC14-79-g7e7ca7c. Packet version: 5

ipconfig_all.txt

C:\Subutai\bin>ping <IP_ADDRESS>
Pinging <IP_ADDRESS> with 32 bytes of data:
Reply from <IP_ADDRESS>: bytes=32 time=213ms TTL=64
Request timed out.
Reply from <IP_ADDRESS>: bytes=32 time=283ms TTL=64
Request timed out.
Ping statistics for <IP_ADDRESS>:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 213ms, Maximum = 283ms, Average = 248ms
C:\Subutai\bin>

C:\Users\Dilshat>p2p debug
DEBUG INFO:
Number of gouroutines: 19
Instances information:
Hash: swarm-acfcbca5-22b7-4723-8334-c3a63a1539b0
ID: dd4ece8d-4a7d-11e6-8e8d-022d0fae0f03
Interface Local Area Network1, HW Addr: 00:ff:12:57:98:1c, IP: <IP_ADDRESS>
Peers:
--- fd09d47c-4a7c-11e6-8a5e-022d0fae0f03 ---
HWAddr: 06:65:02:7a:1d:8a
IP: <IP_ADDRESS>
Endpoint: <IP_ADDRESS>:36995
Peer Address: <IP_ADDRESS>:36995
Proxy ID: 0
--- End of fd09d47c-4a7c-11e6-8a5e-022d0fae0f03 ---
--- 0568c747-4a7d-11e6-8400-022d0fae0f03 ---
HWAddr: 06:cf:45:fa:a7:2b
IP: <IP_ADDRESS>
Endpoint: <IP_ADDRESS>:46644
Peer Address: <IP_ADDRESS>:46644
Proxy ID: 0
--- End of 0568c747-4a7d-11e6-8400-022d0fae0f03 ---
--- fcf4fd1e-4a7c-11e6-8896-022d0fae0f03 ---
HWAddr: 06:4b:50:4d:37:15
IP: <IP_ADDRESS>
Endpoint: <IP_ADDRESS>:39823
Peer Address: <IP_ADDRESS>:43851
Proxy ID: 69
--- End of fcf4fd1e-4a7c-11e6-8896-022d0fae0f03 ---
C:\Users\Dilshat>p2p status
swarm-acfcbca5-22b7-4723-8334-c3a63a1539b0 | <IP_ADDRESS>
fd09d47c-4a7c-11e6-8a5e-022d0fae0f03|<IP_ADDRESS>|State:Connected|
0568c747-4a7d-11e6-8400-022d0fae0f03|<IP_ADDRESS>|State:Connected|
fcf4fd1e-4a7c-11e6-8896-022d0fae0f03|<IP_ADDRESS>|State:Connected|

@Dilshat is your connection wireless?

@Dilshat also, does it reproduces every time?

@crioto connection is wireless.
On Win 10 ping stabilized after p2p service restart but on Win8 it didnt

Can not connect to container on x-peer after ~5 hours after creation. Created x-peer environment with 2 containers on win peers (one on phys. win8.1 - wireless, another on win-VMware-win10 - wired). After creation could connect with ssh to both environments from third machine (phys. win8.1). After ~5 hours: can connect with ssh to one container (running on vm /wired connection) and can not connect to another (running on machine with wireless).
p2p debug:
C:\Subutai\bin>p2p debug
DEBUG INFO:
Number of gouroutines: 20
Instances information:
Hash: swarm-bec602e0-1d68-46e1-961a-72d5eb045af3
ID: f92122cb-4d17-11e6-8348-022d0fae0f03
Interface Local Area Network1, HW Addr: 00:ff:01:8c:1a:e7, IP: <IP_ADDRESS>
Peers:
--- eb526d62-4d17-11e6-82b8-022d0fae0f03 ---
HWAddr: 06:d3:95:bb:36:f3
IP: <IP_ADDRESS>
Endpoint: <IP_ADDRESS>:49218
Peer Address: <IP_ADDRESS>:60348
Proxy ID: 11
--- End of eb526d62-4d17-11e6-82b8-022d0fae0f03 ---
--- eb351270-4d17-11e6-88ce-022d0fae0f03 ---
HWAddr: 00:ff:38:5a:6f:00
IP: <IP_ADDRESS>
Endpoint: <IP_ADDRESS>:49218
Peer Address: <IP_ADDRESS>:65496
Proxy ID: 10
--- End of eb351270-4d17-11e6-88ce-022d0fae0f03 ---
--- f057b772-4d17-11e6-88ff-022d0fae0f03 ---
HWAddr: 00:ff:2f:aa:51:57
IP: <IP_ADDRESS>
Endpoint: <IP_ADDRESS>:53963
Peer Address: <IP_ADDRESS>:56294
Proxy ID: 18
--- End of f057b772-4d17-11e6-88ff-022d0fae0f03 ---
C:\Subutai\bin>
p2p log:
p2p_log.txt
after some tries SubutaiTray crashed, restarted tray and p2p service. after ~ 6 minutes connected to the second container

Long running test: stop to connect to env with ssh after some time (~1 hour after p2p service restart, need to test more to find), need to restart p2p service to connect again (before had experience with 7 days running environment on the same machine without problems)
providing logs


Country/language radio button

I would be great to have a helper for selecting language/country, displayed with flags.
E.g. the following form has a field for selecting post language http://take.ms/PUbCb
Alternative approach, is to display select component with flags and names of languages.
@khusnetdinov thoughts?

It relate to form witch create change set, and it had better to create radio group with locales flags. See locales it can help with implementation


Enable detectBrowserLanguage not only on root, but on several other pages

Hi guys, I need your help, please
For example, at nuxt.config.js I set:
i18n: {
    detectBrowserLanguage: {
      onlyOnRoot: true // for better SEO
   }
}

But on several specific pages, I still want to auto-detect and redirect users to their language.
Is that possible to set "onlyOnRoot: false" on some pages?

The module doesn't provide such functionality.


Support JSX spread attribute

tx-jsx-loader (Webpack plugin) supports JSX with TypeScript,
but using JSX spread attirbute causes error becasue a necessary hook is missing.
I added a hook to use JSX spread attribute.

@pspeter3 @vsiao could you review this PR?

Hmm, don't think you should be adding this here. https://github.com/jbrantly/ts-jsx-loader/blob/master/react-jsx.d.ts is provided for this purpose. @jbrantly can confirm.

Yup. Agree that __spread should not be added here. If you want to use ts-jsx-loader, use the provided react-jsx.d.ts.

Sorry for taking your time.
I should check ts-tx-loader repository well.
Code like <Router.RouteHandler {...this.props} /> works fine.

Hello and thank you for your contribution!
Due to an excessively long queue of pull requests that have become stale, we are "declaring bankruptcy" and closing all PRs opened before May 1, 2016. If you'd still like to merge this code in, please open a new PR that has been merged and rebased with the master branch.
Going forward, we are committing to review or merge all PRs on a regular basis so this bankruptcy will not occur again. We apologize for the incovenience and hope you will continue to contribute to DefinitelyTyped in the future.
Thanks
The TypeScript and DefinitelyTyped teams


Main b 21457 too approve email for retiree separatee

INTEGRATION PR
B-21457
Summary
Currently when a TOO creates a move task order , emails that gets sent to retirees and separatees state that their move is scheduled to deliver to their HOS/HOR/PLEAD instead of the delivery address on their shipment. So these changes are to let the delivery address on the email to display the right address.
this article explains more about the approach used.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

[x] Has the branch been pulled in and checked out?
[x] Have the BL acceptance criteria been met for this change?
[x] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests
Local testing for emails, you will need to start the server with this:
EMAIL_BACKEND=ses AWS_REGION=us-gov-west-1 aws-vault exec transcom-gov-dev -- make server_run

How to test

Access the application
Login as a Customer
Create a new move (Select Retirement/ Separation) on the "Tell us about your move orders page".
Go through the process of Setting up a shipments (e.g HHG/PPM) to create a shipment , sign a complete(Make sure to copy/save your move code for later).
Login as a Service Counselor(SC)
Search for your move code in step 4 and navigate to it.
Make sure you edit/fix any required fields.
Login as a TOO
Repeat step 6
Select the checkbox  for the shipment created in 4
Scroll down and click "Approve selected" button.
Click "Approve and send" button.
You will receive an email (it took ~ 15 mins during testing) with subject"Your personal property move has been ordered" in the email you provided during the Move/shipment creation process.
Note that the verbiage in the email "This is a confirmation that a move task order has been placed for your move  [YOUR_MOVE_CODE] to [Destination_address_you_provided_for_shipment].

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys.
[ ] Have been communicated to #g-database.
[ ] Secure migrations have been tested following the instructions in our docs.

Screenshots
B-21457-TOO-Approved-Move-Details-Emails.docx

@brianmanley-caci this pr is good for main merge when you get the chance.thanks.


[wip]Fix HostStats UpstreamConnectionActive statistics errors

Issues associated with this PR
Your PR should present related issues you want to solve.
Solutions
You should show your solutions about the issues in your PR, including the overall solutions, details and the changes. At this time, Chinese is allowed to describe these.
UT result
Unit Test is needed if the code is changed, your unit test should cover boundary cases, corner cases, and some exceptional cases. And you need to show the UT result.
Benchmark
If your code involves the processing of every request, you should give the Benchmark Result.
Code Style

Make sure Goimports has run
Show Golint result

fix other stats, and such as UpstreamConnectionClose.


SSH access allowed from public networks

When connected to a WiFi network, I can access the ssh server on the AP. This must be prevented by default. There already are firewall rules in place on the device that are intended to prevent exactly that, but they don't match because the interface name is wrong (it's missing the br- prefix for the bridge).
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target     prot opt in     out     source               destination
0     0 DROP       tcp  --  lan_60014 *       <IP_ADDRESS>/0            <IP_ADDRESS>         tcp dpt:22
0     0 DROP       tcp  --  lan_60014 *       <IP_ADDRESS>/0            <IP_ADDRESS>           tcp dpt:22
0     0 DROP       tcp  --  lan_60014 *       <IP_ADDRESS>/0            <IP_ADDRESS>       tcp dpt:22
0     0 DROP       tcp  --  lan_10887 *       <IP_ADDRESS>/0            <IP_ADDRESS>          tcp dpt:22
0     0 DROP       tcp  --  lan_10887 *       <IP_ADDRESS>/0            <IP_ADDRESS>         tcp dpt:22
0     0 DROP       tcp  --  lan_10887 *       <IP_ADDRESS>/0            <IP_ADDRESS>       tcp dpt:22

I don't believe that is wrong.
Can you paste in here the firewall.user?

WANIF=route | awk '/default/ { print $8 }'
. /lib/functions/network.sh
network_get_ipaddr WANIP wan
network_get_subnet local wan
iptables -I FORWARD 1 -i br-lan_60014 -o $WANIF -j ACCEPT
iptables -I FORWARD 1 -i br-lan_10887 -o $WANIF -j ACCEPT
iptables -A INPUT -i lan_60014 -p tcp --dport 22 -d <IP_ADDRESS> -j DROP
iptables -A INPUT -i lan_60014 -p tcp --dport 22 -d <IP_ADDRESS> -j DROP
iptables -A INPUT -i lan_60014 -p tcp --dport 22 -d $WANIP -j DROP
iptables -A INPUT -i lan_10887 -p tcp --dport 22 -d <IP_ADDRESS> -j DROP
iptables -A INPUT -i lan_10887 -p tcp --dport 22 -d <IP_ADDRESS> -j DROP
iptables -A INPUT -i lan_10887 -p tcp --dport 22 -d $WANIP -j DROP
iptables -I FORWARD -s <IP_ADDRESS>/24 -p tcp -d $local -j DROP
iptables -I FORWARD -s <IP_ADDRESS>/24 -p udp -d $local -j DROP
iptables -I FORWARD -s <IP_ADDRESS>/24 -p icmp -d $local -j DROP
iptables -I FORWARD -s <IP_ADDRESS>/24 -p icmp -d $local -j DROP

Ok, give me till tomorrow to look at this when I'll get in the office and I'll update the issue.

@AndrewMargarit @mbecks Checked this locally today and the rule is defo missing the br- prefix.
I can patch the configs easily today however I've just noticed there's a lot of people using SSH internally. We can't therefore just deploy without allowing an option to edit.
Ideally we just put an section in for the undocumented firewall API but this will take some work. I'm going the therefore propose an option for the short-term in the network settings.

I've updated the configs for this but only on the next version of SM. Should be out v. soon..
Am putting an option in to disable / enable ssh also.

This is resolved in SMv4 and won't be applied to v3.


Enhanced Combustion Generator and Combustion Generator

Issue Description:
Noticed Enhanced Combustion Generator block is voiding Gelid Cryotheum from Thermal Foundation and Crushed Ice from Forestry. Combustion Generator is just voiding Gelid Cryotheum.

Please use requested issue format. It's there fore a reason.


Do not emit error when callback is passed to Advertisement.create

If dns_sd.DNSServiceRegister results in an error and you've passed a callback to Advertisement.create the error is passed to the callback as well as being emitted on the advert itself.
E.g.:
var advert = mdns.createAdvertisement(mdns.tcp('my-service'), port, function (error) {
  // will be called with error
})
advert.on('error', function (error) {
  // will also be called with the same error
})

Since the error is emitted on the advert you have to listen for the error event even if you pass a callback otherwise your process will crash with an uncaught exception.
This pull request changes Advertisement to not emit the error if a callback was passed and adds tests for the new behaviour.

I'm happy with the solution, but why the sinon injection here?

Apologies for being unresponsive. It must have slipped... my bad.
Man, this (my) code is old... and it still has error handling bugs. >:-{ ... So, nice catch. The fix looks good to me too, but like @ronkorving I wonder if we really need a new dependency. Could you refactor the test to make do without it?


ARROW-4688: [C++][Parquet] Chunk binary column reads at 2^31 - 1 byte boundaries to avoid splitting chunk inside nested string cell

Chunked outputs with nested types still does not work though; that will have to be addressed later

+1. Test failures appear transient


Having some trouble with Layout/SpaceAroundOperators

We're implementing rubocop in our projects at work and I've stumbled upon an issue and i'm not sure what's best to do here.

Expected behavior
this should not offend by rubocop:
  columns [:wagon, :wagon_nr]                       =>
            [[
              'wagon',
              'wagonnummer',
              'wagon nummer',
              'wagon nr',
              'wagon number',
              'wagonnumber',
              'wagennummer',
              'waggonnummer',
              'wgnr12stellig',
              'Železniční vůz / waggon'
            ]],
          [:wagon, :wagon_sub_type_id]              =>
            [[
              'gattung',
              'wagontype',
              'gat uic',
              'type'
            ]],
          [:wagon_achievements, :loaded_distance]   => ['loaded km'],
          [:wagon_achievements, :unloaded_distance] => ['unloaded km'],
          [:wagon_achievements, :cleaned]           => ['cleaned']

Actual behavior
app/parsers/assets/wagons/wcl_parser.rb:2:53: C: Operator => should be surrounded by a single space.
  columns [:wagon, :wagon_nr]                       =>
                                                    ^^

so rubocop only marks the first operator as offending, the other operators are fine
Steps to reproduce the problem
put the source above in a file and:
rubocop /path/to/file
RuboCop version
-> rubocop -V
0.49.1 (using Parser <IP_ADDRESS>, running on ruby 2.3.1 x86_64-darwin16)

The Layout/SpaceAroundOperators cop works in co-operation with the Layout/AlignHash cop, and uses its configuration. To allow the style you're using here, you need to set
Layout/AlignHash:
  EnforcedHashRocketStyle: table

Does @jonas054's comment resolve this issue?


Extra columns should come before

Fixes #244

Release images for this have tag: v1.0.0-beta.1-6-gc1947e4


allow custom http_headers in config.yaml

This PR creates the config option
http_headers:
  Bearer: eyJhbGciO...
  MyFancyHeader: MyFancyValue

in config.yml to allow setting custom HTTP Headers in request to elasticsearch.

@henkwiedig
Any way you could push this PR to https://github.com/jertel/elastalert ?


Issue with custom foreign key

database_consistency reports an error with one of our model relationships:
class FormRequest < ApplicationRecord
  # t.integer "status_id", null: false
  belongs_to :status, inverse_of: :form_requests, class_name: 'FormRequestStatus'
end

class FormRequestStatus < ApplicationRecord
  has_many :form_requests, inverse_of: :status
end

Error:
<===begin===>
Traceback (most recent call last):
	24: from /home/fletch/.rvm/gems/ruby-2.7.4/bin/ruby_executable_hooks:22:in `<main>'
	23: from /home/fletch/.rvm/gems/ruby-2.7.4/bin/ruby_executable_hooks:22:in `eval'
	22: from /home/fletch/.rvm/gems/ruby-2.7.4/bin/database_consistency:23:in `<main>'
	21: from /home/fletch/.rvm/gems/ruby-2.7.4/bin/database_consistency:23:in `load'
	20: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/bin/database_consistency:44:in `<top (required)>'
	19: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency.rb:53:in `run'
	18: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/base_processor.rb:13:in `reports'
	17: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/base_processor.rb:13:in `flat_map'
	16: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/base_processor.rb:13:in `each'
	15: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/base_processor.rb:14:in `block in reports'
	14: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/base_processor.rb:29:in `reports'
	13: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/associations_processor.rb:15:in `check'
	12: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/associations_processor.rb:15:in `flat_map'
	11: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/associations_processor.rb:15:in `each'
	10: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/associations_processor.rb:18:in `block in check'
	 9: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/associations_processor.rb:18:in `flat_map'
	 8: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/associations_processor.rb:18:in `each'
	 7: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/associations_processor.rb:19:in `block (2 levels) in check'
	 6: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/associations_processor.rb:19:in `map'
	 5: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/processors/associations_processor.rb:21:in `block (3 levels) in check'
	 4: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/checkers/base_checker.rb:34:in `report_if_enabled?'
	 3: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/checkers/base_checker.rb:25:in `report'
	 2: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/checkers/association_checkers/foreign_key_type_checker.rb:40:in `check'
	 1: from /home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/checkers/association_checkers/foreign_key_type_checker.rb:85:in `associated_column'
/home/fletch/.rvm/gems/ruby-2.7.4/gems/database_consistency-1.1.1/lib/database_consistency/checkers/association_checkers/foreign_key_type_checker.rb:99:in `column': Association (form_requests) of class (FormRequestStatus) relies on field (form_request_status_id) of table (form_requests) but it is missing. (DatabaseConsistency::Errors::MissingField)
<===end===>

Happy to provide any additional information that might help debugging. These models are heavily used in our application, so I'm confident they are working.

Hi @mockdeep, thank you for reporting the issue!
Could you please show what SQL query outputs the following command in console for you? Also, please share if that is working as expected by you.
FormRequestStatus.first.form_requests

Ah, nevermind! We don't use the inverse relationship, so that didn't work. It should have been:
class FormRequestStatus < ApplicationRecord
  has_many :form_requests, inverse_of: :status, foreign_key: :status_id
end

It should have been:

Yes, that's what the error was about =)


TS error caused by "hybrid" output mode not available anymore on Astro 5

When upgrading to Astro v5 (beta), I noticed that my build started failing on node_modules/astro-pagefind/src/pagefind.ts.
The error is caused by a check for config.output where it's compared to hybrid.
Since this output mode doesn't exist anymore in v5 of Astro, the check fails.
Not sure how you could fix it without breaking it for v4 (and before) users though..

Thanks for the heads-up. We can always cast it to string before comparing. I need to check again if I can simplify this code in newer Astro versions. Basically, config.outDir supposed to be enough but I had issues with it in hybrid before.

I've now encountered another issue which comes with Astro 5 and this integration. I'm using node adapter and the files are built into dist whereas astro with node builds client assets into dist/client. It is probably caused by the condition of output === hybrid which is not met.
I guess for now simply a config option to manually set the outdir could work.

Fixed in v1.7.0


Mipha-3B and SigLP link

Hi authors,
Thanks for your excellent work. I find that you put these two links wrongly.
Best

Thanks for the reminder and we have already resolved the issue.

Thanks for the reminder and we have already resolved the issue.

Great. Looking forward to the training code.


Enable using the DBMS's SSO provider by default, if no specific provider is specified in the application config

This lets users on https://neodash.graphapp.io authenticate with SSO on Neo4j Aura, so no custom NeoDash deployment is needed.

This would be a useful feature to add. We plan to use Bloom to expose data to customers. Bloom is very flexible , but requires some learning curve. Bloom combined with Neodash can be a very powerfull combination. Supporting SSO is essential to make this happen in our use case


Fix an issue where Zydog was stonebanned

It conflicted with another commit but I think this way of expressing it is better.

It conflicted with another commit but I think this way of expressing it is better.


Update log-analytics-om-agents.md

correcting typos

@MikaVirkkunen,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@MikaVirkkunen : Thanks for your contribution to the Azure documentation! The author, @MGoedtel, has been notified to review your proposed change.

@MikaVirkkunen - Thanks for taking the time to make those corrections.  I approve the changes - #sign-off.


Automatically build libv86 on CI

Can you automatically build libv86.js on Travis CI at every commit and publish it to some server or GitHub Pages? This would be very good because users then won't need to install and configure Closure Compiler and other build dependencies.
Can you also configure Makefile to also build sourcemap file for libv86.js?
Also, the version on your website is very old (from 2018). Can you also update it?

Actually, here is what I do when I want to use v86:
wsl wget http://copy.sh/v86/build/libv86.js

but I didn't know on the website it's old

I also noticed maybe cat instead of closure compiler (for debug builds)? This would be faster.

@copy I'm currently working on PR to build libv86 in Travis CI and publish it to GitHub Pages. Should I publish ACPI version, non-ACPI version of both?

I also noticed maybe cat instead of closure compiler (for debug builds)? This would be faster.

Closure Compiler also does some type checking and linting, I don't think we should disable that.
Closing this issue as it's complete.


Any way to ignore remote sources and choose a "default"?

I have 3 remotes for my git repo:

origin
heroku-staging
heroku-production

I'd like to automatically select "origin" so I don't get the intermediate modal that lets me choose every time. This should be relevant to one project. Is that achievable?

I can't think of a simple way to do this.

My first thought is to assume the first remote selected in the project is the default but that would lead to problems.

Another way is to have users add extra git-plus related options to the repo's gitconfig. That's less messy although I'm not sure how people may feel about that.

Lastly, there could be a package command to set the default and another command to push to default. I'm iffy on having a pair of commands for this.

Of these I'm leaning more towards option 2. What do you think?

I like option 2 better too, but how about a CSON file instead? Something along the format of:
'/Users/myuser/Dev/projectDir':
    'remote-default': 'origin'
    # other configurable stuff in the future

This could be accessible from the package settings and command palette (same way color-tabs-regex does it for example)

Oh that's even better. The next two priorities I have are allowing support for non-ssh users and showing diffs during commits. If you want to take a stab at implementing this, that would be great

I'm not really experienced with atom packages, but I'll give it a go. :) :+1:

:+1: for the feature request, and option 3 in my opinion is better because it's more atom-y, in the sense that  commands are so easily accessible and easy to find through the command palette. But option 2 works as well :)
Any update on this feature being implemented?

@orensol I haven't picked this up yet. You make a good point about option 2 being more atom-y. Whenever this gets picked up, that should be the route taken and we can leverage atom's ability to manage state


Problems in upgrading from influxdb-0.11.0-1 to Enterprise Edition

We are trying to upgrade from Influxdb-0.11.0-1 to Influx Enterprise Edition (latest paid version). I have installed the meta nodes and installed them as well. But when I try to install the data nodes, after downloading them, it shows me transaction errors as follows:
[centos@ip-10-24-34-146 ~]$ sudo yum localinstall influxdb-data-1.0.0_beta3_c1.0.0rc1.x86_64.rpm
Loaded plugins: fastestmirror
Repodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fast
Examining influxdb-data-1.0.0_beta3_c1.0.0rc1.x86_64.rpm: influxdb-data-1.0.0_beta3_c1.0.0rc1-1.x86_64
Marking influxdb-data-1.0.0_beta3_c1.0.0rc1.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package influxdb-data.x86_64 0:1.0.0_beta3_c1.0.0rc1-1 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================================================================================================================
Package                                  Arch                              Version                                            Repository                                                              Size
Installing:
influxdb-data                            x86_64                            1.0.0_beta3_c1.0.0rc1-1                            /influxdb-data-1.0.0_beta3_c1.0.0rc1.x86_64                             64 M
Transaction Summary
Install  1 Package
Total size: 64 M
Installed size: 64 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction check error:
file /etc/influxdb/influxdb.conf from install of influxdb-data-1.0.0_beta3_c1.0.0rc1-1.x86_64 conflicts with file from package influxdb-0.11.0-1.x86_64
file /usr/bin/influx from install of influxdb-data-1.0.0_beta3_c1.0.0rc1-1.x86_64 conflicts with file from package influxdb-0.11.0-1.x86_64
file /usr/bin/influx_inspect from install of influxdb-data-1.0.0_beta3_c1.0.0rc1-1.x86_64 conflicts with file from package influxdb-0.11.0-1.x86_64
file /usr/bin/influx_stress from install of influxdb-data-1.0.0_beta3_c1.0.0rc1-1.x86_64 conflicts with file from package influxdb-0.11.0-1.x86_64
file /usr/bin/influx_tsm from install of influxdb-data-1.0.0_beta3_c1.0.0rc1-1.x86_64 conflicts with file from package influxdb-0.11.0-1.x86_64
file /usr/bin/influxd from install of influxdb-data-1.0.0_beta3_c1.0.0rc1-1.x86_64 conflicts with file from package influxdb-0.11.0-1.x86_64
file /usr/lib/influxdb/scripts/init.sh from install of influxdb-data-1.0.0_beta3_c1.0.0rc1-1.x86_64 conflicts with file from package influxdb-0.11.0-1.x86_64
Error Summary
Should I take this as a normal installation or is there any error which I have to rectify?

@jainbhavuk630 You won't be able to upgrade an 0.11cluster to enterprise clustering directly.  I'd recommend contacting support for assistance on a migration path.  cc @beckettsean
@rossmcdonald Any idea what's going on with the packaging?

The Enterprise influxdb-data and OSS influxdb packages are considered distinct by the package manager, but have conflicting directory usages (hence the file conflicts around /etc/influxdb, etc).
When installing Enterprise influxdb-data over OSS influxdb, the influxdb package should be erased from the RPM database prior to installing influxdb-data. For example:
# Assuming OSS InfluxDB is already installed...

# Erase InfluxDB from RPM database (does not erase data directories, only binaries and configuration)
sudo rpm -e influxdb

# Install influxdb-data
sudo yum localinstall influxdb-data-1.0.0_beta3_c1.0.0rc1.x86_64.rpm